Are they extensions of core spec?

Also, the client projects cannot keep up and Element has defacto a monopoly and could always do what they want.

Meanwhile, XMPP has RFCs and therefore is an internet standard. Extensions can be created anytime and go to different states when implementations show up and demonstrate interoperability. There are sets of XEPs that should be implemented depending on use-case, such as instant messaging.

See this post as well:

When one vendor controls all parts of a service (e.g., both a client and server), it has the means to create a boxed platform. Controlling both the server and client allows a vendor to update the client and server without worrying about breaking compatibility with other clients/servers in the larger network. It could update the client to point users to a server that uses a completely different, closed protocol. This is what happened to many XMPP users in the early 2000s.

Problems may arise when development of the spec and production-grade reference implementation grow tightly coupled, leaving third-party implementation feasibility out of the decision-making process.

Case study: Matrix and Element

The only client that implements all the necessary features is Element. In addition to being the most popular client, Element practically serves as the reference client implementation: it’s developed by the same company that builds the dominant servers and most of the spec. The tight coupling between Element and the Matrix spec allow it to add features at a rate too fast for other clients too keep up; pretty much every Matrix user has to open up Element at some point to perform an action that isn’t supported in any other client. On the server side, Synapse is the only server that implements enough of the spec to be usable, with Dendrite coming in second. Both are made by the same company that develops Element.

As a user, consider using clients and servers made by different groups of people to make platform boxing more difficult. Pick implementations that suffer from less feature creep beyond spec compliance. What distinguishes a client shouldn’t be what features it has, but how it implements its features. Obviously, having some unique features is great; problems arise when the number of unique features crosses a certain threshold. Following both these practices encourages implementations to stick to standards compliance, reliability, and compatibility rather than “innovation”. Choose boring technology over shiny new features.

Try venturing outside the mainstream by taking a look at a less popular provider or client. All implementations start somewhere, and a diversity of implementations prevents a rule by oligopoly.

https://seirdy.one/posts/2021/02/23/keeping-platforms-open/

XMPP? It’s literally the internet standard for that. But it’s not a platform, it is a protocol. Platforms aren’t a good thing.

I thought it was about reinventing the wheel in a more complicated way that needs more resources and is slower. ¯_(ツ)_/¯

Came here thinking it’d be about the Gemini browser, instead it is about a chat bot :/

Thank you! I thought I lost it somewhere!

Matrix? For account creation? WTF?

Why not use an existing internet standard instead? There are so many RFCs, something would work.

Like… IRC. Or XMPP.

That’s what RFCs are for.

There are some BBC podcasts I’d like to listen to, but I’d need to download using a VPN in the UK to avoid ads.

I’d need to download them via VPN and then make them available to myself using another feed.

Others I’ve just unsubscribed, ads are far too annoying and not all have paid private feeds ¯_(ツ)_/¯

“supported by ChatGPT” is when I stopped reading, who knows how much of it is actual information that isn’t hallucinated…

Some of those websites are the sole reason I still have IPv4 enabled. I don’t host much on IPv4 nowadays (mostly just XMPP, as 4 (?) of the servers I talk to still don’t have IPv6).

Wow, that’s cool! But why hours? 30 minutes or 45 minutes or 90 minutes could be valid choices as well. :D

I personally would not want to spend an hour using Piefed on a single day, that’d be too much for my taste.

There are some 4G models from Nokia.

“Startups are good for the world”

WTF

X ist einfach nicht mehr cool seit ein paar Jahren, hätten die auch anders nennen können…

“read the changes before installing a major update”

As if people have the time to read the changelogs for every single package all the time… 🙄

This is pretty important on a server to avoid disruptions and outages, but people have other things to do.

And once it is no longer on and has become a setting, they can just remove the setting and force people to drop gsettings and then remove it completely.

They could also instead ask people on first launch. Some people enable telemetry, so they will find out how many people prefer to keep it, which I bet will be most.

Then that could be solved by displaying a message the first time GNOME is launched, not by disabling it. This will just break workflows for quite a lot of people.

Kostenlos für bestimmte benachteiligte Gruppen und Minderheiten.

Leider nicht das Luxemburger Modell.

Thanks, more info than half the post. :D

WebPush could be implemented.

Just as another data point: I run 1.4.2 on my instance and can use Voyager just fine.

Not much detail what that “innovation” does, reads mostly like marketing material.