It's not any worse than the differen't feature support levels of different Matrix clients. But especially on Android, XMPP has nice modern clients with all the features you would expect, including a/v calls and reactions/stickers.
The main issue right now are up to date Windows desktop clients, but on Linux desktop there are some good options.
There is: XMPP 🤷
There is not much they can do about it short of shutting down the entire server. Due to how matrix functions internally any sufficiently large federated homeserver replicates most of the entire network.
It is a bit counter-intuitive but restricting new signups will not help them much. The way the matrix protocol is designed, i.e. replicating everything on every server, means that clients connecting to their server have only a minor impact. As long as most rooms of the entire matrix network are replicated on the matrix.org homeserver their costs will stay high and there isn't really much they can do about that other than shutting it down entirely.
Deltachat works ok for 1:1 chats and small groups. It is totally unsuitable for large public channels as it doesn't really have a concept of group chats and just pretends so by (in email parlance) adds every one in 'CC'. This only works ok for small private groups.
IRC just needs to get it's shit together and start adopting IRCv3 features on the larger servers. The problem is really only that networks like libera.chat run a feature set that is at least 15 years behind what IRC can actually do.
This article is nonsense. The Foundation was always a front for New Vector and their board is largely made up by New Vector employees. So of course they knew what was going on.
New Vector simply decided that the strategy to make Matrix appear as an open standard was against their business interests and thus left the foundation to fend for itself with obvious consequences.
That sounds like a plot that could include lemmy.ml somewhere 😅
Which, you know, is a great deterrance to would be attackers. Nuclear deterrance is 4D chess via game theory. Not being able to slowly escalate a nuclear war is a benefit that makes people think twice about starting one.
Currently only the Stripe backend supports recurrent payments by charging a credit card automatically. For Taler I plan to add an invoice like reminder email to simulate something similar.
One time payments are of course supported by both.
Hmm, did Pocketbase add AP support, or how is this implemented behind the scenes?