#Snikket is currently working with folk from Superbloom, who specialize in UI/UX design. Part of the project will involve usability testing. For this they need participation from people who (will be?) using Snikket. If you think you would be able to help out, please fill in this form and also share it to others: https://my.liberaforms.org/snikket-2025-usability-study

In other news, my tiny self-hosted #XMPP #Jabber server using #Snikket is now 100% compliant with the #Conversations compliance test!
Out of the box Snikket basically gives you 95% compliance, with it "just" missing out on XMPP over TLS. Their documentation on this is rather lacking, so it took some fiddling to get it working.
Overall Snikket is quite nice. But I don't like how it seemingly goes out of its way to not call itself XMPP/Jabber. Isn't that just confusing?
https://compliance.conversations.im/server/tofu.im/

My #lineageos v21 Pixel 5 with GApps installed stopped receiving many push notifications a few months ago. Recently, I've started to use #xmpp #snikket for private messaging and I noticed calls weren't working reliably on my device and it matched the pattern for when push notifications weren't working. After trying an upgrade to LOS v22 and a few other things, I found an app FCM toolbox https://play.google.com/store/apps/details?id=fr.smarquis.fcm that featured a troubleshooting log mentioning a VPN error...

What's the downside to #selfhosting all the things?

• #Nextcloud
• #Pleroma
• #WordPress
• NAS
• Mail
• #Jellyfin
• #Forgejo
• #Snikket #XMPP

The Internet and the web were born open, then closed walls were built in the name of profit and user convenience. It's time we leave the closed walls behind and go back to how the Internet was supposed to be: a collection of independent applications using common protocols.

https://snikket.org/blog/products-vs-protocols/

If I run `lsof -i -P -n | grep LISTEN`, should I see ports listening from a #Docker container? I'm trying to get a #Snikket container up and running using a reverse proxy, but having some trouble and I'm trying to figure out what's going wrong here. I followed the reverse proxy instructions for #Apache, but when I enable the site Apache is failing even though the config check says syntax is ok. I'm not seeing the configured ports from the Snikket config listening.

#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?

My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*

So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.

Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": https://gultsch.social/@daniel/114012904576436518

It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird

Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".

(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)

Ich möchte mein XMPP-Setup von Yunohost trennen. Also erstmal ab ins Rabbit Hole und zwischen #Snikket, #Prosidy und #ejabbered entscheiden.

Estic intentant muntar un servidor de missatgeria xmpp (en servidor cloud debian). He provat #prosody, amb #Snikket, amb #eJabberd... Seguint les passes que indiquen a les seves webs sembla que s'instal·len correctament però les aplicacions (tipus Conversations) no troben aquests servidors xmpp quan intento connectar-hi.

Em podeu recomanar algun recurs (per novells!) per aprendre conceptes bàsics de servidors en general (ports, certificats, nginx...) i/o xmpp?
Gràcies!
#ajuda #servidors #xmpp

Alguien usa #Snikket como cliente #XMPP en Android?

Two years today with #grapheneos on a refurbished Pixel 6 Pro at the lowest price I've paid for a phone since they stopped GIVING them to you with a 2yr plan. With GOS, #jmp, and #snikket, the previously most insecure and expensive device in the house is the most secure and inexpensive. Including donations to the great apps I've installed with #obtanium!

I was just gifted an old iPad and it's a stark contrast with a device that provides top security without preventing you from doing ANYTHING.

#Prav project started 3 years ago with the goal of mass adoption of private messaging powered by #XMPP and democratic decision-making. The project was inspired by #Quicksy and #Snikket.

Read more at https://ravidwivedi.in/posts/backstory-behind-prav-app-project/

Today, I am glad to announce our first edition of #PravConf in #Kochi, #India. Join us on the 1st and the 2nd of March.

Don't forget to spread the word

More details at https://conf.prav.app

@snikket_im A group of friends, neighbours and I have been testing #Snikket lately, and it's been pretty successful! Thanks for all the great work you've been doing

Our Snikket instance is on a Debian VPS, we'd like to go a step further by having a new instance installed locally.

But we've noticed that we cannot 100% self-host as you're managing the push notification service: https://snikket.org/app/privacy/

Not a deal breaker, but is there a way to work around this, or to have our own service?