The amount of FediFetcher instances scraping chaos.social is alarming. They all come from different Azure IPs because it's the recommended way to run it. Github reports: 1.361 deployments. We also see massive scraping from the TOR Network and scraping of RSS Feeds from SerendeputyBot. That sucks! #mastoadmin
@leah I think the only way to stop it is to fix the underlying problem. As far as I understand the idea behind this tool, it is meant to fetch missing posts from a thread. So we could come up with an FEP that solves that problem. Then hopefully people will stop using the tool.
@dumpsterqueer@heluecht@leah funny thing is that replies collection actually isn't part of activitypub. it's part of activitystreams instead. there are no side effects for receiving a Create of an object with inReplyTo set. https://w3id.org/fep/7458 is a FEP that is relevant here, describing actually using the replies collection. combine with https://w3id.org/fep/0391 for special collection proofs (stamps).
@dumpsterqueer@heluecht@leah and hey, while we're looking at properties from activitystreams, i'd perennially point toward context and https://w3id.org/fep/7888 as a "parallel path" to fep-7458. instead of recursing through replies collections, we could have a singular context collection which represents the moderated conversation as a flat list. this allows inReplyTo as simply metadata.