{"action":"created","issue":{"url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/226","repository_url":"https://api.github.com/repos/ircv3/ircv3-specifications","labels_url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/226/labels{/name}","comments_url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/226/comments","events_url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/226/events","html_url":"https://github.com/ircv3/ircv3-specifications/issues/226","id":133284875,"number":226,"title":"Suggestion: Conversation Threading","user":{"login":"mofosyne","id":827793,"avatar_url":"https://avatars.githubusercontent.com/u/827793?v=3","gravatar_id":"","url":"https://api.github.com/users/mofosyne","html_url":"https://github.com/mofosyne","followers_url":"https://api.github.com/users/mofosyne/followers","following_url":"https://api.github.com/users/mofosyne/following{/other_user}","gists_url":"https://api.github.com/users/mofosyne/gists{/gist_id}","starred_url":"https://api.github.com/users/mofosyne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mofosyne/subscriptions","organizations_url":"https://api.github.com/users/mofosyne/orgs","repos_url":"https://api.github.com/users/mofosyne/repos","events_url":"https://api.github.com/users/mofosyne/events{/privacy}","received_events_url":"https://api.github.com/users/mofosyne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-12T16:33:38Z","updated_at":"2016-02-12T17:49:00Z","closed_at":null,"body":"Has there been any thoughts about supporting conversation threading? Is there any benefits to using it?\r\n\r\nBasically, allows for referring to a previous message. So that an IRC conversation could be multithreaded like reddit.\r\n\r\nThere is some precedence of conversation threading used in real time instant messaging protocol, such as telegram. It seems to be a pretty useful feature. \r\n\r\nhttps://en.wikipedia.org/wiki/Conversation_threading\r\n\r\n\r\n---------\r\n\r\nPossible references to this concept:\r\n\r\n* https://github.com/flowdock/oulu/issues/47 \"Replying to specific discussions is a useful feature of Flowdock, but there seems to be no way of doing it through IRC.\" -- gitkrax |  \"@gitkrax Unfortunately the IRC protocol doesn't support threads, so we would need to do something that's based on plain text.\" -- mutru"},"comment":{"url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/comments/183427719","html_url":"https://github.com/ircv3/ircv3-specifications/issues/226#issuecomment-183427719","issue_url":"https://api.github.com/repos/ircv3/ircv3-specifications/issues/226","id":183427719,"user":{"login":"mofosyne","id":827793,"avatar_url":"https://avatars.githubusercontent.com/u/827793?v=3","gravatar_id":"","url":"https://api.github.com/users/mofosyne","html_url":"https://github.com/mofosyne","followers_url":"https://api.github.com/users/mofosyne/followers","following_url":"https://api.github.com/users/mofosyne/following{/other_user}","gists_url":"https://api.github.com/users/mofosyne/gists{/gist_id}","starred_url":"https://api.github.com/users/mofosyne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mofosyne/subscriptions","organizations_url":"https://api.github.com/users/mofosyne/orgs","repos_url":"https://api.github.com/users/mofosyne/repos","events_url":"https://api.github.com/users/mofosyne/events{/privacy}","received_events_url":"https://api.github.com/users/mofosyne/received_events","type":"User","site_admin":false},"created_at":"2016-02-12T17:48:59Z","updated_at":"2016-02-12T17:48:59Z","body":"to dequis : \r\n  Alternatively the ID could be a hash (doesn't have to be strong, even md5 could do).\r\n\r\n-------\r\n\r\nto SaberUK : \r\n  There are various ways to approach the User Interface aspect of real time threaded conversation.\r\n\r\n* Jump to Prev/Next : In telegram, you can jump to previous comment, which is still held in cronological order. There is a button to then jump forward (and eventually back to real time view).\r\n\r\n* Split screen: The mainscreen chatroom remains the same, however clicking on a thread would open up a split screen showing only the post in that thread (as if it was a separate chatroom). This is good for observing the main chatroom, while seeing any updates to the thread.\r\n\r\n* Tree branch interface: Everything is arranged not in chronological order, but in a branching thread interface (like reddit). Good for overview, but not as good in keeping track of current chat.\r\n\r\nAnyway the point is, there is various possible approaches to dealing with this, and it has been done in actual instant messaging apps already. (Heck 4chan can even count as one if you F4 refresh fast enough).\r\n\r\nEither-way, the minimum needed to allow for these kinds of experimentation, is just to have the ability to tag a message as having a parent.\r\n\r\n"}}