Snikket

ℹ️ A note to any Snikket self-hosters who use #Caddy as a reverse proxy in front of Snikket:

A recent Caddy point release (v2.11.1) has changed the default behaviour of the headers that it sends to upstream servers. You will need to update your Caddy configuration to include a header_up directive for Snikket, otherwise you'll see a message: "The web address you entered does not seem to match the domain of your Snikket installation."

Find the correct config at: https://snikket.org/service/help/advanced/reverse_proxy/#caddy

We're investigating reports of problems for Snikket iOS users connecting to Snikket instances. This is a problem with the app, so it is affecting both hosted and self-hosted instances.

We're working on a resolution 👷

By the power of XMPP interoperability, if your device is affected by this issue you can install the Monal app from the app store and use that to access your Snikket account (same credentials).

Apologies to anyone affected by this issue. More updates will follow!

Looking forward to meeting folk at #FOSDEM in Brussels this weekend!

Whether you're an existing Snikket user and want to say hi, curious to learn more about Snikket, or need help with setting up your instance, come and see us on Level 1 of the AW building on Saturday and Sunday 🙂

Among other things, the upcoming release of our Android app will feature an updated design. More info on our blog!

https://snikket.org/blog/snikket-android-material/

@km@mastodon.babb.no
Thanks for the offer! We managed to purchase one (used) and it's still going well 🙂

@pertho@mastodon.bsd.cafe
Unusual! Snikket usually compares favourably to other messaging apps in terms of resource and power usage.

Was it connected to a Snikket server? Some third-party XMPP servers may lack some of the traffic optimizations that Snikket uses.

If you ever try Snikket again and can still reproduce this issue, do give us a shout!
@neil@mastodon.neilzone.co.uk