What's the downside to #selfhosting all the things?
What's the downside to #selfhosting all the things?
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/
https://homebrewserver.club/have-you-considered-the-alternative.html
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)
#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
@mastodonmigration Obligatory reminder that #Signal relies on a centralized and proprietary server, and does not belong here.
Users of #WhatsApp #Telegram #Discord #Signal and #Threema etc should use #XMPP instead, which is #FreeSoftware and federated.
Users - check out #Quicksy (Android and iOS), #Prav, #Conversations, #Cheogram, #MonoclesChat, #Gajim, #Movim, #Monal...
Self-hosters, check out #Snikket.
Learn more with this user's guide -
https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html
@TMakarios @maple @mastodonmigration @snikket_im Myself, I'd be interested in a self-hosted #snikket server if it were *not* offered as a #docker container. I'd like to run it/prototype it on a #RaspberryPi, as in ARM64/aarch64, on plain-Jane Raspberry Pi OS (#Debian-based). Installable from, say, extrepo would be great (like #Librewolf is these days). Or maybe included in official Debian 13 before the upcoming package freeze? That's asking a lot, I know. #XMPP
@maple @mastodonmigration
I imagine most people who want the easy path, and don't care about centralized silos, will probably stick with WhatsApp.
These days, thanks to @snikket_im , there's a pretty simple app for both Android and iOS, with end-to-end encryption on by default. And they've put a lot of work into making it easy to host your own Snikket server, and give easy invitations to your friends to download the app and get an account on your server. There's a paid hosting option, as well as a docker container. Not everyone will be able to self-host a Snikket server, but I don't think you need to be an ultra geek any more.
Gillar du att snacka om Linux, teknik och/eller lite allt möjligt som berör livet i största allmänhet?
Kom då och gör oss sällskap på Linuxkompis publika gruppchatt på Snikket!
xmpp:linuxkompis@groups.snikket.linuxkompis.se?join
Har du inget konto på Snikket (eller XMPP) tillhandahåller Linuxkompis konton till alla som är intresserad. Hojta till om du vill ha en inbjudan!
Om du inte har en susning om vad Snikket är, kan du läsa den här gamla artikeln som jag skrev för flera år sedan, och som jag förmodligen behöver ge lite ny kärlek.
https://linuxkompis.se/2021/12/16/en-introduktion-till-snikket.html
@Etche_homo
They’re both garbage. And both exclusive. Switch them to #Snikket.
@amy @karmalakas
@rysiek @kkarhan @agturcz An awful lot of people say they've used #XMPP "a while back". But they're often unaware of the best of XMPP, and have an unfairly negative view of it.
Did you happen to try...
...#Snikket for hosting?
https://snikket.org
...apps like #Quicksy and #Prav which use phone numbers for easy onboarding, same as #Signal #WhatsApp or #Telegram?
https://quicksy.im
https://prav.app
...featureful clients like #Cheogram #MonoclesChat #Gajim #Movim etc?
@karmalakas @sylv_a I’ve put the old folks I need to reach on #Snikket. It uses decentralised open standards ( #XMPP #omemo).
Many xmpp apps are glitchy but Snikket is functional enough. I think one of my contacts has problems getting notifications on their iPhone w/Snikket. But it’s tolerable.
I wrote a blog post on setting up #Prosody #XMPP server on #Debian 12, Bookworm.
Most people should probably just stick with #Snikket, but for those who would prefer to go the manual setup route hopefully this will be of interest or help.
https://blog.hetherington.uk/2024/12/setting-up-xmpp-prosody-on-debian-bookworm/
@chuck@linuxlab.sh @fabio@manganiello.social @Menel@nerdculture.de
Don't think I heard of #Snikket yet, I should check it out. When I set up #XMPP again I want it to run on my Kubernetes cluster, since that's where most things already live anyway. I also want to be able to have bridges to other platforms that I use, such as #Signal and (sadly) #Matrix, so I can have one good client for all my chat again, like we had back in the Ol' Days.
After a long time, the #xmpp server #prosody released its next stable version 0.12. It was time well spend, there is a big leap in features, just to pick one, I want to highlight the invite system. Known from the sister project #snikket.org. Simple onboarding! https://blog.prosody.im/great-invitations/ But see for yourself all the other features that make it even easier then before to selfhost a good decentralized chat software, that is as extendable as the protocol itself. https://blog.prosody.im/prosody-0.12.0-released/