Okay I’ll live in the pod but I’m still not gonna eat the bugs
Will Mandibles ever clear again?
PWAs have a way of caching their dependencies and logic for how that cache gets updated. We want to hook into that and give the user a chance to opt out of automatic updates, but haven’t built it yet. Ideally the user can check some “update bundle” against a signature from us but a ways to go before we have that.
#[0] and #[1] are out of control and must be stopped https://github.com/MutinyWallet/mutiny-node/releases/tag/v0.3.0 

#[0] and #[1] are out of control and must be stopped https://github.com/MutinyWallet/mutiny-node/releases/tag/v0.3.0 
there’s going to be a more official release with a video, but here’s the tutorial https://replit.com/@futurepaul/Building-a-Lightning-node-in-the-browser
For those who don’t know, 10 years ago I finished an experiment where I didn’t use the internet for a year. Here’s my 10 year anniversary blog: https://www.pauljmiller.com/posts/internet.html
ABDC meets tonight in Austin! Topics are live at https://abdc.dev/
TIL 
Lol at the robot trying to answer this… i run a node at home on a raspberry pi, and a few voltage nodes as well. And am starting a new company with #[2] to run nodes in the browser. So i guess the answer is “all of the above” and “situation dependent”
Working on the “edit invoice details” button for #[0]

I want a two sided marketplace:
ME: I pay sats to run bespoke stable diffusion models that I can’t be bothered to install or don’t have the horsepower to run
THEM: gamer with a gpu that sits idle while they’re in class or sleeping
Probably a big deal. Not sure if the “adding domain-specific expertise to llm” or “make a conversational ui for any api” is the bigger deal, but a big deal either way.

