This is why RAM costs over $900

Burgers are the food of the working man.

Testing some notes and other stuff.

Nostr has been a pleasant refuge from the AI slop and astroturfing that has engulfed Twitter. What will happen if the bot armies invade nostr one day? Are there any defenses?

another day in the code mines

Handling NIP-55 requests from amethyst is like trying to fill out a government form while getting repeatedly punched in the face. If you try to cover your face, you get kicked in the balls. So you have to juggle getting punched in the face, and kicked in the balls, and filling out forms. Then a robot guard catches you slacking, and executes you for being slow.

Oh boy

TIL about the invisible evil that is android proguard.

Pretty sure I have the craziest setup for signing notes and other stuff 😂

Blossom is pretty cool.

Posting this with igloo mobile via NIP-55. Almost there.

What are some popular use-cases for blinded keys? Asking for a friend.

Signer extensions are dead to me. Absolute dead-end for storing keys. They are the worst security nightmare. They don't exist on mobile. Browsers can't even agree on a spec. Time to rebuild the web3 promise with NIP-46 and PWA. It's so obvious. It just works. The age of nostr-RPC interfaces will be glorious.

What would a dating app on nostr look like? Some ideas: * use range proofs to obfuscate certain attributes like height/weight/age while still allowing for filtering and search * photos and personal info can be encrypted/decrypted using gift-wrapping techniques to obscure the original npubs that are behind each profile. * maybe something interesting can be done with lists and hash collisions? Similar interests would cause higher colission rates while obfuscating the list from brute-force searches. Also what would be the down-sides? Privacy concerns?

they are putting AI generator models on the internet that are turning the freaking memes ghibli

what is the rate limit on the damus relay? "you are noting too much" how much is too much? 😭

I put all this work into asynchronous batch handling of NIP-07 requests, and nostr clients just `await window.nostr.doSomething()` one request at a time. It's actually pretty crazy that clients behave like this. This old and busted synchronous request paradigm needs to change, especially for: * Primal, which requires signing of multiple events with each page refresh, all of them blocking. * Nostrudel, which has a "decrypt all" button, but then decrypts events one at a time. Does nos2x support asynchronous handling of requests? I didn't notice anything blocking, so I want to say yes (assuming you have permissions set). If a client makes requests to a signing device, and those requests have a) permissions and b) no dependencies, then they shouldn't block other requests. Let the requests flow freely!

me going through the jira backlog

gm nostr today is a great day to build a wallet