How will the chat API work?
nightzirch.3126:
Hi Lawton and the rest of the crew!
In the thread regarding permissions I noticed “Chat” was mentioned, but later edited out with the comment “scrap chat for now; that’s months away still.”
I understand you may not have specified this endpoint 100%, but I am curious about your thoughts on what the chat API will include, what we will get permissions to do with it, and how it will work.
Thank you for taking the time to answer!
Lawton Campbell.8517:
It’ll just be access to guild chat. Not sure what transport we’ll use or any of the other details. Literally all I’ve done so far is sit down and say “I should be able to use guild chat while not logged into the game”.
Strategist.6132:
It will probably be a little harder to implement then the other API’s, but I really think this would enhance the community so hard.:P I already see myself chatting with my guild mates during the lectures haha:P
nightzirch.3126:
It’ll just be access to guild chat. Not sure what transport we’ll use or any of the other details. Literally all I’ve done so far is sit down and say “I should be able to use guild chat while not logged into the game”.
Hehe, what I thought and I fully agree.
I also noticed mailing and friendslist were mentioned before edited away in the before-mentioned thread. Are those still on the table we all love so much?
Lawton Campbell.8517:
It’ll just be access to guild chat. Not sure what transport we’ll use or any of the other details. Literally all I’ve done so far is sit down and say “I should be able to use guild chat while not logged into the game”.
Hehe, what I thought and I fully agree.
I also noticed mailing and friendslist were mentioned before edited away in the before-mentioned thread. Are those still on the table we all love so much?
Mail, if we had an endpoint, could ever only be read-only. And you can’t see mails you’ve sent. It’d be a lot of work for a fairly low-value endpoint, IMO.
Friend/block lists might make it though I don’t have plans in the near future for ‘em. There’s a bunch of small fires to put out now and a bunch of other endpoints/improvements ahead of it in line.
MithranArkanere.8957:
The only thing I wonder is if it’ll be like a chat log, allowing access to previous lines for a period of time (e.g.: previous lines up to an hour, a certain amount of lines or a certain amount of bytes), or it’s just listen to lines as they come.
If it allowed to request previous lines, it’ll be a nice way to review things you heard but missed, or copy stuff pasted by people in chat (e.g: Roleplaying dialogs, URLs…)
Lawton Campbell.8517:
The only thing I wonder is if it’ll be like a chat log, allowing access to previous lines for a period of time (e.g.: previous lines up to an hour, a certain amount of lines or a certain amount of bytes), or it’s just listen to lines as they come.
You’d hypothetically be able to set up your own chat logger; we probably won’t provide it since our chat backend does not keep that data internally (it shunts all that to the logs for archival/analytics).
TheHeretic.3529:
This is awesome, and others in my guild feel the same about it. We’d love to see an Android app or a mobile web app!
Valento.9852:
If it’s too hard to sync in-game chat with the API, I would still be very happy to at least send “delayed messages” with an internal time restriction (one message every 1min. or something). I take it would be very difficult to handle quick flux of messages, but maybe I’m just overlooking how the API works. Either way, as long as it’s possible to have a chat with friends, it would be very cool and appreciated.
Lawton Campbell.8517:
If it’s too hard to sync in-game chat with the API, I would still be very happy to at least send “delayed messages” with an internal time restriction (one message every 1min. or something).
The main issue is receiving messages back out in a timely manner. Our backend isn’t designed to do anything but request-reply (and doesn’t have any persistence so long-polling will drop messages). It requires some rearchitecting to get working.