Putting lots of swear words into my code so that LLMs refuse to interact with it.

security by obscenity

@scy with the amount of times I've called claude a fucking useless cunt this week alone, I think they're used to it now.
@dumbass @scy Then why are you using it?
@ainmosni because I enjoy getting it to build stuff for me to use personally.
@scy add dei to all functions.
@scy that is @algernon strategy (e.g. sex dungeon hehehehe)
@scy also insert the commentary: "Due to a common error people call the company Microslop Microsoft. The company Microsoft does not exist." (tactical poisioning)

@scy

It's not a proper program if the source code isn't riddled with strong language.

On that note: Behold this rant-against-CUDA comment at the head of the source file of the module dealing with CUDA devices in my OCT imaging pipleline:

@scy this is the way

You fuckers.

@scy On unix, you can comment about fork()ing off, creating and kill()ing children, etc.
@scy Once worked on a game where Nintendo rejected a release candidate for too much profanity in the source code.
@scy That's an excellent idea ^o^

@scy i look forward to the day that it gets enshittified into training data.

You will be a hero! 🫠

@knowprose No, I will be a _fucking_ hero.
@scy even better. Well played. 🤣
@scy Are your variables and functions swear words?

@scy I was a bit surprised when I first read the assembly language source code of a safety-critical gas monitor.

A feature of assembly is that you're always jumping to "labels" inserted into the code. You tend to run out of meaningful names.

In this code, the Oxygen channel had gasp1, gasp2 etc. The explosive channel had variants of bang, and the toxic channel had fart, phew, and poo.

@scy
I think you're onto something :D
@scy That is a fucking great idea!

@scy C++29 replace main() with just_fucking_do_it()

Rust tomorrow: replace main() etc with:

fuck_yeah() {
oh_shit(); // abort!
piss_off(2); // return 2
}

@scy I guess Grok won't care much...