4 ms·
Offline messages is a server issue, though - in principle there's no reason why you couldn't have a server that remembers offline messages and passes them to th
by caf 11y ago
Offline messages is a server issue, though - in principle there's no reason why you couldn't have a server that remembers offline messages and passes them to the client when it reconnects, framing them as regular IRC messages.
- scrollaway 11y agoThere is, actually. IRC has no concept of timestamps. IRC has no concept of foreign metadata, even, so shoehorning isn't even possible without looking horrible. IRCv3 fixes all that.
- caf 11y agoPrefixing a date/timestamp unless the client has asked for IRCv3 timestamps is reasonable.
- Sanddancer 11y agoYep. This is how slack does it, least for their xmpp gateway. I imagine that their irc gateway is similar.
- scrollaway 11y agoAnd now, you just broke essentially all clients that already support channel logs by duplicating anything they already had. This is a problem bouncers are already solving best they can, and it still sucks. It's not good enough to compete with slack.
- caf 11y agoChannel logs is a marginal, client issue, not a protocol issue. Does anyone do client-side logging on any of these other services that do server-side message history? I didn't say anything about competing with slack.