{"shas":[["bb7c8641e14bcb5a981d37254f0968ddfc8bfa85","29bbaec13092d36559e3abc6f27f7d09c395819f@mit.edu","Preliminary support for jabber chat state notifications.\n\nChat state notifications are described in XEP-0085,\nhttp://xmpp.org/extensions/xep-0085.html.\n\nThe variable jabber:chat_state_notifications, which defualts to on,\ncontrols whether or not chat state notifications (csns) are sent (and,\nonce implemented, whether or not recieved chat state notifications are\ndisplayed).\n\nThis commit implements support for sending <active/> and <composing/>\nnotifications.\n\nThings not yet implemented that must be implemented before this gets\nmerged into master:\n * There are a few things I marked XXX TODO, mostly due to my lack of\n   knowledge of perl.  Someone should check these things and either\n   point me in the direction of a better way to do them, or tell me that\n   what I did is fine.\n * BarnOwl MUST advertise that it supports csns in response to service\n   discovery\n * BarnOwl MUST NOT send <composing/> (or other standalone) csns if the\n   party on the other end does not support csns (doesn't include an\n   <active/> tag in its messages).\n     . This means we need to keep track of which jids support csns, and\n       maybe expire this cache at some point.\n     . We need to decide whether to send a service discovery query to\n       users that haven't chatted with before to decide whether to send\n       a composing notification, or to simply not send composing\n       notifications until/unless we get a reply.\n * We should come up with (good) way to display received csns to our\n   users.\n\nThings not yet implemented that we should implement at some point:\n * BarnOwl SHOULD support <paused/>, <inactive/>, <gone/>.  We'll need\n   more editwin hooks to do this.","Jason Gross"],["0d5cfa5580f7116336d11f142bf449bfa3d124b1","29bbaec13092d36559e3abc6f27f7d09c395819f@mit.edu","Check for recipient support of chat state notifications\n\nBarnOwl only sends stand-alone chat-state notifications if the last chat\nrecieved from the recipient contained a chat state.  This may not be the\nbest way to cache things.\n\nThings to possibly implement in the future:\nDiscover support for chat state notifications if we start composing\nbefore they send their first message.","Jason Gross"]],"repo":"JasonGross/barnowl","actor":"JasonGross","ref":"refs/heads/jabber-chat-state-notifications","size":2,"head":"0d5cfa5580f7116336d11f142bf449bfa3d124b1","actor_gravatar":"c11c7cc23517cf5f043b51fc7914049a","push_id":31930566}