Re:How the European Commission rolled out Matrix to more tha...
by sneak on Thursday November 19, 2026 @10:18AM
(#50561230)
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.
Re:How the European Commission rolled out Matrix to more tha...
by JadedBlueEyes on Thursday November 19, 2026 @10:52AM
(#50561705)
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
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.