@daniel

You seem to imply that we have to choose between:

- a safer space that has a strong CoC, a mediation process, wants to encourage diversity/inclusivity/plurality of opinions, wants to actively seek and include 2slgbtqia+ people in its decision making.

- an Organization that have/want none of these.

I would much rather have a community that knows a bit less of XMPP but will get better over time in a safe space.

@mjg59 @contrapunctus @thanius don't signal know all its users? how is the phone number to jabberd id mapping worse than what Signal has? Why do we have to insist everyone has to make the exact same privacy choices?

I know there are other things that Signal does better for less metadata collection, but I don't think the having the directory makes it worse than Signal.

#XMPP could be extended to collect less metadata as well. There are other social protections for metadata.

@thanius @mjg59 Look into #XMPP.

Projects like Quicksy and Prāv use phone numbers and allow easy onboarding and contact discovery. Unlike Signal, there’s no lock-in - you can choose other servers which don’t need a phone number, or host your own server (for which see Snikket, which allows for easy hosting of a private server, and provides rebranded clients and easy invitation-based onboarding), and still talk to Quicksy/Prāv users.

Servers on the XMPP network are also smaller and less convenient targets for backdoors, corporate takeovers, lawsuits, DDoS attacks, etc than the centralized servers of Signal etc. And since you can self-host it, you can actually trust that the server is running the code it has published.

For more information, please read The Quick and Easy Guide to XMPP. And if anybody is thinking of sharing any OMEMO FUD from a certain Signal fanboy…read this first.
http://moparisthebest.com/against-silos-signal/

@dushman @Linux #Signal is very secure. The #encryption is better than the one from #XMPP and the client #Molly even has additional database encryption. #Conversations is pretty nice and works with #UnifiedPush (I keep it as UP distributor for Molly) so I would probably switch to that if Signal went bad

@ex_06 Using delta with a variety of non-chatmail setups is just fine. It's only that #chatmail enforces end-to-end encryption and a cryptographic security baseline in server-to-server communications.

Given a dedicated small team of experienced devs, it might even be possible to re-use Delta's UIs and amend the core library to have an #XMPP backend and subsequently XMPP chat profiles.

But #Matrix? Are you seriously suggesting this?

@markus

There is no such thing as "neutral" or for "everyone" or "apolitical".

As communities and organizations we always choose who we want to include. For example:

- Include capitalist companies, to the exclusion of the community
- Some people have all the power, while people doing the work have none.
- male/tech-bro (often queerphobic) dominated culture to the exclusion of everybody else.

In JoinJabber we want to say openly who we include, not hide it

@BrodieOnLinux @qdot I find it weird to see #FLOSS #devs use an #InformationBlackhole like #discord which combines all the disadvantages of #MailingList, #IRC, #XMPP, #Matrix and even #MicrosoftTeams and #Signal without any redeeming qualities of any of those, like a functioning search & logging.

• Like the #LKML is kinda shit in terms of UX but at least there are searchable indexes for it so one can just point at a specific message & comment wthout having to be granted access to it.

Not to mention that discord is #ableist af by literally preventing the use of #Screenreader-friendly browsers such as #Lynx and #dillo to work, blocking @torproject / #Tor users and explicitly banning the use of it's #API to build better clients.

• Not even a #paid-for exception is offered, thus making integration into even paid-for tools like #HootSuite not legally possible!

@phosh

Mostly using #Phosh on a #LibreM5 running #Mobian #trixie lately but also a #PinePhone running #Mobian #bookworm (with a trixie era kernel).

About 95% or more using the #Dino #XMPP client.

Mostly with WiFi but occasionally cellular data. Never with cellular voice calls or text.

Had tried Chats ages ago but the #OMEMO support was unreliable and there was no offline support at all. Lack off offline support was a total deal breaker for me.

Love phosh a lot, many thanks!

We want to instead enable 2SLGBTQIA+ people to be directly involved by:
- create stuff that they need without needing approval from people that do not have their experience (most often cishet people)
- Block and/or reform proposals/features/documentation or anything else that is excluding them or makes it harder for them to exist
- advocate for things that benefit them by participating in decision making.

room is -> xmpp:2slgbtqia+@joinjabber.org?join

#xmpp #jabber #pride #pride2025

2/2

@fgntfg @tennoseremel As someone who uses XMPP as their only chat and calling medium, I beg to differ

Also, people are now quitting #Telegram because of their AI bullshit. Like any #centralized platform, it was bound to abuse its users sooner or later. #Federated protocols like #XMPP are the only sensible option.

I suggest you come and rediscover XMPP. Check out some good clients and servers -
https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html#getting-started

And find yourself some channels -
http://search.jabber.network/tags/

@delta For #Conversations_im I literally developed the UI first. I had a somewhat working UI before I was able to put a single #XMPP message on the wire.

A shared library between different platforms is a good thing. People are trying to do this in XMPP (Snikket SDK, Macaw, Prose) and if I were to start something new for Conversations I'd use something like Kotlin Multiplatform too.

However there is also value in diversity of implementations and the good ideas will prevail concept of XMPP.

@geekland

"Y lo más importante ¿era necesario ponerle un nombre tan feo?

#XMPP, antes llamado #Jabber (mira, si podía tener un nombre menos feo)…"

¡Así es!