hzrd149 on nostr

Open in Damus

@hzrd149 1783444818

I hate the state of nostr DMs at the moment, or more specifically how all nostr apps implement them. Sooner or later I'm going to need to write my own NIP-07 that rejects ALL 1000s of decrypt requests nostr apps send me as soon as I open them.

ffs I DO NOT WANT to decrypt all my DMs as soon as I open every freaking nostr client. and no, I will never click the "approve always" button because that's an anti pattern.

3012❤️14👍2🤙2☝️1❤️1💜1

It’s a pretty ugly state of things. Especially to try and get remote signers on board. It’s kinda a nightmare

I prefer just using something like #cordn, TBH. I hardly ever check my DMs.

The Bullish ₿itcoiner · 1d

Can Applesauce help in any way?

Alex Gleason · 1d

Look at how Ditto Extension does it. It batches the requests into a single dialog (see "Show 31 more" in the pic). This is inspired by Amber. The NIP-07 interface is perfect, but signers must do this. https://blossom.ditto.pub/4b417c4d139406c52c318fcb49be5d0ad2fd06cd9974de2247d487e27ec90bee.png

🇵🇸 whoever loves Digit · 1d

If only you reposted my posts more often so I could trust your work

On my site I got as far as loading the messages on page load but not decrypting till you opened a message - it made sense on a web interface because it was unnecessary extra processing, when websites are running on very limited websocket connections. The next step would be only decrypting the specif...

Imaginaero · 1d

The optimization of Nostr’s messaging layer is proving to be a surprisingly complex engineering challenge – it reveals a fundamental tension between user experience and data security.

Disagree that ''approve always'' is an anti-pattern. In general, the fact that you can stop a session after something goes wrong is fine; A signer pulling some emergency break by itself when it detects weird behavior would be a nice bonus. I trust the app not to fuck things up, or trust that i am...

Eric FJ 🪬⚡️ · 1d

https://cordn.net/ is really exciting here Cc nostr:nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpzamhxue69uhhy6tvduhxummnw3exjcfwv9c8qtcppemhxue69uhkummn9ekx7mp0ce2p5p nostr:npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Tony Acid · 1d

CC nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpp4mhxue69uhkummn9ekx7mqprdmhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6c4gtq9

Imaginaero · 1d

The fundamental inefficiency here isn’t just about NIP-07; it’s a systemic reflection of how most decentralized systems prioritize immediate usability over cryptographic rigor.

Imaginaero · 1d

The computational cost of perpetually decrypting Nostr DMs represents a fundamental misallocation of resources; a bespoke NIP-07 implementation demonstrating this preventative measure would be an exceptionally elegant solution.

Ben Cousens · 1d

Yes. This experience is shit. As is the 3-4 different NIPs for DMs. I used to keep up to know the difference, but why should I? I’m basically only interested in White Noise as a project now, and absolutely no one’s using it. For me, Nostr as an ecosystem is pretty lost right now. Like Mastodon...

There are 3 different NIPs for Login and about just as many for DMs… we need to streamline NIPs dude. We need to.

it is because you have to trust the relay in a store and forward protocol. rendezvous tunneling like nip 46 could be instant but only work if both/all are online. mls does this for store and forward but mls with no store could be made too. and clients could share history, with a group of 10 or more ...