sReinwald
Joined 5 years ago
Joined 5 years ago
If it's only needed for one particular checkout, .git/info/exclude is the other obvious option.
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?Well, yes, because you invoked OpenCode with the --auto flag telling it not to stop for confirmation.
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.
Proving that to a jury looks very hard.
> Funny sidenote: The highest rate of foreign migrants into the palatinate region --- where the amish came from --- is now from US citizens
For anyone wondering whether this reflects some strange Amish return migration: almost certainly not. It’s overwhelmingly the result of the enormous US military presence around Ramstein, Landstuhl, and Kaiserslautern. It's also not exactly a recent development.
This isn't surprising to me at all.
The World Cup is on, and it draws attention away from politics. This has been a pretty common observable pattern for as long as I can remember.
> Even if you buy the expansion just to get the "feel" on how it was, it's impossible.
You don't buy previous expansions after a new one launches - they roll into the base subscription. After Shadowlands released, buying BfA separately wasn't even an option.
> MMOs like GW2 and even SWTOR do it way better
“Keep every expansion fully relevant forever” sounds nice until you think through what that actually means for an MMO like WoW. You would either fragment the player base across twenty years of content or turn gearing and balance into a complete circus.
Imagine your best-in-slot trinkets from the current raid and Siege of Orgrimmar, your tier set from Dragon Soul, the weapon from Hellfire Citadel. Try organizing a group when other classes need gear from Icecrown Citadel, The Everbloom, Argus and Ahn'Qiraj.
The point of "current expansion content is relevant" is that it funnels the player base into a fairly narrow area of the theme park. That is important, because if you spread out the population over 20 years worth of content, you risk making the world feel incredibly empty, which is a death sentence for a theme park MMORPG.
Blizzard’s actual approach is much more sane: older content comes back in controlled ways. Timewalking reopens older expansion content with scaling and relevant rewards, and Mythic+ seasons already rotate older dungeons into the current endgame pool. Midnight's Season One, for example, features dungeons from Wrath of the Lich King, Warlords of Draenor, Legion, and Dragonflight.
Work and homelab overlap constantly for me though. I make heavy use of periodic notes, so even something like recipes would get linked in weekly logs for meal planning or tracking. The connections don't have to be deep to be useful - sometimes it might just be 'I made this thing on this day' and that's enough context to be worth having in one place.
Multiple vaults break this. You end up duplicating notes, or linking across vault boundaries (which adds friction), or just forgetting where you put something. That's trading one of Obsidian's strongest features for... tidier folders.
The one case where I do split things out is genuinely isolated project knowledge - like a D&D campaign I used to GM. 99% of those notes have zero connection to anything else. Separation makes sense there precisely because there's nothing to link.
One more thing: a lot of people solve the "big vault gets messy" problem with elaborate folder structures, but Obsidian's search (especially with Omnisearch) makes most of that unnecessary. I don't really organize my notes into careful hierarchies. I write them, link them, and search for them. The mess is fine. I am one with the mess.
Containerization only helps with the second one, not the first, but that still matters. If you’re going to run random third-party MCP servers, isolating them from your host and any sensitive local data is still an obvious improvement over no isolation.
If capitalism requires constant vigilant government intervention to prevent monopolistic practices, anti-competitive markets, and asymmetric bargaining power, then it seems to me that this is absolutely a complaint about capitalism. If anything, your comment just makes the indictment more damning.
This happens because most people just paste a draft and say "make this better" with zero style direction. The model defaults to its own median register, and that register gets very recognizable after you've seen it a hundred times.
But this is a usage problem, not a fundamental one. I actually ran an experiment on this — fed Claude Code a massive export of my own Reddit comments, thousands of them across different subreddits, and had it build a style guide based on how I actually write and argue. The output was genuinely good. It sounded like me, not like Claude. The typical Claude-isms were just about gone.
I wouldn't expect most people to do that. But even a small prompt adjustment makes a real difference. Compare "improve this email" to something like:
Your job is to proofread and edit the following email draft.
Don't make it longer, more formal, or more "polished" than it needs to be.
Fix anything that's actually wrong (grammar that changes meaning, tone misreads).
Leave stylistic roughness alone if it fits the voice.
If the draft is already fine, say so.
That preserves voice way more than the default "Hello computer, pls help me write good" workflow.But if we're being honest, most people don't care about preserving their voice. They need to email their professor or write a letter to their bank, and they don't want to be misunderstood or feel stupid.
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.