![](/static/61a827a1/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
Pidgin is a client, not a specific protocol.
Pidgin is a client, not a specific protocol.
And they’re not going to leave WhatsApp for Sup? either. All I’m saying is we’ve had an alternative for decades, even before WA was created, we don’t need another one, we need the one we already have to have more success.
People act like we need an alternative to Whatsapp but XMPP/Jabber exists and is much older.
Searxng is very good, I like it a lot. As for OSM, I didn’t even know it could be hosted.
Prosody (XMPP server), a git instance, a searXNG instance, Tandoor (recipe manager), Next Cloud, Syncthing for my phone and my partner’s (one could say Next Cloud should be enough but I use it for different purposes), and a few other stuff.
It doesn’t even use an eight of its total RAM and I’ve never seen the CPU go past 20℅. But it uses a lot less power than the thin client it replaced so not a bad investment, especially considering its price.
My first @home server was an old defective iMac G3 but it did the job (and then died for good) A while back, I got a RP3 and then a small thin client with some small AMD CPU. They (barely) got the job done.
I replaced them with an HP EliteDesk G2 micro with a i5-6500T. I don’t know what to do with the extra power.
Fun fact, Google Talk and Facebook used to be compatible with XMPP.