Live data from Hacker News

Happy Birthday, XMPP: 20th Anniversary of Jabber

fr.movim.eu

41–50 of 56 posts

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#41
post #32

I’d say that it feels like just yesterday, but it totally feels like decades ago :) I’m very lucky to still be close with so may of the truly amazing individuals that helped build Jabber, and over the years deeply honored by all those that spoke to me about how it inspired them. While at the surface it may seem like all of our efforts had little impact on the big “messaging silos”, I am most proud of how much Jabber/…

I remember decades ago seeing it come out and thinking we already have irc and email and chat. Why throw in "with xml" and think it's going to be better.

Shows what I know. Way to stick with it. :)

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#42
We need to move away from Hipchat at work and really wanted to use xmpp, but was super let down by the iOS clients, it can't be used in production.

Android - thanks to Cobversations and Xabber, is really ok, PC is ok (Gajim), but we couldn't migrate due to the 3 iOS users in the team. Duplicate msg and all sorts of weird behaviour and errors made it a no go.

We ended up with the shitty MS Teams in the end; comes free with our office365, has working notifications across platforms and can do messaging and file transfers without issues.

I dream of a future where xmpp is an option.

People who have to gain from that: please fix the iOS side of things.

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#44
post #16

Earlier quoted context omitted.

> it didn't happen before (at least for XMPP). It was the niche of niches but the Nokia n900's standard built in xmpp client could do voice/video/filetransfer with a gnome desktop's standard messaging infrastructure (telepathy or something?) in what, like 2010 ? But, besides that, I get what you're saying about "normal" messengers and conversations nowadays. So good. Thanks Mr. Gultsch[0] ! [0] https://gultsch.de/

While I understand the concerns and I appreciate all of what Conversations' author is doing for the community, other clients have also seen significant improvements lately. Gajim[0] has practically come back from the "dead". There is a huge difference, UI/UX-wise but not just, between pre and post 1.0, (1.1 at the time of writing, 1.2 coming). There is also dino[1], a nice and simple desktop client, and converse.js[2…

I still prefer pidgin, but it needs a lot of love to make it a reasonably modern XMPP client:

- https://github.com/danielkraic/Pidgin-XEP-0136-plugin adds XEP-0136 (needs "mam_archive" on prosody)

- https://github.com/gkdr/carbons adds XEP-0280 (Carbons)

- https://github.com/Junker/purple-xmpp-http-upload adds XEP-363 (HTTP uploads)

- https://github.com/gkdr/lurch adds XEP-0384 (OMEMO)

- https://github.com/noonien-d/pidgin-xmpp-receipts XEP-0184 (message delivery receipts)

The real pain for Pidgin is the complete lack of XEP-313 due to Pidgin's aged logging system, and I would really like to see a working message sync for Pidgin :(

EDIT: https://github.com/CkNoSFeRaTU/pidgin apparently has had XEP-313 patched into Pidgin for years now. Combined with lurch and Carbons, message sync is working fine.

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#45
post #17
post #13

Earlier quoted context omitted.

Before doing that, please consider contributing to an existing project first. There are many out there and they'd love more contributors.

Which is the best XMPP server? For the server mentioned here... OpenFire = written in Java Prosody = Lua Ejabberd = Erlang

I love Prosody. It took five minutes to set up and it's been flawlessly running ever since. We use it for internal company talk, pasting code, sending files. If you don't need 1M+ clients it's great.

I also set up an ejabberd instance for a client years ago when Prosody was not a thing but it's more complicated to set up. They changed the config file from Erlang to YAML a while ago but it's still complex. But it's nice it has a web interface to create users and easier to not get bothered about it once it's up and running. Ejabberd can handle a massive number of clients.

Here's an older discussion about XMPP self hosting:

https://news.ycombinator.com/item?id=8783794

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#46
post #42

We need to move away from Hipchat at work and really wanted to use xmpp, but was super let down by the iOS clients, it can't be used in production. Android - thanks to Cobversations and Xabber, is really ok, PC is ok (Gajim), but we couldn't migrate due to the 3 iOS users in the team. Duplicate msg and all sorts of weird behaviour and errors made it a no go. We ended up with the shitty MS Teams in the end; comes free…

I know it's not open... but I personally really like Teams, especially if you use some of the integrations, wiki and files.

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#47
post #44
post #16

Earlier quoted context omitted.

While I understand the concerns and I appreciate all of what Conversations' author is doing for the community, other clients have also seen significant improvements lately. Gajim[0] has practically come back from the "dead". There is a huge difference, UI/UX-wise but not just, between pre and post 1.0, (1.1 at the time of writing, 1.2 coming). There is also dino[1], a nice and simple desktop client, and converse.js[2…

I still prefer pidgin, but it needs a lot of love to make it a reasonably modern XMPP client: - https://github.com/danielkraic/Pidgin-XEP-0136-plugin adds XEP-0136 (needs "mam_archive" on prosody) - https://github.com/gkdr/carbons adds XEP-0280 (Carbons) - https://github.com/Junker/purple-xmpp-http-upload adds XEP-363 (HTTP uploads) - https://github.com/gkdr/lurch adds XEP-0384 (OMEMO) - https://github.com/noonien-d/…

I wish Pidgin would just disappear. It is absolutely unusable without all these plugins in a modern multi client world, and most users don't know they need them.

The delivery receipts issue is a decade old [0]! Libpurple is a mess to implement all the modern features, because it tries to support the baseline of so many different protocols.

[0] https://developer.pidgin.im/ticket/6940

Re: Happy Birthday, XMPP: 20th Anniversary of Jabber

#48
post #47
post #44

Earlier quoted context omitted.

I still prefer pidgin, but it needs a lot of love to make it a reasonably modern XMPP client: - https://github.com/danielkraic/Pidgin-XEP-0136-plugin adds XEP-0136 (needs "mam_archive" on prosody) - https://github.com/gkdr/carbons adds XEP-0280 (Carbons) - https://github.com/Junker/purple-xmpp-http-upload adds XEP-363 (HTTP uploads) - https://github.com/gkdr/lurch adds XEP-0384 (OMEMO) - https://github.com/noonien-d/…

I wish Pidgin would just disappear. It is absolutely unusable without all these plugins in a modern multi client world, and most users don't know they need them. The delivery receipts issue is a decade old [0]! Libpurple is a mess to implement all the modern features, because it tries to support the baseline of so many different protocols. [0] https://developer.pidgin.im/ticket/6940

I wish it would reborn, that I agree on. Disappear - no. Please no. I still need to connect to 3-4 systems, and the last thing I want is 3-4 messengers, especially if all of them are webapps. Pidgin is still the only thing standing between me and total messenger madness.
Post reply on HN