Re:Why Slack is inappropriate for open source communications
by kuschku on Wednesday April 12, 2017 @12:20PM
(#14099161)
Recently I had a user ask for better support for large channels, in the IRC client I contribute to sometimes.
What is large, you might ask? 18'000 users in a channel.
And still it should feel and be as easily usable as a channel with 10 users, even via dialup.
That's the point where every byte that isn't used optimally becomes a problem. And where HTTP2 eith gzip or even brotli just isn't enough.
Where Java's IO is too slow, and you need to use the new native noncopying IO subsystem.
But I'll also be happy if, someday, we'll have a truly universal protocol for this.
In terms of the line protocol - we all agree that HTTP+JSON is an inefficient baseline for Matrix. It's just a matter of time for someone to propose a proper binary transport (although HTTP2+gzipped JSON really isn't that bad, and works fine on dialup speeds). Luckily this thread has prompted a few people to offer to contribute one though, so perhaps we'll see some progress there at last :)