3 ms·
> If you need real time there is IRC. The problem with IRC is that you cannot get chat history of a channel unless you configure a bouncer to do it for you. O
by u801e 9y ago
> If you need real time there is IRC.
The problem with IRC is that you cannot get chat history of a channel unless you configure a bouncer to do it for you. On that note, what's your opinion on XMPP? We used to use a XMPP server for internal company communication and the server was configured to replay the chat history to a client when it connected.
> Otherwise, just setup a mailing list.
That has a similar problem to IRC which is that new members cannot easily access messages sent before they joined. A better option would be an internally hosted NNTP server.
- davidw 9y agoChat is ephemeral for quick back and forth discussion. If you need history, maybe you should be using email anyway.
- u801e 9y agoPerhaps, but a lot of times, certain discussions take place over chat, and it's beneficial if someone who happens to join a little later in the conversation can simply read through the chat history to get up to speed rather than interrupting everyone to get some context to the conversation and proceed to ask questions about things that had already been discussed (rather than simply reading and getting the answers that way). Open protocols can certainly do this.
- anfilt 9y agoYou could do that as well with IRC. I like IRC since the protocol is so simple you could almost type in a raw telnet session live. That simplicity also means it's not to hard to add additional things to it. If you want.
- u801e 9y ago> You could do that as well with IRC. You mean replaying channel chat history on the server side without having to use a bouncer? > I like IRC since the protocol is so simple you could almost type in a raw telnet session live. That is true and it makes writing bots relatively easy. From what I've read about XMPP, it appears that most languages have libraries to abstract the XMPP protocol to make writing a bot easier.