TIL that the president of Signal believes that people who run Mastodon and/or Matrix servers do so "in most cases" on hyperscaler* infrastructure.
This is my Mastodon server. And its UPS. And its networked KVM for when things get really hairy.
It's also my Matrix server. And Nextcloud. And Git. And Home-Assistant. And Jellyfin. And SearXNG. And Peertube.
When people objected to her claims, she doubled down and proclaimed condescendingly that we "don't have a clear understanding of this space".
TIL that I don't feel confident in recommending people to use Signal. Something's very off here.
*) "hyperscaler" basically means the big cloud infra providers with provisioning APIs that allow you to scale your resources up/down automatically with usage
@troed do you serve ~100 million users? What about HA? What is the point of this post?
Do you say that @signalapp should hire multiple devops engineers, buy hardware, spend time figuring out how to implement a robust infrastructure, deal with all inevitable fuck ups, upset a lot of their users just because people are afraid of AWS?
This is the whole point of encryption. It does not matter what services are used for hosting.
@dwaem @troed @signalapp It matters when your services go down. The point is Signal should NOT be centralized. In fact, just use Linphone (or any SIP client) with cryptomesh IPv6 (cjdns/yggdrasil/pinecone/etc) for the equivalent of Signal. Your CGA IPv6 is your "phone number". With an actual decentralized protocol, it doesn't matter how many people are down - the ones still up can still talk to each other.
When matrix.org went down, the Synapse Admins room was discussing the issue - because matrix.org going down just means accounts on that instance (admittedly a lot) are down.
