Executive Order 69420 is coming for your Bitcoin through ANY third-party custodian that holds sats for you. You've been warned.

If you have a Nostr client that does not support Amber login yet, I do not use it, and cannot recommend it. If you have a Nostr client with DM capabilities and do not support at least NIP-17, I do not use it, and cannot recommend it.

Better yet, I'm an extremist paranoid Bitcoin anarchist. No more compromises. With extreme prejudice.

I'm an extremist paranoid crypto anarchist. No more compromises. With extreme prejudice.

@ZEUS 0.9.1 is out with blinded paths for BOLT11 - This offers privacy on the receiving end of a transaction. Do everyone a favor, and UPDATE now. If you don't use app with blinded paths, do everyone a favor, and get ⚡ Zeus ⚡ Easily downloadable from the @Zapstore Thank you!

**Puts Tinfoil Hat On** People on twitter keep talking about google removing the price chart and causing price suppression - They're missing the bigger picture. Google removed the price chart, funneling people into and promoting pump&dump rugpull schemes such as XRP IN ORDER TO keep people poor and in debt. If you don't use google AND you stack sats you've got nothing to worry about. **Prepares for a barrage of self-proclaimed cypherpunks who can't leave Google because of XYZ**

Looking to contribute some code for the first time? Joining the open-source revolution? Flotilla, a Discord-like on Nostr, has some issues just for you. Check it out.

GitHub

coracle-social/flotilla

A nostr relay-based communities PWA modeled after discord - coracle-social/flotilla

Anyone run a nostr-rs-relay that could give me a few pointers for configuring mine? It's been running great for general posting but I've noticed some general slowness particularly on the DM side of things, and certain DMs just not coming through at all or huge (hours) desync when testing on multiple identities. It's not the only relay I use for inbox/DMs which makes it more odd, but it's the only relay I have control over 😉 Current config: Running in docker container min_conn = 4 max_conn = 128 reject_future_seconds = 1800 Not limiting subscriptions currently Whitelisted to certain npubs as I'm testing broadcast_buffer = 16384 event_persist_buffer = 4096 limit_scrapers = true #AskNostr

How can an implementation of NIP-17 by different developers be so different to the end user? I understand it hasn't be widely implemented yet, but clients that have implemented it have issues. Genuinely curious. - #Amethyst and #0xchat seem to be the closest in similarity - They both communicate (mostly) fine between each other, and chats are created as they should. I think one thing in need of cleanup is that some messages on Amethyst are received as "template via 0xchat". - #Coracle almost works, but for some DMs it creates a completely separate group chat when viewed on 0xchat. Further, some DMs are sent unencrypted with no option for encryption (if this has anything to do with inbox relays I'm unsure how when NIP-17 messages can be sent in other clients to/from the same users). - Not sure what the deal with #Iris is. The Desktop app(hasn't been updated in a while) can only do groups, but these groups can't be joined by other clients. Web is missing this functionality entirely, including beta.iris. I'd love to onboard other people and suggest "use this on your phone, and this on desktop/web", but we can't communicate. Not sure if I'm missing something... Or if it's just too soon, even though what's there seems like it's supposed to work. #AskNostr

@Martti Malmi Can you explain the history on NIP-17 DMs in Iris? I understand there was a bounty for this which was claimed for its integration in Iris (according to

hrfbounties

Home - hrfbounties

The Human Rights Foundation is supporting open-source developers working to increase the usability and privacy of the Bitcoin and Lightning network...

but see no functionality reflecting that. Clearly missed those events, so what happened? 😃

"Nostr, interoperability baby!" "On Nostr, always reach your audience!" "We do direct messaging on Nostr... NIP-04 only!" "We do direct messaging on Nostr... NIP-17 only!" "We do direct messaging on Nostr.... NIP-59, non NIP-17 only!" I think this is ONE of the things that REALLY needs to be ironed out as soon as possible. 🚨 If an app has direct-messaging capabilities, it should do direct-messaging, period. If that means standardizing for the current-times what is the acceptable NIP, and/or phasing-out others, so be it, but do it. We still have clients that only support NIP-04 😬

NIP-46 should be THE standard by now. NIP-55 seems to further support it within the Android eco-system. If your client runs on Android or as a PWA, I shouldn't be giving your application direct access to my private key. I personally ONLY use Nostr clients that support remote signing with Amber and I imagine many users will follow suit when they realise how easy, seamless, but important it is. #Nostr #Android View article →

If you're like me, trying to #nostrize your protocols, you may have noticed #0xchat and #Amethyst can send each other encrypted DMs using newer NIPs, but almost no other client has implemented said NIPs in many months. Further, both of those apps are Android only. I've finally found a desktop client that can partake! #Gossip It's not flashy, but it's functional.

GitHub

GitHub - mikedilger/gossip: Gossip is a nostr client

Gossip is a nostr client. Contribute to mikedilger/gossip development by creating an account on GitHub.