If any of you is curious about how best to block #Meta #Facebook #Instagram or any other faceless corporation from interacting with your posts on Mastodon, you(r admin) will want to look at turning on AUTHORIZED_FETCH for your instance. This setting, partnered with a bog-standard suspension of an instance, ensures that your posts won't leak to that instance via transitive boosting.

It works just fine. I've had it turned on on Old Mermaid Town since almost day 0, and we federate with other instances, even other fedi software, just fine*.

* Almost. We found a weird follow bug with Bookwyrm which we are still trying to identify.

@Gargron

Is this feature turned on on mastodon.social, so that my content cannot illegally be used by #Meta's #ProjectBarcelona?

"...
how best to block #Meta #Facebook #Instagram or any other faceless corporation from interacting with your posts on Mastodon, you(r admin) will want to look at turning on AUTHORIZED_FETCH for your instance...."

Thank you for your consideration.

@futzle

@futzle @admin I forget do we have authorized fetch on?

@futzle Would Authorised_Fetch mean the instance would have to manually approve other (non-corporate) instances or would members see them just fine?

Could u please link the documentation explaining this parameter? I'll look it up otherwise :))

Thanks much !! <3

@ash It’s described on the docs here. https://docs.joinmastodon.org/admin/config/

It’s orthogonal to instance blocking. You(r admin) still needs to block the instance. Users won’t even notice.

Configuring your environment - Mastodon documentation

Setting environment variables for your Mastodon installation.