Post B1uNoEGAwbkSGIbCO8 by masoud@persadon.com
 (DIR) More posts by masoud@persadon.com
 (DIR) Post #B1uNnfSiJzyuL3CDZY by daniel@gultsch.social
       2026-01-03T12:34:20Z
       
       0 likes, 1 repeats
       
       I think #XMPP has a relatively clear and achievable path to drastically reduce the amount of metadata, but I’m increasingly worried that it is not going to move the needle in terms of adoption.For 99.99% of people, the only relevant feature for an instant messenger is simply 'Are my friends using it?' The other 0.01% are equally divided between people who already use XMPP and don’t mind the metadata, and people who won’t use it anyway.#Jabber #Conversations_im
       
 (DIR) Post #B1uNoEGAwbkSGIbCO8 by masoud@persadon.com
       2026-01-03T12:42:46Z
       
       0 likes, 0 repeats
       
       @daniel Very interesting! May I ask, what this "relatively clear and achievable path" is? Does it already have a XEP? Is it implemented by any project? Is there any plan?
       
 (DIR) Post #B1uNoF97eJhV0iJ528 by daniel@gultsch.social
       2026-01-03T12:49:04Z
       
       0 likes, 1 repeats
       
       To anyone curious about the technical details:• Go roster-less. I seriously considered that for Quicksy. You basically just do it.• Per device offline queue. With SASL2 the server knows what devices a users has. Discard messages once you know every device has received them.• Sealed sender. With SASL anonymous and PEP we have some good building blocks for that. Basically just have to come up with semantics of which key pairs go where.• Stanza Content Encryption with MLS or OMEMO@masoud