Conversation

@thegibson@hackers.town @vantablack@beach.city
I am in favor of the following three-step program:

- Limit Meta
- Activate authorized fetch (important!!)
- Inform users and tell them that they can block Meta’s domain and effectively isolate themselves from that service.

Limiting Meta means no posts on the federated timeline (in case of badly moderated posts) and that users will have to approve all follows from meta users (they won’t send their posts to meta unless they give consent first)

Authorized fetch means that Meta cannot easily (they still can by other means) scrap your instance and it also means that boosts won’t accidentally push posts to meta if the user is against it.

And domain blocking means that you’re giving the choice to the users. (it can even be opt-out, if you find a way to add meta as a default blocked domains for all users)

It also means that users can connect with their normie IRL friends who are all on meta’s services (either facebook or instagram) and will never willingly use mastodon.

Defederating from all servers who decide to federate with meta is beyond stupid. All you’re going to achieve is completely isolate yourself. If that’s the path you wan to take, you might as well disable federation entirely. Scrap all ActivityPub related code from your instance and continue as the old web of PHPBB forums.

Defederating from Meta and only Meta is a lot less serious (especially if all your users are likely minded), but you’re still forcing a choice on your users that shouldn’t be yours to make. Let users ban meta themselves if they want to.

Federating with meta should be a user choice, not an admin choice and even less a coordinated fediverse choice.

Public

Notices

Feeds