I wonder when (if?) orbital radio receiver arrays (a la starlink) are sensitive and discriminating enough to be used for this type of attack.
No, the "distributor" is the part which runs on your portable device, receives the push notifications, and wakes up the target apps as necessary.
Conversations can be a unified push distibutor: https://unifiedpush.org/users/distributors/conversations/
..and I'd trust it (battery-wise) with that. I have an old tablet with conversations running without battery restrictions on it, and if I'm not actually picking it up and using it it regularly goes 1-2 weeks on an 80% battery charge before it dies, the whole time giving audible notifications for XMPP messages/calls (which I attend to on other devices).
Apart from the pleasant one on the left, they're all the worst. The 4th from the right is almost good, but then you notice the creepy-as-fuck centre tine-gap length.
They're a little pricey I suppose, but judging by a few minutes comparing gumtree listings for hatchback cars and cargo bikes:
< 20% the cost of a hatchback in analogous condition/age/fanciness.
To be clear though: by E2EE here I mean browser-side encryption with zero-knowledge on the server side.
Etherpad is still encrypted in transit with https; only the server can snoop.
Cryptpad and other web-based E2EE services can still be completely compromised server-side by serving malicious code to the browser, and practically the user would never know.
Cryptpad:
Etherpad:
PrivateBin:
@tavu
@sopuli.xyz