iso recording maxi

we had payment targets on profiles (even if it was just bitcoin), noone used them. zaps and one tap zaps are what got people to send money. if there's too much friction people won't use it. leaving the app to send some shitcoin that the receiver is not even notified of is a shitty experience. i think generalizing zaps is a good idea though. no reason that we need bolt11 on there, but should probably be a different kind at this point. View quoted note →

Idea: a lightning wallet interface where you can connect multiple nwc wallets and use it as a single wallet 🤔

nerd post ahead... strfry spawns a noteguard read-policy process for each read thread, so a naive per-IP rate limit actually enforces N× the budget. each process has its own counter. claude came up with a pretty cool fix: put the token buckets in a shared mmap'd file on /dev/shm. - open-addressing hash table - one tiny spinlock per slot (atomic compare-exchange) - fixed FNV-1a hash so every process maps an IP to the same slot now N processes share ONE authoritative bucket per IP. lock-free IPC, no daemon, no redis. just a file and some atomics. pretty neat! View quoted note →

"Out of ~7,700 active client IPs, only ~15 (about 0.2%) are throttled at any given moment, and it's a stable set. The throttle is doing exactly what you'd want: constraining a tiny set of heavy readers while the general population has plenty of budget." excellent View quoted note →

enabling 1MB per minute limit on the damus relay dropped the output bandwidth from 100Mbps to 15Mbps. bandwidth hogs can no longer DoS the server! i might be able to afford it now View quoted note →

november is crazy for gaming: 4th: wow forever launch 5th: oot remake 19th: gta vi

wow forever 👀

battlestation

when looking at the OoT sourcecode i thought the way morpha was coded was pretty clever. i got claude to do an interactive 3d explainer of how its rendered. this is why decompilation of old games is awesome!

How Morpha Is Rendered