4 ms·

There are good reasons to not have a backlog in a chat system. For one it stops you from being lazy and not maintaining FAQs and documentation. It also forces

There are good reasons to not have a backlog in a chat system. For one it stops you from being lazy and not maintaining FAQs and documentation. It also forces you to stop treating the chat as something you need to keep up to date with. At work I see people commonly scrolling back for pages and pages to find the last read marker and continue reading from there. This seems unhealthy to me. I use a bouncer but I very rarely use the logs. For all the purposes for which I would use logs, there are normally bots in the channel which can compensate.

op00to 3y ago
I worked on a global team and conversation happens 24/7. When my bouncer dropped, I would miss out on critical stuff.
- Arch-TK 3y ago
  If discord had a blip and stopped working for your global team then you would have a more catastrophic problem surely? Regardless, what is your point? I never claimed that conversions can't happen when you are not online, just that you should design your conversations such that it doesn't matter if someone isn't online. The problem you just described was caused not by IRC and its lack of backlog but by you and your team and your misuse of a backlog-less chat system. Important announcements shouldn't be done on IRC. For that matter, neither should they be done on Teams, Slack, Discord, Matrix, XMPP, or Skype. Important announcements belong on a web page and a mailing list (both simultaneously) or alternatively on some other purpose built system which tracks who has seen an annoucement so that if important announcement is missed by a key player, someone is alerted and can reach out using an alternative method of communication. But even if you insist on misusing a chat protocol like IRC for this, ask someone who was there for their logs? I don't understand how nobody on your global team was able to even just summarize what you missed.
  - j45 3y ago
    IRC bots literally maintained a history for anyone to catchup.
- SV_BubbleTime 3y ago
  That fair… but does that sound like a that called for a synchronous system? It seems someone chose the wrong thing, then you needed a history feature to bridge the gap.
j45 3y ago
This is a good point. Using chat as a source of truth is not a good idea Over time it becomes more and more ridiculous to use it as your knowledge base.
- esafak 3y ago
  Telling people to stop chatting is close to a nonstarter. You have to offer a better alternative.

op00to 3y ago

I worked on a global team and conversation happens 24/7. When my bouncer dropped, I would miss out on critical stuff.

Arch-TK 3y ago
If discord had a blip and stopped working for your global team then you would have a more catastrophic problem surely? Regardless, what is your point? I never claimed that conversions can't happen when you are not online, just that you should design your conversations such that it doesn't matter if someone isn't online. The problem you just described was caused not by IRC and its lack of backlog but by you and your team and your misuse of a backlog-less chat system. Important announcements shouldn't be done on IRC. For that matter, neither should they be done on Teams, Slack, Discord, Matrix, XMPP, or Skype. Important announcements belong on a web page and a mailing list (both simultaneously) or alternatively on some other purpose built system which tracks who has seen an annoucement so that if important announcement is missed by a key player, someone is alerted and can reach out using an alternative method of communication. But even if you insist on misusing a chat protocol like IRC for this, ask someone who was there for their logs? I don't understand how nobody on your global team was able to even just summarize what you missed.
- j45 3y ago
  IRC bots literally maintained a history for anyone to catchup.
SV_BubbleTime 3y ago
That fair… but does that sound like a that called for a synchronous system? It seems someone chose the wrong thing, then you needed a history feature to bridge the gap.

j45 3y ago

This is a good point. Using chat as a source of truth is not a good idea Over time it becomes more and more ridiculous to use it as your knowledge base.

esafak 3y ago
Telling people to stop chatting is close to a nonstarter. You have to offer a better alternative.