Yesterday, users of mstdn.social instance lost their connections to artists at mastodon.art instance ( src: https://framapiaf.org/@Curator@mastodon.art/110570978375947500 ). I hope giving visibility to this issue will help them to restore the broken bridges.
@davidrevoy pardon my ignorance, is "mstdn.social" the same as "mastodon.social" or a different instance?
Is there any kind of documentation on how to keep track of who I'm following so that I can restore broken follows the next time mastodon.social breaks the fediverse or is otherwise excommunicated by other instances?
@davidrevoy the short dumb answer is Preferences > Import/Export > Export, which will produce a dump of everything. Or just collect the CSV for "follows".
Is there any mechanism to be notified that one of my "follows" is no longer accessible? Do I just have to re-follow everyone every other week?
@manicdee They are different, but I also mixed up the two instances at first so I think many will have the same feeling. Their naming really overlaps too much; it just sounds like one is the URL shortening of the second... I could disambiguate the two by their number of active users mainly:
- https://mstdn.social/explore (31K active users)
- https://mastodon.social/explore (220K active users)
@davidrevoy thank you for the clarification. Now I can try to understand my options for the rest of my questions at a more relaxing pace :D Although I'm sure it's only a matter of time before mastodon.social gets in trouble for what the people that use it are saying or doing.
These are completely different instances hosted by different owners.
You can export your followers via settings in Mastodon web application. #MastodonSocial's impact on the Fediverse is overstated - as long as there is a relay server that your instance can depend on, mastodon.social is but one of the noisy figures that can be safely removed. Not without caveats, but, if people you follow don't sit there, it's fine.