Have you read this yet?
FOSS infrastructure is under attack by AI companies https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/ Please boost for awareness, reach and to public shame Microsoft, Meta, OpenAI, Perplexity and other such AI companies.
#opensource #programming #Developers
Discussion
I did this morning actually yeah, actually inspired this note :) On Sunday I cut from a few MB/s down to a few B/s just by tuning some more user agent stuff and nginx things.
Ill be honest and say I got interrupted and didn't finish the article. Ill have to see if they made recommendations on how to mitigate it.
nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z you seen dis? damn those bastids
we must make replication a key priority, they can't vacuum every replica at once if they aren't so easily recognised as affiliated (and abstracting from the web app and building a protocol will help a lot with preventing this kind of harm
ai bastards are desperate to hoover up every bit of code they can get thinking if they just get one more thing to feed the model that it will somehow magically make it work better :scoff:
What about presenting a zero-sats lightning invoice?
Or a Nostr login, to read?
I'm just thinking for our public gitserver. Not your website.
I guess the bots don't bother hitting up websites like Alexandria, since they can just go for the relays, directly. Or maybe they're too dumb, to figure that out? 😅
I like how you think
the issue for the rest of the web is about the tradeoff with being indexed by search engines.
nostr train dont care 🚂
Yeah getting indexed is nice, just as long as it's not most of my electric bill. The other things are you have to expose some things so it's not complicated for the user. I think capchas and stuff like that suck and they really skyrockets bounce rates depending on your market. Plus integrating those services destroys user privacy.
It's always a trade off. If a user can do it usually a bot can do it too.
Imagine blocking nip05 requests...
The GitCitadel nip05 accounts for the next busiest traffic (not a problem by the way just a few kb/s) and I wouldn't want to block that.