Regarding encryption of the push message, from https://unifiedpush.org/developers/spec/android/ :
Push message: This is an array of bytes (ByteArray) sent by the application server to the push server. The distributor sends this message to the end user application. It MUST be the raw POST data received by the push server (or the rewrite proxy if present). The message MUST be an encrypted content that follows RFC8291. Its size is between 1 and 4096 bytes (inclusive).
That rules it out for me then. I like to use XMPP+OMEMO with about 4-5 clients which I can continue a conversation with at any time. Main mobile, tablet, desktop, other desktop, and backup mobile which is usually switched off. (Even if a device has been missing for too long and run out of OMEMO keys, the keys sync up again once I send a message with it.)
You have to trust the servers with your metadata, and that the servers have their inter-server communication locked down, but at least you can choose/operate servers.
Some clients are a bit flaky with their e2e encryption defaults or from a UI perspective it is easy to send an unencrypted message (in a new chat for example) before noticing that was how it was set.
There are a few XEPs the server needs which enable things like OMEMO, efficient mobile data/battery use, offline and multiple device deliverability, file transfers, etc. Audio/video calling has various requirements as I think xmpp only facilitates the setup of the call.
Munin feels a little old and crusty, but just works. Over 20 years old now.
XMPP lacks good clients and suffers from fragmentation of protocol standards implementation
“Protocol fragmentation” is not a valid complaint about XMPP – it’s like complaining that ActivityPub is fragmented; but that’s not a problem: you use the services (Mastodon, Lemmy, Kbin, etc) built with it which suit your needs, mostly interacting with that sector of the federation (eg, Lemmy+Kbin), but get a little interoperability with other sectors as a bonus (eg, Lemmy+Mastodon).
🤔
deleted by creator
Most
people1, even in this very thread, clearly don’t […]
deleted by creator
deleted by creator
deleted by creator
Oh, I agree. I don’t think it’s a particularly useful reference page – more of a biased agglomeration on a substrate of preconceived opinion, but the initial pile-on of downvotes without comments felt a bit like the usual Mozilla-fanaticism.
I tend to upvote posts not because I agree with them, but because I’m interested in people’s responses to the ideas within them.
So many downvotes…
I’m only about 10% in (and just skimming), and it’s a rant but it’s coherent and well-reasoned.
Starts off as a dive into Mozilla’s rank hypocrisy and doublespeak around privacy.
If that’s the main problem then that’s easy to solve! Simply use a free public xmpp server.
I mention the self- and paid-hosting options because businesses tend to like having a sevice agreement backed by a contract, and may have additional specialised requirements not provided by free services (xmpp or otherwise).
XMPP. A business can self-host, there are public servers, or there are many businesses which offer customised xmpp hosting as a service.
I can be federated with other xmpp servers or be a locked-down work-only service, or federate with chosen other servers (such as a client company’s xmpp servers).
An excellent discrete maths textbook for those missing the inclusion of the subject in the course: Discrete Mathematics - An Open Introduction, 3rd edition by Oscar Levin
Arkenfox is a tool to assist setting up stock Firefox.
“Current AI models cannot forget data they were trained on, even if the data was later removed from the training data set,” Han’s report said.
Bullshit. You delete the entire model and start again.
x.x.x.x))<ICMP>((1.1.1.1
I think a lot of comments have missed that ntfy.sh does not use UnifiedPush, the ntfy server is a UnifiedPush provider and the ntfy app is a UnifiedPush distributor.