The #matrix.org Homeserver is down, and will be for some time.

This is why it's a bad idea to just use the default instance in any decentralized network. It leads to centralization and any issue will impact disproportionally more people, not just the local users but also anyone they want/need to communicate with on other instances. Not to mention the longer time to recover due to the data size.
https://mastodon.matrix.org/@matrix/115139109820482116

#matrix_org #Decentralization #Centralization #DefaultInstance

The Matrix.org Foundation (@[email protected])

Status update: we’re 47TB through restoring the 55TB db snapshot of the matrix.org DB, but then have to rebuild the DB and replay the subsequent 17h of DB traffic, which will take several hours. Thank you for your patience, and apologies once again for the outage.

Matrix.org's Mastodon

Probably a bad idea for reasons I'm not seeing but what if the #DefaultInstance in the app was not #MastodonSocial, but a "temporary" instance (hosted by whom? an obvious question), where users are encouraged to quickly choose a home instance with posts from admins highlighting various instances and who they might appeal to?

Lack of portability of posts would be a problem as would getting people to make their stay temporary, but those are the same problems as defaulting to social

People say that having a #DefaultInstance #makes #onboarding easier, but when I first tried #Matrix, I joined their default instance, and the cesspool that was the default instance made me not want to use matrix for months after.

Seems the same thing is happening with .social... Maybe just have a simple wizard to assign people their first instance instead.