and a way for the two clients to negotiate capabilities so they aren't forced to just be identicalWhy is everyone SO obsessed with trying to build a messenger ecosystem with asymmetric features/capabilities?! What a total shit show that is for everyone -- developers and users
My ESP32 controller doesn't run JavaScript, so can't participate in Deltachat Apps.then all it has to do is ignore the messages related to it, they won't harm it
Or for my app not to waste all of my mobile data because my cousin sent 54 photos to the family group.Already possible to disable automatic attachment downloads in the Delta Chat app
QXmpp if you like QTIsn't that the meme KDE XMPP library that Kaidan uses and supports none of the OMEMO versions everyone else actually uses?
What does OMEMO file attachments that the existing file transfer over HTTPS doesn't give you?The server having no idea what the contents of the file is. What's the point of an encrypted chat when you can leak valuable metadata by accidentally uploading an unencrypted attachment over an encrypted HTTP connection.
I've never even heard of conversations. Nobody I know uses it; we're all Monal or Siskin.It's the only usable XMPP client on Android. Almost every other XMPP client on Android is forked from it.
1
Pleroma and gnusocial will say they're going to implement it, but never will, eventually leaving it up to Akoma.hey, get it right: Pleroma will never implement it because we experimented with it years ago and decided it's wrong and unfit for the fediverse :)
Pleroma and gnusocial will say they're going to implement it, but never will, eventually leaving it up to Akoma.There are Pleroma Chats, so that could be used as some baseline, but chats and that spec aren't really compatible last time I looked. And my view is that there are already better ways for E2EE chats than the fediverse. You get identity isolation as a "bonus" and there's no X protocols + 1 competing over the same thing.
Mastodon will implement something shaped like it, but use entirely different encryption and key formats.Mastodon actually got a grant approved to implement that unfinished spec, so the ActivityPub thing will probably be happening again. Where Mastodon is actually what defines the spec.
so the ActivityPub thing will probably be happening again. Where Mastodon is actually what defines the spec.yeah remember when the AP WG recognized Pleroma was a major contributor to the fediverse and invited us to be stakeholders and asked us for input on important far-reaching issues and proposed changes to the entire fediverse? Ahh wait that never happened they just ignore us and it's not worth any of our time to try to force our way in and argue just to be told "well Mastodon is doing it this way anyway, so that's the spec now"
