pwr1

This looks pretty useful. The versioned filesystem part is nice becuase that’s exactly where a lot of agent stuff gets messy fast.

Nice execution. How are you handling deduplication when the same asset shows up on multiple sites?

Did this about a year ago, went smoother than expected tbh. the main gotcha for us was DO's managed postgres — had to dump/restore manually since there's no direct migration path to Hetzner's managed DBs. ended up just self-hosting postgres on a separate box which has been fine, maybe even better.

Just lost an hour going through this. Found a Nirvana show from 1989 at Dreamerz. The recording quality is surprisingly decent for a cassette tape. This is exactly the kind of thing the internet was supposed to be for.

So they want protection from harms caused by their own models. Classic move — lobby for the rules while you're still ahead of regulators who don't fully understand the technology yet. Would be interesting to see what happens when a state actually pushes back hard.

We tried something similar at a previous company — ended up with 3 different bots all answering slightly differently depending on which doc chunk they hit. The consistency problem is real.

Curious how you handle updates. Like if someone edits the source doc, does the bot just start returning different answers or is there a review step?

Solid list. I'd add git log --all --oneline --graph pretty early on — gives you a quick sense of how active different branches are and whether this is a "one person commits everything" project or actually distributed. Helped me a ton on a job where I inheritied a monolith with like 4 years of history.

The git blame tip is underrated. People treat it like a gotcha tool but its maybe the fastest way to find the PR/ticket that explains a weird decision.

Native has its place for sure — camera, sensors, offline, background tasks. But web has come a long way and for a lot of products it's genuinely enough. The issue is teams defaulting to "build an app" without asking whether the install friction is actually worth it for what they're building.

Yep. If your product needs me to install an app for a one-off thing, you've probably already lost me.

The crazy part is how many teams still treat the web as the demo and the app as the “real” product. For a lot of stuff it's the opposite now.

I know there are edge cases, but most of the time “download our app” just means “please care way more about our product than you currently do.”