News for hackers. Stuff that matters.

A comment on Open Sourcers Race to Build Better Versions of Slack. Parent comment

Re:Open Sourcers Race to Build Better Versions of Slack by caf on Wednesday March 16, 2016 @08:54PM (#11301896)
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.
[ Parent | on HN ]
Re:Open Sourcers Race to Build Better Versions of Slack by scrollaway on Wednesday March 16, 2016 @09:46PM (#11302078)
There 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.

[ Parent | on HN ]
Re:Open Sourcers Race to Build Better Versions of Slack by caf on Wednesday March 16, 2016 @10:14PM (#11302163)
Prefixing a date/timestamp unless the client has asked for IRCv3 timestamps is reasonable.
[ Parent | on HN ]
Re:Open Sourcers Race to Build Better Versions of Slack by scrollaway on Thursday March 17, 2016 @09:47AM (#11304277)
And 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.

[ Parent | on HN ]
Re:Open Sourcers Race to Build Better Versions of Slack by caf on Thursday March 17, 2016 @07:29PM (#11308519)
Channel 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.

[ Parent | on HN ]
Re:Open Sourcers Race to Build Better Versions of Slack by Sanddancer on Thursday March 17, 2016 @02:22AM (#11302855)
Yep. This is how slack does it, least for their xmpp gateway. I imagine that their irc gateway is similar.
[ Parent | on HN ]