To be fair, with Rust macros anything goes. There was an example where someone demoed descriping rust structs and enums nested as xml with a macro to parse it.

Signal dies something called sealed Sender. The idea is, the sender information is encrypted in the package. https://signal.org/blog/sealed-sender/

Well, unless you login and transfer all your keys every time, the client already has all the info required to fetch and decrypt all the messages.

I know that you can configure synapse to delete messages. However every federated server only operates on their own delete scedule and you as the reciever can’t see the messages then anymore. Which I think is stupid.

The messages should only be stored on the reciever device after they were delivered and deleted on the transfering server.

I think a messaging server should store messages only until they are delivered. It shouldn’t have access to who sent it, only where they are going.

Matrix keeps a massive stack of metadata on the server, because the server takes care of the protocol and it needs all that metadata.

However you can’t loose data you never aggregated.

How do you migrate everything?

Im more surprised it works at all considering it uses eac