upvote
> Some people (like me) simply don't like the idea of being at the mercy of any single particular entity.

Is the person hosting the Matrix instance not the single particular entity you are now at the mercy of?

I'm not trying to be glib, it's a genuine thought. I also love the idea of using self-hosted solutions for everything but more often than not it just means putting all the trust/responsibility on the one person willing to maintain the whole thing.

reply
Valid point, and there are p2p/decentralized approaches such as White Noise that builds on Nostr and MLS (RFC 9420) [0]

[0]: https://www.whitenoise.chat/

reply
No. Hosting a matrix service is a commodity. Search for "matrix hosting" and you will find plenty of providers. As long as you have your domain and a data backup you can change seamlessly. What can you do if Signal stops being a good alternative?
reply
> Is the person hosting the Matrix instance not the single particular entity you are now at the mercy of?

to some degree, but you could migrate to a different or your own instance without needing to convince your contacts to do the same.

reply
We're also in the process of (slowly) adding account portability to Matrix - I demo'd the first ever (rather anticlimactic) migration at the matrix conf last month: https://youtu.be/U5LRRNgvTZE?list=PLFDUAtPqCX98&t=1082
reply
You’re at the mercy of whoever is hosting your Matrix instance.

Also, every matrix instance in the world has to forward their notification pushes for every iOS user in the world to vector.im, the matrix vendor, to be relayed to Apple.

So, if you use iOS, you are at the mercy of at least 3 entities.

There are also lots of Signal clients, and they’re all free software.

reply
That's an incorrect evaluation of push notifications.

Because of the way push notifications work on iOS, they are end-to-end encrypted and relayed via a push gateway operated by the person that deployed that client to the app store. For Element clients, this is Element Creations. For other clients, there are other operators with no relation at all. If you build your client from source, it's you.

As far as the server and protocol is concerned, it just sends notifications where the client tells it to.

reply
Yes, vector.im (new vector ltd) changed their name to Element Creations because they still haven’t learned the lesson that having a company name different than your product name is dumb. Countless startups have re-learned this lesson.

Regardless, that’s why I said pushes and not push notifications, but they are all indeed relayed through one entity, formerly named New Vector and now named Element (and if they are successful then eventually named Matrix). They’re the publisher of the iOS app and iOS apps can only receive pushes from their publisher.

All of this handwaving about distributed this and selfhosted that and it all relies on some small VC-backed startup’s instances in realtime. If those go down the app effectively goes down because nobody on iOS gets notifications. Same goes for when some hobby sysadmin’s non-HA deployment goes offline for a day or two.

reply
There is no "the app". For my personal usage I don't use any apps published by Element, and as such do not rely on any of their infrastructure. I develop my own server [0], my friends develop their own clients[1][2][3]. When my server went down I switched to one hosted by someone I know, and then switched back when it was up. Decentralisation and interoperability are not theoretical.

[0]: https://forgejo.ellis.link/continuwuation/continuwuity [1]: https://github.com/gomuks/gomuks [2]: https://git.sable.moe/sableclient/sable-next [3]: https://git.federated.nexus/Nexus/nexus

reply
> So, if you use iOS, you are at the mercy of at least 3 entities.

To be pedantic here, you can communicate without notifications.

reply
No, you can spin up a new container at another hoster with your backup.
reply