Hacker News Reader

Mastodon-the-software doesn't have to do anything. Mastodon instances have to choose whether to block Threads or not.

Of course there is no 'central enforcement', that would be at odds with the very principle of federated social media (namely, that instance admins are free to choose how they run their own instance).

View on HN

This gets you right back to the issue of having to transmit licenses with all content. Which is fine - this can absolutely be a thing which exists within the protocol.

But then people are suddenly going to find they don't get the impact they want either: because the immediate outcome is simply going to be "license for public distribution or we'll reject your content" because everything else is too much hassle.

Blocking Threads doesn't prevent your content from getting to Meta. Some other instance that you federate with might not block it. See: TFA.

Blocking Threads is necessary but not sufficient. I should probably be clearer about that in the article.

Reply on news.ycombinator.com