You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll need to poll the server for user status. Probably more efficient to do this using client.send('WHO', '#channelName') than to maintain a list of users we've seen in all the channels on the server and query each one with client.whois() individually.
The response to a raw WHO command will be sent in a raw event, with one event per user. The events all have a command attribute of 'rpl_whoreply'.
Looks like the interesting bits of the response to a raw WHO command are:
This is repeated for each user in the channel. the 7th item in the args array is the status, H for “Here” and G for “Gone”. Looks like it can be followed by characters like * or @ if the user is an admin too.
The text was updated successfully, but these errors were encountered:
4a1ce66 includes some work towards this, polling each channel for user statuses and then updating their userButtons when they go away / come back.
As for putting the status in the scrollback, I’m starting to wonder what the benefit is of historical away activity. If a conversation is happening in a channel, do I really want a completely unrelated line popping up, recording the fact that some unrelated person set themselves as away?
Thinking about it, the times I'm interested in someone's status are:
When speed of response is important, and I want a heads-up, before starting a direct message whether the ideal person is likely to respond quickly, or whether I should ask someone else / not ask the question at all.
When I'm mid-chat with someone and they're not responding – or someone's been mentioned and they've not responded yet. Knowing if they're “away” would help explain their silence.
Both of these can be achieved by displaying users’ current status in the sidebar. Neither of them require a historical record of "this user went away at this point and came back at this point" in the channel scrollback.
We'll need to poll the server for user status. Probably more efficient to do this using
client.send('WHO', '#channelName')
than to maintain a list of users we've seen in all the channels on the server and query each one withclient.whois()
individually.The response to a raw
WHO
command will be sent in araw
event, with one event per user. The events all have acommand
attribute of'rpl_whoreply'
.Looks like the interesting bits of the response to a raw
WHO
command are:This is repeated for each user in the channel. the 7th item in the
args
array is the status,H
for “Here” andG
for “Gone”. Looks like it can be followed by characters like*
or@
if the user is an admin too.The text was updated successfully, but these errors were encountered: