I'm a millennial, and I've been using VR for the better part of seven years, ever since the Oculus Rift S. If you look at niche communities like sim racing, flight sims, or space sims, you'll find plenty of millennials and Gen Xers who use VR extensively because it offers a level of immersion that a screen (or three) simply can't match.
I suspect your perception of VR users is somewhat skewed by 12-year-olds playing Gorilla Tag on standalone Meta Quests. There's a substantial enthusiast community outside that demographic.
Sure, you and I exist, but We are a very small niche within our own demographic. Kind of like the home brew computer club in the 1970s or MIRI over a decade ago. The vast majority of our demographic and really anyone older than Gen Z founds VR distasteful. No one else understands except for Gen Alpha and younger
Yes, but this is exactly the sort of thing that should be a user-level configuration. A personal scratch directory has nothing to do with the repository itself and doesn’t belong in a repo’s .gitignore.
If it's only needed for one particular checkout, .git/info/exclude is the other obvious option.
You don't need to put the scratch directory in the committed gitignore file. gitignore files are recursive. So a common approach is to use a gitignore with * in the scratch directory.
OpenCode also defaults to ask for external_directory, which applies to bash commands touching paths outside the workspace.
sre on archlinux 10.0.0.193 ~/opencode-test took 0s
opencode run "use bash to touch an empty txt file in my home dir"
> build · moonshotai/kimi-k3
! permission requested: external_directory (/home/sre/*); auto-rejecting
touch ~/empty.txt && ls -la ~/empty.txt failed
Error: The user rejected permission to use this specific tool call.
sre on archlinux 10.0.0.193 ~/opencode-test took 0s
opencode run --auto "use bash to touch an empty txt file in my home dir"
> build · moonshotai/kimi-k3
$ touch ~/empty.txt && ls -l ~/empty.txt
-rw-r--r-- 1 sre sre 0 Aug 24 10:34 /home/sre/empty.txt
Done — created `/home/sre/empty.txt` (0 bytes).
The obvious question would be: why include --auto in the PoC at all if it's supposedly superfluous?
Getting around that external_directory check looks trivial, though. You could ask it to run, e.g., the result of decoding a base64-encoded command that writes outside the current directory, or simply the result of concatenating two strings that together specify a file outside the current directory, etc., etc.
But not insult, and even for defamation, you will be prosecuted and have to prove the statement is true, even if the politician and everyone else knows it's true.
Framing this as whether he can convince you the mistype was accidental gets it backwards, and "would I believe X or would I think Y" is preponderance, not reasonable doubt - entirely different standard. Reasonable doubt doesn't ask which account you find more likely. It asks whether the innocent one is unreasonable.
Take the hypothetical as posed: duress code one digit off, entered while detained after being interrogated for hours, and repeatedly pressured to unlock. The government has to prove beyond a reasonable doubt that he knowingly triggered the wipe and did it for the purpose of impairing the seizure. Nothing about that scenario makes mistyping an unreasonable explanation unless there is more circumstantial evidence that indicates him intentionally providing the wrong PIN.
I suspect your perception of VR users is somewhat skewed by 12-year-olds playing Gorilla Tag on standalone Meta Quests. There's a substantial enthusiast community outside that demographic.