4 ms·
Because as owners of the server and/or channel you are free to implement a protocol on top of it. On Discord and Slack you do not have such liberty. Heck, Slack
by Fnoord 7y ago
Because as owners of the server and/or channel you are free to implement a protocol on top of it. On Discord and Slack you do not have such liberty. Heck, Slack killed IRC gateway.
- dmitriid 7y agoAgain Back to this statement: > What I'm not fine with is being forced to use Slack for work-related material. You don't want such sensitive data centralized. You want to host such yourself The moment you use IRCCloud all that sensitive data is on IRCCloud’s servers. How does “building a protocol in top of that (on top if what?)” help?
- Fnoord 7y agoThe point is that those who own the channel and/or server can enforce E2EE. They own the data. Its also possible someone on an IRC client is running a compromised server. Then you're also back to square one. Given we're talking in circles I'll withdraw from this discussion.
- dmitriid 7y agoHow can they enforce E2EE if IRC protocol doesn’t support it? How can they enforce E2EE if very few if any IRC clients support it? What good does “owning the data” do if the data ends up on IRCCloud’s servers anyway (companies who use Slack also own their data). It’s quite telling that people have such a strong belief in the magic of protocols.