Post
That would be great to know.
Probably this requires blocking at every possible level to be sure (eg. robots.txt, user agent, IP ranges...) And if some bots are using ActivityPub for scraping we could also block their HTTP signature public keys?
We've prototyped a system that builds on Bonfire's circles/boundaries to define and enforce blocks at the instance, user, and post levels. Would love feedback and suggestions to make it stronger!
Interesting, would love to find more about the circiles/boundaries-based prototype, is anything written up on that (or is there a repo to check)?
Agreed about blocking all the different paths. For the HTTP signature public keys, does that give any stronger protection than instance blocking?
Ah yes forgot to include the link: https://github.com/bonfire-networks/bonfire-app/issues/1412
And you're right, that'd be the same as instance blocking.
A space for Bonfire maintainers and contributors to communicate
