If you feed somebody's posts into your shitty LLM without an explicit and reversible opt-in, you are violating the consent of fedi users.

This "Zeitgeist" app not only violates consent, but it also doesn't have a centralized ActivityPub identity that can be blocked or defederated.

#FediAdmin #Fediblock

https://alpaca.gold/@seldo/116229243453108157

The creator is making pretty clear that it's designed this way to make it harder to block.

Normally, you'd expect an LLM scraper to have a single (blockable) ActivityPub account doing the scraping.

This is designed so that everybody who uses the service has their identities harvested to steal people's data on the app's behalf.

#FediBlock #FediAdmin

@fedilore Is there any reason I can't just moderation block alpaca.gold entirely? Seems like a single user instance.
@celestiallavendar You should block alpaca.gold, but the app itself is a client which means it uses the user credentials of everybody who uses it to feed the LLM.
@fedilore That makes sense. If it's a mastodon client I wonder if *key instances are safe. Probably not I would assume, cuz the posts still federate.
@celestiallavendar Nope. Anything even slightly compatible with a Mastodon phone app can be logged in like this.
@fedilore Yeah, that's what I figured. Honestly, it makes me think that there should be a way to implement some kind of bot & scrape layer to ActivityPub that poisons all outgoing content for bots while leaving it fine for users. Could solve a lot of these Fedi scrape / LLM / data harvest issues I think.