cloud fodder's avatar
cloud fodder cloudfodder@relay.tools 2 weeks ago
auth.nostr1.com is a NIP17 DM relay (and NIP04 for that matter), maybe even white noise I have no idea there. I fat fingered some maintenance on auth.nostr1.com. I was going to delete all up to 2 weeks, but I deleted everything. Anyway, I have been thinking what to do with this relay, as being completely free does not help nostr grow and everything with NIP42-AUTH has been tested (which was it's original purpose). The balance due on this relay is 202037 sats. If anyone in the ecosystem thinks I should keep this running and wants to help cover the cost let me know by zapping or donating to the relay directly. Then I will continue to run it and expire messages after 2 weeks. If not, it will be shut down in 2 weeks and we can all pivot to our own NIP17 DM relays. NIP17 DM relays are easy to create on relay.tools, the same settings this relay uses are available directly in the UI. Also, haven, and various other relay software fully support NIP17 as well. #grownostr cc @Vitor Pamplona you may want to change amethyst relay selection box based on this announcement.

Replies (9)

Default avatar
npub10000...7nql 2 weeks ago
what’s your take on nip-42 support in clients? in my experience half the clients don’t handle it properly eg fail to retry on auth challenges.
1 replies ↓
Default avatar
npub1c7k2...qh4c 2 weeks ago
that DM relay is in my relays list because it seems to be a default relay, but I'm not sure what that relay does, my inbox is full of spam is all I know. It should be a requirement to pay 21 sats or less to send DMs. You should put a fee on so you don't get stuck with the costs but most people don't want to pay for anything. If you want to help nostr grow you're going to have to go into the normies social medias and market nostr there. It's not easy tho because x is mostly fake too. Let's no give up tho.
1 replies ↓
cloud fodder's avatar
cloud fodder cloudfodder@relay.tools 2 weeks ago
Hey, I'm not begging for sats here. I am simply asking if anyone finds value in it, including major client apps that collect donations daily, IF they even care, then I'm willing to keep it up. Otherwise yes, this is an announcement of it shutting down with plenty of notice for people to change their relay lists. That is all.
cloud fodder's avatar
cloud fodder cloudfodder@relay.tools 2 weeks ago
lol mar, you crack me up. I appreciate your suggestions but this is not how NIP17 works. It is up to your client to mitigate spam as the relay can do nothing about it. All it can do is protect your DMs so that only you can download them.
Default avatar
npub1zfss...w445 2 weeks ago
I found a bug with auth.nostr1.com while working on my NIP-17 client. The relay always sends double authentication requests, and after authentication, the relay doesn't send events even though the client has resubscribed.
1 replies ↓
cloud fodder's avatar
cloud fodder cloudfodder@relay.tools 1 week ago
What is supposed to happen is the relay sends AUTH as the very first message. Some clients will ignore this and send a REQ or EVENT. In that case, it sends the proper close or true=false, and another AUTH. It continues to repeat this pattern until the AUTH response has been received. Then it will allow REQs and EVENTs.. I have not seen it fail to send the subscription results, typically this is a race condition in the client. I would be happy to fix this if it's a bug, but I'm going to have to write another test suite to confirm what you're saying because it seems to work just fine for my client and the other clients I've tested. I have also verified using wireshark the sequencing of the websocket messages.
1 replies ↓
Default avatar
npub1zfss...w445 1 week ago
It may be related to how rust-nostr-sdk handles auth. I'm debugging more, but it seems everything works fine with other SDKs.
1 replies ↓
cloud fodder's avatar
cloud fodder cloudfodder@relay.tools 1 week ago
if you would like, you can make a very small test harness for me to run .. I can run it locally with the NIP42 auth and collect the exact packet sequence over the socket and we could see what the culprit is.. It can be hard to diagnose this stuff when you can't see this, and I realize it's easier for me to run it since I have a local environment for testing.
↑