Yeah, but afaik nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt doesn't get them from a #nostr event (yet).
Am I right?
Discussion
Yeah, we should create a new event kind where relays can post an event to advertise that they are a relay for search. :) Then the client just need to get all the advertisements and list them on the screen.
If you do that, you can also make pinned notes that can be used as ads.
As long as the sender maintains the biggest zap to devs, the note will remain pinned to top of the feed. Can be checked every hour or every 24h, depending on the demand.
we should be able to get that with NIP-66 and the stuff nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx built:
nak req -k 30166 -t N=50 relay.nostr.watch -a 9bbbb845e5b6c831c29789900769843ab43bb5047abe697870cb50b6fc9bf923 should get it, but I see it's returning non-NIP-50 relays 🤔
kind:30166 with "#N": ["50"] should get that info 😀
Hmm, I just ran a test and more or less got what I expected. Here's the test result:
https://gist.github.com/dskvr/6036030fb5302e8a519e1d73d5f790c4
Can you provide replication instructions?
You're missing `since` btw.
Also don't you need to encapsulate `50` with double quotes in nak? `"50"` :D
has existed for almost two years.