u/CryptoExo

Something I’ve thought about for years and never managed to talk myself out of.

Everything that tells you you’ve lived a whole life is sitting in your brain at this moment. Your memories, your childhood, what you did yesterday. If you’d only been conscious for the last second you’d still have all of that and it would feel exactly like it does now. There’s no way to tell the difference from the inside.

So I don’t believe in a continuous self. Your brain tells you there is one and you’ve got no way of checking.

I also don’t think time flows. The block universe idea in physics says past, present and future all exist together, like a film reel where every frame is already there. Relativity makes it more complicated than that but that’s the gist. Your life is a line through it and every point on the line thinks it’s now.

What I actually believe is that the universe itself is conscious at the fundamental level, in ways we can’t understand. Our brains are just equipped to give us the illusion that we’re conscious as individuals, with our own experiences. There’s really only the one thing and we’re all it, each convinced we’re separate because we only have our own memories.

Not sure if it's just me but I've enabled AV1 on my web browser profile, also tried in the Windows app. The HDR option is greyed out in every game that I've tested.

When can we expect HDR support to arrive?

Opus 5 performs well at agentic coding but as an orchastrator it always seems to find something more to do when all the criteria has been met and there's nothing more to do, resulting in an endless workflow.

The moment we switch to Fable for orchastration our workflow finally begins to clear.

This is noticeably worse in 5 than in earlier Opus models.

Should we avoid using Opus 5 for orchastration, or is this a skills issue?

I sat on this decision a little too long. The "what if we're missing something" anxiety kept me on GitHub a few weeks longer than it needed to. Finally pulled the trigger on a self-hosted Forgejo instance, and I'm kicking myself for not doing it sooner.

The honest summary: it ticks every box we actually needed. Repos, PRs, issues, CI/CD via Actions-compatible workflows, the lot. Nothing on our day-to-day list went missing in the move.

What's genuinely changed for us:

• No more subscription line item. It's just running on our own hardware now. That recurring cost is gone.
• No Actions rate limits or overage charges. Our runners, our minutes. We're not watching a usage meter or budgeting for excess. CI just runs.
• It stays up when GitHub doesn't. Every time GitHub has a wobble and half of dev Twitter is melting down, our stuff keeps ticking along. That alone is worth a lot for peace of mind.
• The data is ours. It lives on our infrastructure, fully under our control. No "where is this actually hosted and who can touch it" question marks.

Fair caveat so this doesn't read like an ad: self-hosting means you own the uptime, backups, and upgrades now. If you're not comfortable running infra, that trade-off is real. But if you already manage servers, the operational overhead has been minimal — it's a well-behaved, lightweight piece of software.

Anyone else made the jump? Curious what edge cases bit people post-migration, especially around Actions workflow compatibility and migrating issue/PR history.

https://preview.redd.it/j76ouo70qm1h1.jpg?width=3060&format=pjpg&auto=webp&s=9f096c62140ba9933a4d2254c887019f8deafe4f

If you're stuck in a reboot loop after installing Windows 11 update KB5089549, you've probably noticed your display flickers several times before the machine restarts. Here's what worked for me:

The workaround

If you have a 4K display, switch it off completely (not just standby) while the PC boots, then switch it back on once you reach the login screen. Some systems get into a bad state on boot when negotiating with the 4K panel.

Other things worth checking

• BIOS is set to UEFI boot mode (not Legacy/CSM)
• Secure Boot is enabled
• CSM (Compatibility Support Module) is disabled

Hope this helps someone!

Was thinking about this the other day while running Claude Code.

Back in the 60s and 70s, computers were too expensive for most people, so offices had dumb terminals hooked up to a central mainframe. All the heavy lifting happened somewhere else, and the box on your desk was basically a keyboard with a screen. Then PCs got cheap and powerful through the 80s, client-server architecture took over in the 90s, and most workloads migrated off the mainframe and onto kit you actually owned. (Mainframes never fully died — banks and airlines still run them — but they stopped being how most of us worked.)

Fast forward to now. Gigabit fibre, low-latency everything, and what am I doing? Sitting in a terminal, typing prompts that get shipped off to a datacenter so a model bigger than anything I could run at home can write my code for me. My laptop is genuinely more idle running Claude Code than it was compiling C++ in 2005. The terminal is back. The mainframe is back. We just call it "the cloud" and the green phosphor got replaced with syntax highlighting.

What I've noticed is the same old mainframe-era trade-offs are creeping back into my actual workflow:

No persistent state between sessions. I've ended up writing increasingly detailed CLAUDE.md files and leaning on MCP servers to give the "mainframe" some context about my project.

Connection = productivity. A flaky link or an Anthropic blip and I'm dead in the water. Never used to care about my uptime this much when everything ran locally.

What goes over the wire matters. I think harder now about what context to send vs. keep local — secrets, proprietary code, big binaries. Same calculus as deciding what to run on the mainframe vs. the terminal back in the day.

Billed by usage, not ownership. Tokens instead of CPU-hours, but the economic model is identical.

The scrappy local alternative is back too, except now it's Ollama and llama.cpp instead of the Altair and the Apple II.

So a few questions for the sub:

Do any of you keep a local model (Ollama, llama.cpp, etc.) as a fallback for when Claude Code is down or rate-limited, or do you just accept the dependency?

How are you handling the no-persistent-state problem — pure CLAUDE.md, custom slash commands, MCP servers, something else?

Anyone running a hybrid setup where a local model handles grunt work (boilerplate, renames, simple refactors) and Claude Code handles the hard stuff?

Curious whether we'll swing back toward local once consumer hardware catches up, or whether centralised AI coding is just the natural endgame given how expensive frontier training is.