IRC log for #openknot, 2016-10-01

Open Knot Communications Platform - https://github.com/openknot

All times shown according to UTC.

Time	Nick	Message
17:38	pdurbin	How could IRC support threads or subjects? For more context, please see https://gitter.im/gitterHQ/irc-bridge/archives/2016/10/01 and how I'm being told http://blog.gitter.im/2016/09/30/introducing-gitter-topics/ can't be supported via IRC.
19:09	dotplus	I don't think it's crazy talk - but also I can't see traditional IRC clients supporting a threaded/conversation-based model, although it wouldn't be impossible. I could see it happening for web/browser-based clients.
19:11	dotplus	The difficulty, basically, would be: how to provide the user with a frictionless, preferably completely transparent, method of (switching between\|following [new] threads).
19:11	dotplus	that's not how IRC clients work currently.
19:18	dotplus	One way would be to have unusually sophisticated "room" list, which would really be a "thread" list. What kind of sophistication am I talking about? it would auto-update and it would offer uncommonly powerful search/filter such as 1) by regex (to take advantage of possible conventionalizing of the thread/room names, such as pre/suffix with (threadcreator\|lastpostauthor) or pre/suffix with "parent" room/thread 2) timestamp of (creation\|last ...
19:18	dotplus	... post) 3) probably more, but that's what springs to mind before I get on the plane
23:16	pdurbin	dotplus: nice thoughts. thanks. safe flight

Open Knot Communications Platform - https://github.com/openknot