News for hackers. Stuff that matters.
Re:Modern XMPP Server by troupo on Saturday December 02, 2023 @06:30AM (#38497854)
> Any decade now people are going to realize how awesome XMPP

In all honesty, it's not that awesome. It took XMPP over a decade to get features expected from modern protocols such as not requiring persistent connections, client notifications, conversation syncing between clients, file uploads, E2EE...

Re:Modern XMPP Server by zaik on Saturday December 02, 2023 @06:49AM (#38497931)
If you account for resources which have been put into development of those features, it's pretty obvious XMPP is the more agile protocol. Five independent open source developers take longer to develop some feature in their spare time than a corporation with tens of millions of venture capital funding, and sometimes they're even faster? Imagine what could be if people focused on XMPP instead of constantly re-inventing the wheel.
Re:Modern XMPP Server by troupo on Saturday December 02, 2023 @08:00AM (#38498324)
> If you account for resources which have been put into development of those features, it's pretty obvious XMPP is the more agile protocol.

10 years is not agile.

> Imagine what could be if people focused on XMPP instead of constantly re-inventing the wheel.

We could try and imagine. As it stands, it's XMPP which is reinventing the wheel, continuously. The primary reason being: it was developed at a time when non-persistent internet connection, multi-device synchronisation, video calls, ubiquitous file sharing and other wonders of the modern world didn't exist, and retrofitting it was a multi-year struggle. Undoubtedly prolonged by the very same people who decried the modern world and claimed that XMPP was enough: https://news.ycombinator.com/item?id=38497839

Re:Modern XMPP Server by nicoco on Saturday December 02, 2023 @07:20AM (#38498100)
Do not trust the FUD.

I've been using XMPP since I had a smartphone (I was late to the party, around 2015) and never needed a persistent connection or had issues with multi-device use. https://xmpp.org/extensions/xep-0313.html solves both and the first version is from 2012.

E2EE via opengpg has been there since the beginning of XMPP, and via OMEMO (signal-like) for 7 years now, just like HTTP file upload.

Re:Modern XMPP Server by troupo on Saturday December 02, 2023 @07:56AM (#38498296)
> Do not trust the FUD.

I don't. I know what I'm talking about: https://news.ycombinator.com/item?id=38497839

> solves both and the first version is from 2012.

The question is: when it stopped being experimental and supported by most servers and clients.

Re:Modern XMPP Server by seba_dos1 on Saturday December 02, 2023 @02:10PM (#38501085)
You saying things like "experimental or beta proposal" in context of XEPs shows that you don't know what you're talking about. For a while and for several reasons, many XEPs used to be widely implemented already before they have been processed beyond draft state. XSF's process has been unclogged relatively recently.
Re:Modern XMPP Server by arendtio on Saturday December 02, 2023 @10:41AM (#38499332)
How many protocols do you know that made that transition at all? I don't know many that even have that level of requirements (low latency, multi-device, low energy consumption, federation, scalability) in the first place, and even fewer that managed to pull that feat off.

IRC probably has a similar level of requirements, but I haven't heard of its mobile capabilities. Most others seem to be completely new developments and in the case of Matrix e.g. they seem to have solved some issues by reducing the scalability (higher server load).

So yes, it took a while for XMPP to solve those issues, and you can say it took too long. But at the same time having done that at all, is an achievement in itself.