Show threadlendulado1d ago

He atinado con la solución a lo de iocaine: la versión en debian es muy antigua, actualizándola a la última ya funciona.

#iocaine #debian #caddy

Show threadlendulado1d ago

2. Quería configurar iocaine en el VPS que tengo. Sigo todo el manual de instalación, se ejecuta bien de forma local, pero cuando le pongo delante el reverse-proxy con Caddy, aún siguendo la configuración del manual, falla. Cuando se intenta acceder a la página, el navegador encuentra problemas, como si el fallo que da a los bots se lo devolviera al navegador. Aquí creo que es más tema de que la versión de Caddy en el VPS tiene casi 4 años de antigüedad y no entiende la conf.

#caddy #iocaine

political campaign enjoyer2d ago

I'm happy to announce the availability of iocaine 3.4.0-rc.1, first (and hopefully only!) release candidate for the #iocaine 3.4.0 release scheduled for April 11st.

Despite still being a 3.x version, this does introduce a breaking change: the firewalling code has been redesigned. This means a different API on the scripting side, and its configuration no longer lives in the handler's config.

Even though a breaking change, the feature was explicitly labeled experimental, so I'm committing SemVer sins, and am not bumping the major version.

Cookie monster!

political campaign enjoyer3d ago

Time to roll up the sleeves, and cut an #iocaine 3.4.0-rc.1 release.

Good thing I did most of the preparation yesterday.

tootbrute4d ago

already blocked 84 AI bots in less than 24 hours using #iocaine. this is awesome!

 suck it ai.

political campaign enjoyer4d ago

I planned to release #iocaine 3.4.0 on April 1st, but I am reconsidering that.

I rushed 3.3.0, and  that turned out to be a mistake, I had to rework much of the firewall feature for 3.4.0. I do not want to make the same mistake again, 3.4.0 should be a release I can comfortably end the 3.x series on.

So the new plan - because I do want to release something on the 1st! - is to release iocaine 3.4.0-rc.1 instead. This satisfies the desire to have a release that's a strict improvement over 3.3.0, but one where I can still fiddle and stabilize things before the final release.

The 3.4.0 release should follow a week and a half after, on the 11th. That is also a departure from my usual Friday releases, but April 11th is the day of Hungarian Poetry1, and I'm a sucker for releasing on special days.

  • And the anniversary of our wedding. ↩︎

    • tootbruteMar 28
    Wonder if #iocaine will be released as a #caddy plugin one day. For now I should try caddy defender.
    Show threadpolitical campaign enjoyerMar 27

    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).

    Show threadpolitical campaign enjoyerMar 27

    fakejpeg-rs 0.2.0 released, and I merged #iocaine's dev/4.0 branch into main, and thus begins the 4.0 development for real.

    3.4 will be released from the iocaine-3.x branch, main is now free to break backwards compat, and it already did, by upgrading #Roto to 0.10.0.

    Lukas RotermundMar 26

    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 #AI #LLMs #FightAI #selfhosting

    Fighting AI and LLMs with iocaine

    In this post, we will take a look at iocaine, the deadliest poison known to AI, and we will cover the reasons why I use it to protect my blog and all my other self-hosted services.

    Lukas Rotermund