It is proven! I am floogulinc on Keybase: https://keybase.io/floogulinc/sigchain#f1e5b4289f660ed6d83756177276d65a44de1dd9e898eefa1820146cd656a61d0f
@emma_essex The reason I see many instances suspending others is that when an instance pulls in content from other federated instances, it is stored on that server and many owners don't want certain content to be on their server for legal and other reasons.
@emma_essex There are actually two types of blocking on mastodon, suspending and silencing. Silenced means they don't appear in the Federated timeline, but users can follow users on it and see them in their Home view. My main objection is with suspending instances. mastodon.xyz only silences pawoo while others suspend it all together.
@emma_essex The thing about blocking pawoo is that it is literally the largest mastodon instance with 179380 users right now compared to the largest English instance at 81073 for mastodon.social. For comparison mastodon.xyz has 10418 users. Blocking pawoo is blocking 23.28% of all mastodon users.
It looks like mastodon is already much more successful in Japan with the top 2 instances being Japanese (pawoo and mstdn.jp).
@emma_essex I agree with this. Another issue caused by blocking other instances like many are doing is it leads users to create multiple accounts on various instances just to be able to see stuff from those instances (pawoo for example), which further fragments and defeats the point of federation.
@TheKinrar Thanks, if you ever add more it might be a good idea to make a gist or github repo with the list like some other instances have.
@emma_essex Yeah, I'm really feeling the extended character limit. Even in writing those tweets suggesting the other mastodon clients I couldn't write out everything I wanted. The ability to control access to posts on a per-post level is really nice as well. I'm excited to see if this can really start to replace Twitter as others have tried.