3 ms·
Not making a judgement call on Discord, but I'd argue that all communication for free software projects should be public and unencrypted.
by paxys 7y ago
Not making a judgement call on Discord, but I'd argue that all communication for free software projects should be public and unencrypted.
- stkdump 7y agoWhat about security bugs? Don't you need at least a secure way to discuss them?
- paxys 7y agoExpecially security bugs. Communication can be hidden during the remediation period, but there's no reason for them to not be made public immediately after.
- t-writescode 7y agoSo then there is a reason to have communication be private, as you said.
- dependenttypes 7y agoI would argue that even then it should be public. Forks exist and everyone can have one (even if it is for private use). For all we know the maintainer of the "original" could be a hostile actor.
- chungy 7y agoEncryption is kind of moot. Every IRC server has been behind SSL/TLS for a very long time and it doesn't prevent usage nor archives.
- paxys 7y agoThe core argument in the article is that such systems aren't E2E encrypted.
- cooljacob204 7y agoSo the same as IRC.
- diath 7y agoI agree that IRC encryption is kind of moot, the issue with IRC is that most channels usually don't enforce SSL-only clients, meaning that you have both encrypted and unencrypted traffic going through, effectively making it unencrypted altogether as all it takes is snooping on a single unencrypted client. It's a shame too, honestly with Let's Encrypt being a thing nowadays I feel like IRC networks should be SSL only.