yup itโs a good idea. Will come soon enough.
Discussion
Thatโs awesome.
๐ฅ๐ฅ๐ฅ
Wheres the code? Lol
https://github.com/damus-io/damus#contributing
Found it โค๏ธ
#[3] barbecue yesterday was lit. You really know how to cook a steak.
I think as long as the party receiving the DMs has it as an option it is fine.
i'd prefer the following if it was being done just for me....
1. Unknown parties must pay me 100 sats to DM me
2. Once I follow you back you pay me nothing to DM me
If it is to "prevent spam" vs. a way to be enriched as an influencer at the expense of followers, let's treat it like that.
Whenever someone asks me to join a telegram group, or something, I tell them to send me 3000Sats and Iโll join it.
Would love that!
We can offer some of these features on the relay side too if someone will implement NIP-42 for us https://github.com/damus-io/damus/issues/940
Hello, i think i have implement nip42 in my client since 1.1.0 version, but i haven't find the relay for test.
Can you give me a test relay address or you can test by yourself throw download from appstore.
wss://filter:nostr.wine without any additional paths will request an AUTH (though you need to be a paid user to pass, itโs enough for you to play with).
Kolliders pay relay also supports it.
#[7]โ has been silent for a while on #Nostr. Iโm starting to get worried ๐
I actually bought their relay and had to test it in the terminal and send a test note with nostril. Thatโs the current state of AUTH on nostr.
My Nostr POW Service was one of the first to implement it.. and itโs not specifically a relay ๐
Does nostr.wine has any auth msg callback?
Assuming you mean filter.nostr.wine, it will answer your AUTH event as in a spec with either an OK or a NOTICE.
But i can't receive any callback.
Works fine for me (random unpaid private key)โฆ

We wonโt respond to ANYTHING else unless you answer the AUTH. Otherwise the websocket is completely ignored.
This is one of the many things completely ignored in the NIP-42 spec is how to address the REQs that get sent before/simultaneous to an AUTH req being sent. The timing of the AUTH events isnโt defined either so clients have to be ready to answer them at all times (apparently).
