Nip42 (AUTH) #144
No reviewers
Labels
No Label
1000k
100k
10k
200k
20k
500k
50k
5k
75k
backend
blocked:design
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
scope:intl
scope:nip
scope:query_tracing
scope:ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/snort#144
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "nip42"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seems to work fine, tested with 2 different relay implementations,
nostr-rs-relay
andnostream
are the 2 most popular relay softwares, we should also make sure to test it on these before merginghttps://nip42.snort-social.pages.dev/
Closes #94
I tested it out a bit on my private relay, seems to be working well.
I noticed that it tries to AUTH against a server that is not marked to be read from, which I think it shouldn't do.
I noticed this because I thought my server had read settings set to true, but I only saw it AUTH successfully and not send any other REQ messages (or receive events).
https://github.com/v0l/snort/pull/145
Nostream doesn't seem to support NIP-42 according to README, neither does nostr-rs-relay. We should test with them when they release NIP-42 support, code lgtm.
we are not using result so can use
useEffect
The good thing about this is, it doesnt matter if the relay supports it or not, so we can merge this anyway it will only respond to AUTH if the relay asks for it
Deploying with Cloudflare Pages
a9ec933
View logs
🎉