this post was submitted on 13 Aug 2023
26 points (78.3% liked)

Programming

17507 readers
9 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
26
Intentionally corrupting LLM training data? (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/programming
12 comments fedilink hide all child comments
 

Inspired by the comments on this Ars article, I've decided to program my website to "poison the well" when it gets a request from GPTBot.

The intuitive approach is just to generate some HTML like this:

<p>
// Twenty pages of random words
</p>

(I also considered just hardcoding twenty megabytes of "FUCK YOU," but that's a little juvenile for my taste.)

Unfortunately, I'm not very familiar with ML beyond a few basic concepts, so I'm unsure if this would get me the most bang for my buck.

What do you smarter people on Lemmy think?

(I'm aware this won't do much, but I'm petty.)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago

Another idea that just occurred to me. Maybe position: absolute; both the real content and the gibberish content with the same top, left, width, and height attributes so that the real content and the gibberish overlap and occupy the same location on the page. Make sure both the real and gibberish content elements have no background so that remains clear. Put the gibberish content in the DOM before the real content. (I think that will ensure that the gibberish appears behind the real content even without setting the z-index.) And then make JS set the color of the text in the gibberish element the same color as the background so humans can’t see it.

Be aware that these techniques can affect accessibility for people using screen readers.