[wkat4242]

> Being barebones is a part of the selling point for an eXtensible platform though.

Understood but as a user I don't want core functionality like history to be hidden behind extensions which may or may not be supported or need additional components to client or server.

As a user (and home server operator) I found that Matrix+Element gives me a much better user experience with much less fuss (though I admit it was more than 5 years ago when I last ran ejabberd). And the bridges are amazing, just what I needed. Because Matrix is not very useful until everyone uses it, for the transition there are bridges.

I don't really care about the underlying architecture, I just want it to easily provide me a modern chat experience.

[toastal]

> core functionality like history

I won’t disagree with this. It could be a part of the main spec, but there’s some novelty knowing you could do a ‘complete’ server or client in a day. There are certainly different modern expectations than compared to IRC. Compared to the OP, barebones XMPP is much closer to a ‘simple chat’.

> bridges

XMPP + libpurple were trying to do similar things. For a hot minute everyone, even the like of Facebook Chat and whatever Google’s chat was named at the time, was using XMPP til they all decided to go for a proprietary option and users had the option to chat from anywhere with anyone. That doesn’t discount Matrix for doing something needed now. Proprietary chat lock-in runs in cycles. Here’s to hoping they don’t adopt & abandon Matrix.

[wkat4242]

> I won’t disagree with this. It could be a part of the main spec, but there’s some novelty knowing you could do a ‘complete’ server or client in a day. There are certainly different modern expectations than compared to IRC. Compared to the OP, barebones XMPP is much closer to a ‘simple chat’.

Novelty sure but it's not really complete in terms of what a user expects. I still use IRC a lot too but with a client that provides all the mod cons I need. Also, nobody writes a protocol handler from scratch anymore. People writing a matrix client will simply use libmatrix.

There's just the reality that "simple chat" akin to ICQ in its early days, is just not what people want anymore. It's not a benefit anymore IMO.

I think the XMPP community is really too focused on architectural cleanliness than on offering the user what they want. Which is their prerogative, sure. But it's mine to choose the chat network that suits me best. This is how I moved to Matrix.

> XMPP + libpurple were trying to do similar things. For a hot minute everyone, even the like of Facebook Chat and whatever Google’s chat was named at the time, was using XMPP til they all decided to go for a proprietary option and users had the option to chat from anywhere with anyone. That doesn’t discount Matrix for doing something needed now. Proprietary chat lock-in runs in cycles. Here’s to hoping they don’t adopt & abandon Matrix.

Yeah I know, they killed federation, I guess mainly because of marketing. If google chat users can reach facebook chat users there's no need to sign up for facebook chat, thus less data mining for facebook, and lower numbers in their growth hacking charts. Keeping users in the walled garden is a goal, not a side-effect.

This is also why I dislike Signal so much, they even ban other versions of their supposedly open client. I'll never adopt that as a whatsapp replacement because it's simply no better in terms of lock-in. I don't want yet another walled garden. Signal solves one or 2 problems of whatsapp but for me to adopt something as the be-all-end-all chat app it will have to solve all or at least most of them.

It doesn't really matter if the third party apps adopt Matrix and stop federating. It won't be any worse than it is now. I'll just bridge where needed.