Re:Mitigating a DDoS on Mastodon
by bluehatbrit on Friday December 06, 2019 @06:57AM
(#21721031)
From my understanding of Mastodon, you register an account with an instance and that's where your account and data are stored. You then get an address which is something like [email protected]. Federated instances can then connect together to read and exchange information, but for the most part your data doesn't leave your instance. I imagine the idea behind this is you can choose (or host) where your data sits, but still interact with a large network of individuals. That said, my understanding of Mastodon is limited.
Re:Mitigating a DDoS on Mastodon
by dredmorbius on Friday December 06, 2019 @09:20AM
(#21721921)
As others have noted: accounts are instance-bound.
Other Fediverse protocols -- I believe either Friendica or ... I think Hubzilla? -- have some level of account portability.
There's a fairly long-standing request for Mastodon to support this. For now, you can have accounts on other instances forwarded to your primary.
While you can export and import your own follows, followers of your account won't automatically redirect to the new home.
Masodon content however will syndicate across the Fediverse, and even some of my posts from a now-dead instance can (occasionally) be found.
> While you can export and import your own follows, followers of your account won't automatically redirect to the new home.
This information is outdated since October 11, 2019. You can move followers from one account to another in Mastodon 3.0.
Re:Mitigating a DDoS on Mastodon
by dredmorbius on Friday December 06, 2019 @11:39AM
(#21723412)
TIL, thanks!
(For others: Gargron is Mastodon's creator.)
That's at least how I think a federated system should work. Not sure if reality matches that.