pull down to refresh
151 sats \ 6 replies \ @orthzar 27 Jul 2022 \ on: Daily discussion thread
I started writing a Nostr client in Common Lisp a few days ago. Nothing to link yet, since the code is unusable at the moment.
Months ago, I had started designing a protocol to replace email. But I realized I could build it on Nostr and skip a few steps.
Nice! Are you going to be using NIP-04?
reply
Very likely, though pubkeys would not be re-used (for spam resistance reasons). I'm still reading through the Nostr NIPs, so I'm not sure how to go about this just yet.
reply
If you'd like to expand I'm curious, how could pubkey reuse encourage spam?
reply
Re-use of pubkeys is similar to re-use of email addresses. We re-use email addresses for years, which makes spamming as easy as buying a list of addresses. But if nobody re-used email addresses -- instead changing their address after every message -- then lists of addresses would be pointless, because the lists would be out of date very quickly.
As best as I can tell, Nostr pubkeys are similar to addresses. But Nostr doesn't impose the restriction that email does: Nostr relays don't hand out one pubkey/address per user. Rather, Nostr clients can make as many pubkeys as they like. The trick is to coordinate change-of-address between clients (which is beyond the scope of this topic).
You mention the PoW NIP in a follow up post. PoW is appropriate when you're re-using addresses/pubkeys. I might be able use PoW for first-contact addresses. I'll have to think about that some more.
reply
Oh this is interesting: Proof of Work https://github.com/nostr-protocol/nips/blob/master/13.md
reply
I hope Nostr takes off. Discord is kinda bad. Or hopefully Nostr foces discord to open source their stuff and allow alternative clients because there is only one desktop client and its developed by discord and some pretty basic features are not being implemented for years. So all power to you and Nostr imo.
reply