←back to thread

89 points rw_grim | 2 comments | | HN request time: 0s | source
Show context
nicoco ◴[] No.42212713[source]
It's nice to see pidgin still alive and kicking!

I hate to have different apps for similar stuff and I also prefer "native" clients over web UIs so I used pidgin a lot in my life. I impressed many people with its "telepathic" feature that would open a chat when someone starts typing, to let you type in something before they even finish their initial sentence. Fun times…

However, when I finally got a smartphone, and started a more conventional line of work which came with extra devices, I switched to grouping my chats using server-side gateways for better multi-device consistency. I started by using Spectrum [1] which leverages on libpurple (pidgin's "backend") to do that. Since spectrum is on life support (maintenance mode, no modern chat features like emoji reactions which I happen to like despite my old age), I actually started my own hobby project [2], because I'm not really interested in learning C++ (which spectrum is written in). (shameless plug, I know)

The hype these days is more around mautrix [3], but the permacomputing enthusiasth in me prefers XMPP over Matrix. I'm not that religious about it though, my gateway project includes the most feature-rich XMPP/Matrix gateway out there [4] which I try to improve and maintain when time and motivation allow it. Unfortunately, XMPP support in pidgin has historically been pretty poor and IMHO partly responsible for some of the hate XMPP gets. I'm not blaming the pidgin devs of course, I should contribute to libpurple-xmpp (if that's how it's called) instead of complaining. ^^

[1] https://spectrum.im/ [2] https://sr.ht/~nicoco/slidge [3] https://github.com/mautrix/ [4] https://git.sr.ht/~nicoco/matridge

replies(1): >>42213482 #
1. Arathorn ◴[] No.42213482[source]
what is more permacomputingy about xmpp than matrix, ooi?
replies(1): >>42213815 #
2. nicoco ◴[] No.42213815[source]
Resource usage in general, especially server side? Although XMPP clients also seem to win too, cf [1] (debatable methodology in this link, I agree).

And this is not "implementation detail stuff", by design serving Matrix is resource-hungry, while serving XMPP is very lightweight. Others have phrased it better than me, something along the lines of:

> Matrix is a distributed, eventually consistent database; XMPP is just message passing.

Both have their own merits.

But you know all of that Arathorn ;). I'm replying for readers anyway.

[1] https://decentim.grafana.net/public-dashboards/92602d3a4aa84...