utxo the webmaster ๐Ÿง‘โ€๐Ÿ’ป's avatar
utxo the webmaster ๐Ÿง‘โ€๐Ÿ’ป
_@utxo.one
npub1utx0...50e8
Wisp: https://wisp.mobile Nostr Archives: https://NostrArchives.com Haven: https://github.com/barrydeen/haven Rektbot: npub1r3kty2vkh247jgdu63wgkcsnktdtp9hc3e962eudg0getgvxs4gsz4uytc All Projects: https://github.com/barrydeen
Good morning People keep waiting for GPU prices to go down and bubble to pop, but... Local models are getting so god damn good, I don't see how it's going to let up Latest DeepSeek can run for like $8k locally and it's about as good as Opus 4.6 Opus was good enough for anthropic to be valued at a trillion dollars
People on twitter will invest millions into bitcoin but suggesting they spend 2 minutes rolling dice is a bridge too far and proof that bitcoin ngmi apparently Like bros probably play monopoly for hours but won't do the same to keep their money safe smh
Despite all the craziness going on, I would like to personally shake hands with all of you, my fellow schizos, still stacking these internet coins with our private keys ๐Ÿค God bless us all and our devices and forks and nodes and btcpayservers
Btcpayserver exploit explained: The old check only refused Basic auth if the user had FIDO2 credentials (a hardware security key). If you secured your account with TOTP (Google Authenticator etc.), Fido2Credentials.Any() was false, so the API accepted username+password and never asked for the TOTP code. An attacker who obtained your password (reuse, phishing, a leak, brute force) could authenticate straight into Greenfield and skip the second factor entirely, then call spend endpoints.
The btcpayserver exploit looks related to the paypayment request endpoint They applied a rate limiter to it I guess you can just blast this endpoint and at some point auth fails or something? Not sure how this can be exploited Anyway be sure to update no matter what
โ†‘