lightcap

@lightcap.eth

Buidling web3 from a shed in the woods. Human—for now. Remember kids: Wallets in browsers, not browsers in wallets

538 following1.8K followers

Latest casts

lightcap@lightcap.eth·

Careful out there kids. This is at least the second iteration of this phishing ad. Keep those seed phrases safe.

lightcap@lightcap.eth·

Gotta give it to the folks working on Opencode. I prefer the clean design of their TUI by *miles and miles* over any other TUI/CLI interface. Honestly, it's beautiful and so well thought out. Open source winning a lot these days.

lightcap@lightcap.eth·
Reply

This is largely why I've been so quiet round these parts for the last few months.

lightcap@lightcap.eth·
Reply

All those things matter, but they still end up in runtimes.

lightcap@lightcap.eth·
Reply

I'm trying to fix it at a structural level right now. Building codezero.io

lightcap@lightcap.eth·
Reply

Gotta keep those agents running bruh

lightcap@lightcap.eth·

Who else is moving to self-hosted gitlab? After 18 years I can't believe I have to, but here we are.

lightcap@lightcap.eth·
Reply

What the industry seems to ignore is that it doesn't matter where you store your secrets if you stuff them into the runtimes. There's dozens of ways to leak/exfil creds in runtimes. AI and agents have just made it exponentially more common/worse.

lightcap@lightcap.eth·
Reply

It's also so much more than not being in the repo. Scanners can catch that. Though some insane percentage of caught secrets in repos aren't ever removed. And those that are aren't *truly* removed. They stay in the objects unless you use something like BFG to rewrite it all.

lightcap@lightcap.eth·
Reply

They're mostly for github actions. But yeah, they do. Better way is OIDC, but so few people bother with anything but the easiest option.