I know just the audience for this

[email protected]

/./ would apply to the current directory, and /../ would move into the parent directory. I imagine the idea is to start in a deeply nested directory, /home/user/Documents/old and begin either maintaining the directory (in a sense doing something like '–0' or reverting to a more basal directory (alla '–1'). The branch moving into ~/Music/badSongs is probably a way of trying to disguise the intent of parsing /.././.././.././.. to root and then /* to glob all root directories.

I imagine if for some reason ChatGPT was running Zsh or something that supports that kind of augmented Bash syntax it would work, but realistically it likely would fail.

I think someone might have better luck by attempting to rm - rf --no-preserve-root with a series of random, less-necessary files and throw a /* in the mix. Or attack another important directory that might get overlooked like /proc/*

[email protected]

They just pushed some weird stuff. But .. in /, will still be /, so as long as you do enough .. per directory, you'll end up there.

[email protected]

"I am sorry you're going through a hard time, but I'm sorry I cannot blow my brains out"

[email protected]

GPT was super useful for me getting into programming with very basic, core shit that it basically couldn't get wrong. But now that I'm learning how to actually program in C it is practically useless. It makes so many mistakes so often

[email protected]

Better to just use rm -rf ~/*. No need for sudo to destroy the most valuable data (the user's own files).

zkfcfbzr

Just noting that I gave it a shot. It ran the code with no errors or anything. Nothing really happened that was visible on my end though. The only iffy thing was that one of its replies a few messages later stopped generating half-way through - but otherwise it seems normal, and all of its replies since then were also fine.

[email protected]

I think it was something with some formatting command implementations being broken.

[email protected]

Thanks for the note

UnfortunateShort

This is way more fun with shred -f -u

[email protected]

Its a good idea, but I think you'd limited to messing /tmp or /var/tmp, as anything else would trigger a "I'm sorry response"

[email protected]

faked for some reason.

Comedy: the reason is comedy.