@stux yes. Block their user agent. We did: https://github.com/toot-community/platform/blob/main/manifests/applications/ingress-nginx/helm-values.yaml#L23

Does anyone know a good way to block them?

I do not want anything to do with their shady business and they should stay away from ours

Just edited our #nginx configs and added

if ($http_user_agent ~* "Meta-ExternalAgent") {
return 403;
}

to the server block

#AI #NoAI #Meta

Just edited our #nginx configs and added

if ($http_user_agent ~* "Meta-ExternalAgent") {
return 403;
}

to the server block

#AI #NoAI #Meta

In addition, i've also enabled CloudFlare's AI scrape block for masto.ai and .coffee

mstdn.social DNS is at Hetzner

@stux

Is there an Instance Runner newsletter for all nodes to.learn from your efforts?

Just edited our #nginx configs and added

if ($http_user_agent ~* "Meta-ExternalAgent") {
return 403;
}

to the server block

#AI #NoAI #Meta

@kevinrns When Ghost's new federation works fully ill setup a small blog on a sub of mstdn with info, posts and also financial data etc

So according to this article: https://www.dropsitenews.com/p/meta-facebook-tech-copyright-privacy-whistleblower

#Meta is scraping the media proxies of mstdn, masto and .coffee..

If this is true, this is very worriying and pisses me very much off

No wonder our media loads so crappy if they are constantly tapping in..

Fuck #Meta to hell

Just edited our #nginx configs and added

if ($http_user_agent ~* "Meta-ExternalAgent") {
return 403;
}

to the server block

#AI #NoAI #Meta

In addition, i've also enabled CloudFlare's AI scrape block for masto.ai and .coffee

mstdn.social DNS is at Hetzner