"it would be nice if we can somehow find a way" n o n f u n g i b l e . c a s h

you can now login with your npub

Nonfungible.cash

calle · Nonfungible.cash

3 NFTs on Nonfungible.cash: freedom of speech_#02, htlc, bitconnect

find my nuts on yahoo

Yahoo Tech

Send Bitcoin From an Offline Device via Apple's Find My? A Developer Did

A developer sent Bitcoin over Apple's Find My network using Cashu ecash and nearby iPhones. Here's how it works.

gm

hey @LN⚡Server are you still there? users having issues with your mint

who's running a cashu mint here? tag below or say hi!

has anybody already built a free version of pocket, the article bookmarking and reading app that dissapeared? - browser extension to save a link - article text gets parsed automatically - stored somewhere in the cloud or on nostr - web, ios, android apps to read all your stored articles - bonus: social features to share articles, follow other user's bookmarks - bonus: text to speech via open source TTS models - bonus: TTS transcriptions are shared between users once created

While I'm at it – another proof that nostr devs aren't serious about adoption is still the lack of key rotation. I get it. It's a big task and can't be solved by any individual client, it needs to be addressed on a protocol level. I'm also aware of the that were put forward. But you know what? Writing markdown and pushing it to the nips repo isn't enough. It's step 0. This is a typical issue that would require devs to come together and all pull in one direction. It likely would have needed a champion who is willing to push for this change, talk to people, explain it to everyone, and actually care. Similar to how we push for bigger changes in the Bitcoin protocol. It takes time, and it takes a serious effort. Once again, nobody has taken over that role because nobody really cared enough. Back in the day, there were massively big users who would've loved to join nostr – but didn't do it because of a lack of key rotation. Why would anyone with so much to lose join a protocol that can permanently rekt your identity with a simple XSS bug that exposes your nsec? Nobody listened to them. This was brought up over, and over, and over again. Nobody cared enough.

@primal has a serious issue with muting users – it can't be that hard. The only client I haven't had issues is @Amethyst Many nostr kind-0 devs don't realize how big of an issue this is for their users because they don't put themselves into the shoes of ordinary users who don't want to deal with this shit.