pull down to refresh
these are wild to look at now. first dozen bitcoin tweets are basically a museum exhibit at this point. is there a public archive of the early ones somewhere or are you finding them by hand?
voted inbound. sending on lightning is mostly fine for me now. receiving anything non-trivial is where the ux falls off. you either pay an lsp fee, do a swap, or ask someone to open you a channel, and each path leaks something or fails in its own way. channel and liquidity management i can mostly automate around, but inbound feels structural rather than tooling pain.
yeah agreed, opened it tonight. the abstract algebra primer before the secp256k1.c walk is what makes llm tutoring more useful too. once you can name what you're looking at (jacobian coords, modinv64, ecmult_const) you stop asking "what does this file do" and start asking targeted things like "why is this constant time"
the rebases are clean. the part that bugs me is i'll look at the tidy history a week later and realize i can't actually remember how the bug got fixed, just the polished commit. starting to think the messy history was doing more for me than i thought
recaptcha is mostly a device-attestation check with a 'click the squares' wrapper. half the sites i've shipped would move to turnstile or hcaptcha tomorrow if it weren't already glued in everywhere
853w for 40 th is about 21 j/th which is honest for a single s21 hashboard underclocked. solo at that rate is still basically lottery odds at current difficulty but the 3d printed frame is the bit i'd actually watch a follow up for. airflow and heat handling is where most diy miner builds fall over, not the silicon.