writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

334
active users

#xmpp

43 posts35 participants0 posts today

What would be some good places to donate towards improving #XMPP stuff?

I'm mostly happy, but would like to donate to make sure I can continue to enjoy it all, but don't know where.

Replied in thread

@stubenhocker

#Messenger Apps mit #XMPP-Protokoll

Na ja, es ist ja nur ein Protokoll, genau wie das #ActivityPub protocol fürs Fediversum.

Das war mal überfällig--Übersicht über mögliche Apps:

eversten.net/blog/tabelle/

Ich vermute mal, die können auch alle miteinander komunizieren.

Mich würden die aktiven Nutzerzahlen interessieren, aber nachdem 95% der Apps nach dem 3. Monat nicht mehr genutzt werden...

"Messenger, die den offenen Standard xmpp.org verwenden."
@thevril @pluralistic @kino

eversten.netEntscheidungshilfe für XMPP Apps - eversten.net
Replied in thread

@Rgsharpe @jwz I kind of get using Signal if you think you're in a government's radar and want E2EE today and don't know anyone trustworthy to run an #XMPP server for you and don't mind sharing your phone number to a US company and some of its users ("least worst", as you said)

Since I have the privilege of not being in that situation, I'm instead supporting the open, federated, enshittification-resistant XMPP protocol so we can give ourselves comparable privacy and more besides😉

Prāv is always open for collaboration, and, at the risk of a somewhat premature announcement, we are happy to have received an expression of interest from possibly the most well-connected personality on the Fediverse!

We hope this potential partnership helps spread awareness about #XMPP to more corners of the Fediverse...once we have figured out how exactly to send a reply!

Replied in thread

@samueljohnson Glad you asked. Signal is a centralized service run on Big Tech infrastructure. You can decide to trust Signal as your service provider; That’s absolutely fine and reasonable even. But they don’t allow federation or inter-op with anyone who wants to make different choices.

#XMPP gives you that choice. Don’t trust me to be your server operator? That’s fine: pick a different one.

Donations to Signal are directly funding Amazon, Google and Microsoft.¹

¹: projects.propublica.org/nonpro

ProPublica · Signal Technology Foundation - Nonprofit ExplorerSince 2013, the IRS has released data culled from millions of nonprofit tax filings. Use this database to find organizations and see details like their executive compensation, revenue and expenses, as well as download tax filings going back as far as 2001.

Tangentially, I think I lean towards, there needs to be a new set of #XMPP RFC specs (can we call it XMPP 3 given that it's the third line of specs, or even a more friendly name¹?). Some XEPs need to be made standard, particularly service discovery, pubsub, and data-forms. (Personally I want to hold off on making MUCs the standard so that MIX can be used instead.) This new RFC set also needs to mandate encryption, define and offer probably MLS-based encryption, and recommend that unencrypted private messages are rejected by sending servers and dropped or rejected by receiving servers. Ideally someone needs to figure out some zero-trust shenanigans to minimize the metadata. Also mandate some form of TLS, channel binding, etc. Pick an extensible profile standard out of the many competing specs (preferably either vCard4 or User Profiles... and I think I'd prefer vCard4 since it reuses an existing standard). Basically modernize it, formalize lots of "final" XEPs into core parts of the spec, reduce conflicts between competing XEPs, stuff like that.

¹ some ideas: Universal Messaging Protocol/Standard (UMP/UMS), "The Messaging Protocol" with no acronym (MessProto?)... or even a clever acronym like Chat Handling and Transceiving (CHAT). Maybe even go back to Jabber somehow. Mostly because XMPP is a mouthful and immediately loses the less nerdy

RE:
infosec.town/notes/a6dnzjfwjl5l06cj

Infosec.TownBlake Leonard (@blake)All these competing "chat" protocols and standards make it so difficult to pick one and make my efforts have the most, best impact. As long as we don't pick Matrix, we'll be good. But holy shit we've got to pick one. We'll never win against Signal or WhatsApp or RCS while we're still so fractured and infighting. I can't even pick a side.

Looks like Dino is enabling #OMEMO by default for the next release¹. I think that was the last of the major #XMPP clients to do so. Hopefully we can now put the "But XMPP is not encrypted by default" debate to rest.

¹: github.com/dino/dino/commit/fc

GitHubSet OMEMO as default encryption · dino/dino@fc6447cModern XMPP ("Jabber") Chat Client using GTK/Vala. Contribute to dino/dino development by creating an account on GitHub.

You are encouraged to self-host #XMPP but you are not required to. We try to make self hosting as easy as possible. I think it is one step above hosting your own website but way easier than hosting your own e-mail.

If you are medium tech-savvy I recommend getting your own domain and going for an XMPP provider that let’s you bring your own domain (for example: account.conversations.im/domai) this gives you the flexibility to self host or switch providers later.

account.conversations.imJabber/XMPP Domain HostingLet us host your Jabber/XMPP domain for you. Convenient webinferface. Available within 24 hours. Hosting starts at 12 Euro/year
@jwz has some thoughts on #Signal and I think he is right. Nice Logo, btw :)

jwz schrieb den folgenden Beitrag Tue, 08 Apr 2025 22:07:51 +0200
Because of the ongoing fucktastrophe, the cries of "Use SIGNAL!" are constant and unavoidable. And I get it, it may be the least-bad option in a sea of terrible options. If, that is, you choose to ignore the advice of "don't use your phone for that shit" (the Stringer Bell Rule).

But out of curiosity, because I haven't been keeping up, has the Signal Corporation addressed: ...

https://jwz.org/b/ykmD


What he addresses are these points:
  1. cryptocurrency (ponzi scheme)
  2. no third-party implementations
  3. no usage without telephone number
  4. sharing name and phone number with every contact in your address book
  5. no reproducible builds on apple devices


So, what kind of messengers do we have. Let's take a look at Mike Kuketz' Messenger Matrix. This list recommends seven menssengers.

Let's see how many are left when we include jwz's points:
  • Briar
  • Conversations (XMPP, Android)
  • Element (Matrix)
  • Line
  • Monal (XMPP, iOS)
  • Signal
  • Threema


This leaves us with #Briar and #XMPP.
Does anyone use Conversations (Android #XMPP client) as Unified Push distributor with Schildi Matrix client?
I've set up mod_unified_push on Prosody and it seems to work — all tests in notification troubleshooting pass and the notifications themselves arrive just fine. Problem is, every time I open Schildi, it seems to re-register the receiver making a new push URL. The notifications still arrive, but by the end of the day I have like 20 HTTP pushers and I have to delete old ones from time to time.

Am I doing something wrong or is it just buggy? Nothing like that ever happened to me when I was using ntfy.

I'm putting the finishing touches on a massive release of the Converse #XMPP chat client. 🚀

✨ Here’s what to look forward to:

◾ Groupchat DMs: You can DM other participants without knowing their address
◾ Blocklists for spammers 💩
◾ Accessibility improvements, like support for RTL languages
◾ Media enhancements
◾Big performance enhancements, particularly for chats with a long history and many participants.
◾Three new themes, Nordic 🗻 , Dracula 🧛‍♂️ and Cyberpunk 🌆