For #iocaine 3.4, I think I'm just gonna ignore the table & set name, and use hard-coded ones. Not very nice, but that's a simple to implement and API-compatible way.
Will fix it in 4.0. That'll restore configurable table name, but the per-ruleset sets and chains will be gone (from the API too).
I just finished a short introduction post about @algernon's project iocaine: the deadliest poison known to AI 
(not man 
)
Within the post I explain what iocaine is, how it's related to AI and LLMs and of course why I use it to fight AI/LLM companies and to poison their crawlers and training sets.
Using, configuring and watching iocaine was also a way for me to shifting my dystopic/pessimistic thoughts 
into fun and joy 
And yes, I hate AI and LLMs and yes, I'm really fine by becoming an obsolete developer by not using it 
https://lukasrotermund.de/posts/fighting-ai-and-llms-with-iocaine/
#iocaine daily stats restored!
I borked DNS. Whops.
Will try to weave firewall metrics in too for the next daily toot.
#iocaine has been up for 12h 9m 5s, and spent 12h 44m 20s dealing with - gestures hands wildly - everything. In the past 24 hours, it served 36.03M requests, 99.04% of which were garbage, 0.75% passed through unscathed, and 0.199% were fed to the Cookie Monster. This required about 662.16MiB of memory on average, and 209.13GiB of absolute trash was generated for the nastiest visitors. Top garbage consumers were: - Disguised bots - 25.78M - Claude - 2.13M - Facebook - 1.19M - Aggressive maze explorers - 1.11M - OpenAI - 1.10M - Amazon - 428.96K - Commercial scrapers - 245.85K - Alibaba - 62.73K - Enthusiastic guestbook visitors - 28.02K - Huawei - 9.41K - Google - 79.05 Various other agents slurped through 368.51K pages of unhinged junk, bless their little hearts. In these trying times, 0.05% of all requests were likely of human origin: I hope you enjoyed your stay, and will visit again! Of all requests iocaine let into the garden, 73.49% were from Fediverse software. Thank you! #FediHug #AIStatsPorn
There we go! Request rate down from ~1k req/sec to ~150 req/sec within ~45 minutes. Caddy memory use is fine.
iocaine's CPU use is rather high, though. It's currently the dominating process on Eru. I suppose the firewalling isn't that cheap, and I'm still banning IPs at a high-ish rate.
Will have to profile this at some point. But for now, I'm glad it's working out well so far.
If all goes well, I will release #iocaine 3.4.0 on April 1st. A departure from my usual Friday releases, but... I can't not release on April 1st if I have the opportunity.
@tansy For websites, #Iocaine could help. https://iocaine.madhouse-project.org/ made by @algernon
I'm probably going to merge the dev/4.0 branch of #iocaine into main tonight, which means that the main branch will become incompatible with NSoE temporarily. In a couple of days, I will update NSoE's main branch too, and that will work with iocaine main, but not with 3.x.
NSoE has an iocaine-3.x branch, that will continue to function with 3.3. I will continue updating that branch for a while, until I put the main branch into prod, and even after that for a while.
Today is #iocaine 3.3.0 release day.
I'd like if it included a Grafana dashboard for the built-in script. But I'm yet to build one. It's very similar in shape to NSoE's, mind you... but I'd still need to do some work on it.
I've been postponing this since forever. But this is likely going to be the last 3.x release, I really, really should.
I'll go grind some spoons1, and see if I can manage.
Well, hello there The Pitt S02E11! ↩︎
tootbrute
a very strange trackball
Lukas Rotermund
Nelson
Petra van Cronenburg