Gordon

I keep re-learning this lesson: block it out before you jump into detail work

feeling disenchanted. longing to return to the simple ways of a medieval peasant. raking muck, eating gruel, knowing my place, with no access to modern dentistry. a meaningful life.

this is cool

Soon we’ll reach the tipping point where the PR reviews are also AI generated. Sloppen Source software. newsletter.squishy.computer/p/is-open-so...

A Game of Thoughts - shimmeringvoid My personal guide to navigating the imaginal plane

🃏 what if you could turn 'ideation' itself into a game? what are the mechanics? the systems? the underlying physics?

welcome to part one of me trying to reverse engineer my imagination

“The illiterate of the future will not be the person who cannot read. It will be the person who does not know how to learn."

Just According To Keikaku As A Service

different tools, different jobs, and not incompatible

data has to get to client somehow

also cool

:0

I think view transitions may also offer some flexibility here. Less static pages with view transitions, more each page is a small SPA. In-page VT for the minor transitions, Page-2-page VT for the major transitions.

...Tradeoff between determinism and complexity. EAP is deterministic but state management is complex. MB is simple but not as deterministic. Both have great debugging properties. And if you can break the app into smaller bits, then I think simplicity of msg bus may win.

I've come to believe there are basically two good architectures for apps:
- Elm App Architecture: strict tree of state machines
- Message bus: no direct parent-child relationships, everything connected via messages over one bus

It's just something that I've been playing with... Simplest version:
- Components emit custom events for requests like "toggle sidebar"
- Sidebar component listens on window for bubbled "toggle sidebar" events.

Components don't need to know about each other, they just pub/sub custom events.

This is the move many game engines make. When you have levels that let divide state into coarse-grained buckets, state management often becomes an order of magnitude simpler. MPA ~= video game levels, where each page is a level. View transitions provide seamless transitions between levels.

Ok, I think I'm all in on CSS view transitions. The new stack:

MPA + view transitions + web components + island architecture w message bus

No complex state management. This is going to simplify app dev by an order of magnitude.

Kintsugi: Decentralized E2EE Key Recovery Kintsugi is a protocol for key recovery, allowing a user to regain access to end-to-end encrypted data after they have lost their device, but still have their (potentially low-entropy) password. Exist...

📄✨ New paper! Emilie Ma (kewbi.sh) and I looked at the problem of users of end-to-end encrypted apps recovering their private keys if their device is lost, broken, or stolen. We found a cryptographic approach that is decentralised and resilient against social engineering arxiv.org/abs/2507.21122

New Zuck post, what a difference a few years makes:

Today: "We'll need to be rigorous about mitigating these risks and careful about what we choose to open source."

2024: "Meta is committed to open source AI... and therefore a platform that will be around for the long term."

usually the baseline is “nothing” so the right heuristic is usually not “is it ideal” but rather “is it better than nothing?”

TIL the quality of commodity 3D printers has improved a lot. Look at that... Smooth. No lines. Nice.

SpecTree: Composable Instructions What would React for context engineering look like?

Transclusion for context engineering www.fuzzycomputer.com/posts/spectree

atproto record type for "i've been pwned", which includes a signature from the responsible account, enabling interoperable bi-directional verification of account hacks

Conclusion So claude sucks. It can’t solve any hard problem. But… people really underestimate the amount of open source maintenance that is not hard problems. There is a ton of tedious stuff to do. I am behind on bumping dependency compatibilities, writing docstrings for things I wrote a summary on Discourse/StackOverflow, solving little interface issues, bisecting failures, etc. So basically a lot of that: Refactoring Easy trivial PRs and requests Documentation improvements Compat testing Bisecting who/what change caused a problem I have had to spend like 4am-10am every morning Sunday through Saturday for the last 10 years on this stuff before the day gets started just to keep up on the “simple stuff” for the hundreds of repos I maintain. And this neverending chunk of “meh” stuff is exactly what it seems fit to do. So now I just let the 32 bots run wild on it and get straight to the real work, and it’s a gamechanger.

(cont.)

"So claude sucks. It can’t solve any hard problem.

But… people really underestimate the amount of open source maintenance that is not hard problems."

discourse.julialang.org/t/the-use-of...

rust tooling is god tier

wild how cargo is so good that cargo installing from source is often more convenient than getting the bin. rust is so nice.

Web resources are accessed by URLs (Uniform Resource Locators), meaning they belong to a single location. This makes web content centralized, vulnerable to lock-in, link rot, and censorship.

We should decentralize the web somewhat.

It's the weekend. Anybody want to talk about BLAKE3?

You only need 3 ingredients to do this.
1) A fixed cryptographic hash function (sha256 for us)
2) A fixed chunk size
3) A deterministic tree structure
That's it! Blake3 comes with this these built-in, but they aren't magic.

nvidia should add a soul coprocessor