Those of you who have to work through Google, Apple and other store's compliance, we feel you! Maintaining around 16+ target distribution sites for cross platform apps takes a constant toll on us. One of the giant features of #webxdc app developments is precisely that no store is needed. You can just write an index.html, a .js file and pack into a zip file and everyone can use this as an app in their chats, no store needed for permission and distribution.

Get Started - Webxdc

We just boosted a report from someone (we don't know) summarizing and reporting about recent court happenings in Moscow against us. We confirm these legal proceedings are indeed happening and we are represented by a lawyer there ...

Wet-Dry World

jan Anja(); (@cybertailor@wetdry.world)

What have I learned from "#DeltaChat v. Roskomnadzor" case: it's illegal to develop e-mail clients in Russia :neocat_thinking: RE: https://craba....

There are rumours that a theater play work-titled "how to arrest a protocol?" will be presented at #38c3 btw :)

Are you interested in enshittification-resistant application development? After almost two years of collaboration with the wonderful @iroh team, we are happy to announce that #deltachat 1.48 apps on all platforms contain top-notch Peer-to-Peer networking support, including hole-punching and forward-secret end-to-end encryption. It is exposed through the new #webxdc realtime APIs and there are some nice initial showcase apps 🎉

Delta Chat: Delta Chat introduces realtime Peer-to-Peer networking

Are you interested in enshittification-resistant application development? After almost two years of collaboration with the wonderful Iroh team, and...

With our #deltachat #chatmail and #webxdc efforts we put all intelligence on the end devices, and architecutally separate it from a transport layer that routes safely and fast but knows nothing. There are a dozen or more #chatmail servers across many jurisdictions, all safely interopable with each other and classic servers. Turned out we can dumb down email servers by relying on cryptography instead of IP reputation and ai/spam filtering. And have 200ms delivery times. We are not done :)

Working based on interoperable specifications is value to users and developers. Development teams get the freedom to exchange component implementations which is beneficial to the user. Other developers can team up to replace a whole tool or app with another interoperable one, providing a second level of "freedom to exit". Its true for #activitypub and is true for our e-mail Standards and #openpgp based end-to-end encryption. Protocols are the fundamental source to provide freedom of exit.

@npub1s537...6xm4 OAuth2 is not supported anymore. You can follow the instructions at

Gmail - Provider Info

to reconfigure the account using app passwords.

Preventing enshittificatiom with the "Ulysses pact" from @npub1fdrp...lvhs

Pluralistic: Bluesky and enshittification (02 Nov 2024) – Pluralistic: Daily links from Cory Doctorow

We consider our efforts aligned: #deltachat #chatmail and #webxdc implement "right to exit" on all levels of our decentralized messaging project. - deploy your own servers permission free and interoperable with all e-mail servers ("federation mast") - all apps and libraries and server components are 100% Foss - interactive chat-shared web-apps can be used in other messengers #righttoexit

Running #chatmail servers is <2h effort per month, according to an ad-hoc poll with 10 operators responding. Some have 10Ks of #deltachat users. Typically 300MB ram is used and max 60gb disc space per server. And all interoperate safely based on high security standards (DKIM and TLS enforced, and only no-metadata #openpgp encrypted messages allowed) .... with typically 0.5 secs end-to-end delivery. Who said again that email is insecure, cumbersome and slow? :)

Maybe the secret why the #deltachat project with "just" a dozen active contributors succeeds in delivering cross-platform apps, instigating the chatmail server network and spearheading the webxdc-app paradigm, lies in asking the right questions: - Is it really needed? - Can we not do it? - Is there a simpler way that requires less changes? - What is the interesting next impl step that is already interesting itself for users, without requiring first completing a big refactoring project?