I’ll try to find a link to the metadata issues, but for now I’ll just say it’s senders, receivers, timestamps, and room “joins” I think. Also reactions and read receipts aren’t encrypted for sure.
Sure, “only the various server admins get the metadata,” but when you don’t trust the admins of the largest and “default” server? That’s an issue. Also nothing stops [insert group that worries you] from spinning up a server to collect metadata, unless as I said you host your own separated server without any federation.
As for the AMDOCs connection, this is enough for me to be out, make your own decisions:
The initial project was created inside Amdocs, while building a chat tool called “Amdocs Unified Communications”,[6] by Matthew Hodgson and Amandine Le Pape. Amdocs then funded most of the development work from 2014 to October 2017.[7]
I’ll try to find a link to the metadata issues, but for now I’ll just say it’s senders, receivers, timestamps, and room “joins” I think. Also reactions and read receipts aren’t encrypted for sure.
Sure, “only the various server admins get the metadata,” but when you don’t trust the admins of the largest and “default” server? That’s an issue. Also nothing stops [insert group that worries you] from spinning up a server to collect metadata, unless as I said you host your own separated server without any federation.
As for the AMDOCs connection, this is enough for me to be out, make your own decisions:
https://en.wikipedia.org/wiki/Matrix_(protocol)