When A.I.’s Output Is a Threat to A.I. Itself
www.nytimes.com
As A.I.-generated data becomes harder to detect, it’s increasingly likely to be ingested by future A.I., leading to worse results.
  • Admiral Patrick@dubvee.orgEnglish
    100·
    3 months ago

    My takeaway from this is:

    1. Get a bunch of AI-generated slop and put it in a bunch of individual .htm files on my webserver.
    2. When my bot user agent filter is invoked in Nginx, instead of returning 444 and closing the connection, return a random .htm of AI-generated slop (instead of serving the real content)
    3. Laugh as the LLMs eat their own shit
    4. ???
    5. Profit
    • mesamune@lemmy.worldEnglish
      38·
      3 months ago

      I might just do this. It would be fun to write a quick python script to automate this so that it keeps going forever. Just have a link that regens junk then have it go to another junk html file forever more.

      • capital@lemmy.worldEnglish
        13·
        3 months ago

        Also send this junk to Reddit comments to poison that data too because fuck Spez?

          • capital@lemmy.worldEnglish
            6·
            3 months ago

            That’s a little different than what I mean.

            I mean to run a single bot from a script which interacts a normal human amount during normal human times within a configurable time zone which is acting as a real person just to poison their dataset.

    • ScrolloneEnglish
      7·
      3 months ago

      This is a great idea, I might create a Laravel package to automatically do this.