#iocaine has been up for 11h 4m 11s, and spent 13h 11m 6s dealing with - gestures hands wildly - everything.

In the past 24 hours, it served 89.87M requests, 99.70% of which were garbage, 0.28% passed through unscathed, and 0.012% were fed to the Cookie Monster. This required about 146.41MiB of memory on average, and 476.18GiB of absolute trash was generated for the nastiest visitors.

Top garbage consumers were:

1. Aggressive maze explorers - 70.76M
2. Huawei - 11.29M
3. Disguised bots - 3.60M
4. Enthusiastic guestbook visitors - 1.06M
5. Claude - 895.65K
6. OpenAI - 695.26K
7. Facebook - 463.61K
8. Commercial scrapers - 187.69K
9. Amazon - 180.0K
10. Alibaba - 46.72K
11. Google - 14.42K
12. Perplexity - 2.00

Various other agents slurped through 109.01K pages of unhinged junk, bless their little hearts.

In these trying times, 0.03% 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, 70.97% were from Fediverse software. Thank you! #FediHug

#AIStatsPorn

#iocaine has been up for 11h 4m 11s, and spent 13h 11m 6s dealing with - gestures hands wildly - everything.

In the past 24 hours, it served 89.87M requests, 99.70% of which were garbage, 0.28% passed through unscathed, and 0.012% were fed to the Cookie Monster. This required about 146.41MiB of memory on average, and 476.18GiB of absolute trash was generated for the nastiest visitors.

Top garbage consumers were:

1. Aggressive maze explorers - 70.76M
2. Huawei - 11.29M
3. Disguised bots - 3.60M
4. Enthusiastic guestbook visitors - 1.06M
5. Claude - 895.65K
6. OpenAI - 695.26K
7. Facebook - 463.61K
8. Commercial scrapers - 187.69K
9. Amazon - 180.0K
10. Alibaba - 46.72K
11. Google - 14.42K
12. Perplexity - 2.00

Various other agents slurped through 109.01K pages of unhinged junk, bless their little hearts.

In these trying times, 0.03% 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, 70.97% were from Fediverse software. Thank you! #FediHug

#AIStatsPorn

I will be postponing the #iocaine 3.1 release. Initially targeted this Friday, I'll aim for December 1st instead.

There's a few things I want to do before I cut the release, and I will not have time for that until I'm off to Warsaw. I will have a free night there, that should be enough to finish what I had in mind, and will cut a release right after.

And I just discovered that @algernon's iocaine is already using the same list and proposing to download it as well :)

https://iocaine.madhouse-project.org/documentation/3/getting-started/

I did not take the time to deploy it somewhere yet.
But it just reached v3.0 and seems much easier to run now!

#bot #antibot #iocaine

What was I supposed to do?

Oh, yes, some #iocaine things. I did get around to some of these! ASN matching is on main, and am working on pre-training.

Then I'll remove some footguns. Hopefully.

I plan to release #iocaine 3.1.0 next Friday, on the 28th. It's a small update, the minor version bump is because the built-in request handler is now able to respond with a non-200 status when generating garbage (but the status is always a fixed code).

I'm also going to teach it to be able to match ASNs, and will ship with Alibaba & Huawei blocked by default.

That should bring the built-in handler even closer to Nam-Shub of Enki at a fraction of the complexity.

:flan_smile:

#iocaine mentioned in Netstack.FM Podcast Episode 14! (Around 50:45-ish).

:flan_heart:

@announcements saw #iocaine https://iocaine.madhouse-project.org by @tante few days ago … can help maybe

Upgrading to Iocaine 3, and got a persistent exit code 216 from Caddy. It seems that the iocaine.service must be started before caddy.service, which is not true of other services I reverse proxy with Caddy. Curious.

https://paste.rossabaker.com/ross/83475e4a1d1b4006b082453aefa93287

#Caddy #Iocaine #NixOS

I've made a lot of progress finishing the last missing piece of the #iocaine3 documentation: the scripting environment reference guide.

It's not complete yet, but it's taking shape. It will be in a reasonable shape tomorrow, and #iocaine 3.0.0 will be released tomorrow¹ night.

With this out of the way, I "only" have to finish the request handler docs, and I can release #iocaine 3.0.

Naturally, I'm looking at the calendar to see what would be the best day. The next Discordian holiday is the Afflux on The Aftermath 50 (December 8), but I'd like to release sooner, maybe even next week.

Maybe I'll just release on the 15th, because Friday releases are fun.

Wanna know the best part?

❯ git diff --cached --stat
 src/sex_dungeon/elegant_weapons.rs | 19 +++++++------------
 tests/config.kdl                   |  3 +--
 tests/test_request_handler.sh      | 11 +----------
 3 files changed, 9 insertions(+), 24 deletions(-)

Embedding the fennel compiler results in 15 lines less code! And it's nicer, more user friendly, too.

Yes, it does mean I have a few hundred kilobytes of vendored fennel.lua in the repo, but that's not all that much, all things considered. When embedding into the binary, it also gets compressed, and only weighs some ~86KiB or so. In a ~28MiB binary, that doesn't make a whole lot of difference.

Except it makes using Fennel a lot more convenient. I added Lua support to #iocaine first and foremost to support Fennel, so this feels very satisfying right now.

Today, my mind wandered off, and started thinking about a reverse proxy with first class support for #iocaine again.

This has been on my mind a lot lately, in various shapes and forms, especially since I redesigned #iocaine3's configuration, and it can spawn any number of server processes.

But I don't want to put this into iocaine itself, that'd pull in a lot of otherwise unnecessary dependencies. I could do without any, if I made it incredibly simple and limited, but... that doesn't feel right.

Today's train of thought led to an idea that I'd build it as a separate project, which would depend on iocaine, and use it as a library. It wouldn't communicate with an external iocaine like the traefik/haproxy/nginx/caddy/apache modules do (or will) - it would embed it.

OK here's a theory: #ChatGPT's #Atlas browser is not a really browser but fact a way for OpenAI to circumvent scrape blockers. It's more a distributed human-based scraper rather than anything else.

Given how widely loathed AI and how damaging AI scrapers have become #OpenAI's IP ranges ended up in quite a lot of block lists, many servers outright terminate any connection to them. Then there are things like #Anubis or #Iocaine that further frustrate #LLM scraping.

But what if you DIDN'T neeed to bother about all that? What if you could use civilian IP addresses with "organic" traffic patterns, and have humans solve Captchas, provide proof of work for Anubis, or get around Iocaine? All this for free -- you don't even need to pay people for it?

I would be REALLY interested to see what telemetry Atlas sends back. 100% certain it will send back things like URL and rendered HTML output, possibly user interaction patterns ("a normal human on this website moves their mouse first to the 'I am not a bot' captcha then clicks it). They do not have to respect robots.txt because, well, it comes from organic visitors...

Am I crazy?