Hacker News Reader

Comment by lrae | Hacker News Reader

Yes.

Chat Control 2.0 was the big one in those regards.

(Also, LOL @ Skype mention.)

Then I'm not very moved about this. I always assumed that anything unencrypted is scanned one way or another. What I care is not having a backdoor for E2E, i.e. like client-side scanning telling me what I am allowed to talk about like with the LLMs. CSAM excuse is a great excuse to turn every conversation to what we have with AI today.

And the temperature of the frog pot rises by one degree.

I assume the same, but not because it’s sanctioned. Sanctioning is a slippery slope or a degree change as has been mentioned.

If reading messages that are not for ones eyes is OK, then it is a much smaller step to the next level, which is to also being able to read encrypted messages. Slowly boiling the frog.

But the next level IS the chat control 2.0 and yes it is the one people should be concerned about. But it's not like this is unprecedented this is literally just an extension of something that existed.

> I always assumed that anything unencrypted is scanned one way or another

By this logic, I should be happy if mail delivered to my address always arrives already open.

Don't downplay Skype, as Teams is still just rebranded Skype for Business (LYNC).

Are my AIM chats safe?! /s

You kid, but there are still some active AIM users (or at least, a revival of it)

You should be using AIM OTR: https://otr.cypherpunks.ca/

Adding to this there is pidgin-otr and python-potr.

For IRC there is irssi-otr. There was weechat-otr but I think it may have gone unsupported as their script did not work in python3.

There is also ejabberd [0] that has OMEMO [1] preferred over OTR and PGP and supports many to many E2EE.

Someone tried to MitM Jabber, discussion here on HN [2].

[0] - https://ejabberd.im/

[1] - https://en.wikipedia.org/wiki/OMEMO

[2] - https://news.ycombinator.com/item?id=37955264

Reply on news.ycombinator.com