|
Top-level
 Finally, I give a laundry list of things that I believe need to happen to mitigate the risk stemming from #Mastodon monoculture on the #Fediverse. I also list some things every person using fedi can do themselves to help mitigate that risk. I've already seen one vibrant decentralized social network wither on the vine due to monoculture and flagship-instance-itis, and while fedi is much bigger and more resilient already, I do think we should worry about it here too. 馃У/4/end 7 comments
@sheogorath I thought about it and decided against it for now. But that's just my opinion, of course.  @rysiek Perhaps mastodon.social should be the learner instance: the one you join when you first start using the fedi but which you're expected to migrate off of to a more appropriate to you instance in a reasonable time (6 months?). (I have slightly more nuanced thoughts on the actual implementation but does the principle make any sense?) @edavies it would definitely make more sense if it was set up that way, than the way it is set-up today. @edavies It would work if the mastodon.social domain would be changed to something like mastodonbeginners.social. With such domain name many people would migrate to other instances naturally, as soon as they would start to feel uncomfortable with "beginners" part. #MastodonSocial #MastodonBeginners #MastodonMonoculture #Mastodon #Fediverse @rysiek @chlopmarcin Yes, something like that might help. I've tooted on this idea once before: the other one mentioned this: https://functional.cafe/@edavies/110264604135941189  @rysiek Thanks for your valuable thoughts - yes, the monoculture Mastodon is and will be a problem in the #Fediverse .
|
Gregory's Server
@rysiek I think something missing from the list is: Set up limited defederation, which hides new posts from mastodon.social on public timelines but keeps followers and followings active.
This amplifies decentralised accounts while not impacting existing relations.