@Samkupar @navneetmathur @stux @Deepsealioness @Gargron

Agreed, the account export function is what you're looking at.

The idea behind the fediverse is that you can have multiple accounts, spreading across multiple servers. There's nothing stopping you from opening an account elsewhere and importing all of your current follows. You can keep this up-to-date as a fall-back.

Treat a fediverse account like an email address.

@GigaByte4711 @Samkupar @stux @Deepsealioness @Gargron
Thanks all for response. The reason for my question was to address some of the apprehensions around stability of account (follow/follower) that mastodon needs to compete with the Birdie on.
I understand that one can export and import those that you follow across accounts.
But, in a scenario where say, mstdn.social is compromised, all of my followed accounts that are on mstdn also get compromised, so even if I migrate them, I am kinda stuck

@navneetmathur @Samkupar @stux @Deepsealioness @Gargron
Correct. Bear in mind, this is a social platform. If you were to have your twitter/email account compromised, you would have the same issue. People would be able to identify who you interact with.

This is the same on mastodon hosts. If what you are saying should be cryptographically private, it should be encrypted end-to-end.

(1/2)

@navneetmathur @Samkupar @stux @Deepsealioness @Gargron
As an instance host, I can promise two things:

•I will keep my server and mastodon patched
•I will take the instance offline and alert users if it has been compromised.

That's where my ability to protect you ends. If your Threat Profile requires that no-one can identify who you talk to, then don't put data into the fediverse you can't deal with being public.
(2/2)