mccSo there's this guy who made a tool where someone punches in their bluesky or mastodon credentials to his website, and it auto-crawls their feeds and produces an LLM summary of everyone it finds posting there. He was asked what people should do if we don't want to be mulched as content for his summary feeds. He said we should block him. I replied, I can do that, but that only stops *you* from running the tool on me, how do I prevent *your other users* from running your tool on me? He blocked me.
It is possible he interpreted the way I phrased my request as rude. I may have said something like "you are selling us as meat".
Anyway, the fact he's blocked me *partially* solves my problem, in that now he cannot LLM summarize me anymore, but the problem that possibly eventually a *second* person would use his tool remains unresolved.
Honestly, it's baffling that he added Mastodon support at all given that he's been here for years and thus saw some of the MANY YEARS of conflict and debate about the idea of people merely *archiving* or *indexing* Mastodon posts. And then he goes an uploads an auto-LLM-mulcher tool. IDK.
jablkoziemne@mcc it was bound to happen :/ though I believe servers could mitigate this by placing limits on number of querries given user/ip/subnet/userahent could perform. Thoyhg that would impact people behind NAT, thoes who want to scroll and read bit longer, and probably bots would just go around it by adding longer sleeps between querries.
Still, in the end if your client can display toots or other activities, so can bots.
@jablkoziemne The fact that anyone could have done this does not make doing it okay