Forget warn apps and mobiles: when it comes to neighborhoods there are many non-digital ways to help each other. Without needing permission from billionaires. Whistles!
While #chatcontrol poses an existential threat to the Freiburg merlinux GmbH and distributing #deltachat apps from within the EU to all stores worldwide, it would resist any chatcontrol legislation up to the German constitutional and EuGH courts. If the EU based company would need to fold in a few years, there would likely be forks distributed outside the EU that will *seamlessly* continue to function. Our architecture and FOSS licensing makes sure of it. See also
#chatcontrol is a giant legal-technical quagmire and would erode privacy in times where we most need it. But let's talk about protecting children ... what chatcontrol claims to be about: First, it's unproven that chatcontrol would help lower actual abuses. Second, why not spend the many EU millions that go into busying politicians, developers, lawyers and orgs into hiring social workers? They could directly act on the huge backlog of _reported known_ child abuse cases. That definitely helps.
There now is a recording of the ad-hoc #datenspuren "usable end-to-end" talk from friday evening, german audio only
The problem with #chatcontrol is deep and extremely significant. It would be a paradigm shift that implies state and corporate control of app developers and users, i.e. what you can install on "your" devices. It would empower Google, Apple and Microsoft to increase enclosure even more. Just as with the p2p wealth of good tools two decades ago, e2e tooling would remain available only to small specialist circles. Given authoritarian threats everywhere, #chatcontrol is an exceptionally bad idea.
What if a state tries to mandate us as #deltachat app devs/distributors to shut down a chat profile? Nothing. It can't be done. We have no list of chat identities, have no handle or data about them, and don't mediate the message transfer. However, EU #Chatcontrol politicians and Russian authorities would want us to insert backdoors into our FOSS code. But that is nothing than can happen overnight, and we are fine with friendly forks already. Resilient private internet communication ftw :)
Woah! Only now did we discover a great blog post from @npub12hxm...n282 who discusses the progression from hosting a #Matrix , a #Snikket and a #SimpleX server, to now running a #chatmail relay It's an excellent read, with lots of good advise, including having a public "hello" profile and another unpublished chat profile for private chatting. #deltachat apps have pervasive multi-profile support (and multi-device support) so it's pretty easy to establish such a two-profile setup.
#deltachat is being used in virtually all world regions where one or more other messengers fail to work. We recently released a major milestone (V2 security hardening releases) that prepared the ground for chat profiles to have multiple #chatmail relays at once ... failure or blocking of a single relay would not disrupt chatting anymore. But multi transport also helps with the "centralization problem in decentralized systems" ... (Funding is looking good currently btw!)
Sometimes we are surprised ourselves how well everything works :) - cross-platform #deltachat releases every 2-3 months, with a focus on never breaking the world despite significant underlying changes - many #chatmail relays humming along, including the default onboarding one serving 230K monthly users with ~0 admin hours needed -lively and sometimes controversial discussions among the diverse dozen core contributors, with an evolving shared vision, both short and long term Toi Toi Toi
#Whatsapp on #iOS had a severe 0day that was exploited in the wild for some months, and is fixed with august 20th releases Last year #signal also had its multi-device functionality exploited in the wild. FWIW #deltachat has a dumber multi-device sync model, no device linking, depends on being in the same WiFI for setup (therefore no easy remote exploits), and #OpenPGP signatures and verification for ongoing usage (like all other E2EE messages).