Unknown parent

mastodon - Link to source

Daniel Gultsch

@tomjennings Chat Control has exceptions for closed, private deployments. For example Slack or Microsoft Teams won't have client side scanning. (That would be stupid and open the door for corporate espionage, and if anything is more important than the children it's capitalism).
Jabber/XMPP is just a series of private deployments that occasionally happen to be interconnected.
#Conversations_im is a client that can connect to closed, private deployments so it won't get client side scanning.
in reply to Daniel Gultsch

So is Signal and they are affected. My feeling is that to make it work they will make a 2.1 which moves it to the OS level. The EU surveillance proposals for 2029 already address device encryption as all key unlockable by Google/Apple, this will follow pretty quickly

Again, stopping chatcontrol for the millionth time is stupid, we need to stop the authoritarian government behind it

in reply to gvs

@gvs No, Signal is not used in private deployments. I guess you could technically run your own Signal server but I have not heard of anyone doing that and this is most certainly not as widespread as XMPP is in these deployments.
I mean there was #SignalGate but anyone who reported on that, who understood a little bit how these things usually work, made absolutely clear that Signal is not a thing commonly used by military and intelligence.
in reply to Daniel Gultsch

I wouldn't be so sure about that, after all, the way of implementing it hasn't been specified at all. To make sure the malware is even installed they'd either have to force all manufacturers to make it an integral system component or the mobile providers to not let you online unless your device responds to an encrypted ping for the app. Both would let them turn the trojan off explicitly for phones identifying as belonging to something cop-adjacent.