Fair enough.

What I struggle with is that there is no good central place to check for e.g. other nostr relays or apps that are compatible with onion/Tor/standard XYZ.

Which is maybe good, given the distributed ethos of nostr.

A similar previous example, media format tracking (e.g. does app X play webm) was not deemed a good fit for nostrability.

Maybe I’ll link to your repo, and get yelled at by fiatjaf anyway.

Reply to this note

Please Login to reply.

Discussion

Lol, Fiatjaf can yell all he want 😂 If it fits somewhere, and it makes it easy for people to find TOR relays, I'd consider it, but I don't really see how moving it to nostrability helps much atm.

NIP-66 might help with relay discoverability (nostr equivalent of nostr.watch I guess?), idk.

nostr:nevent1qvzqqqqqqypzpem34u9stj8ftlxldl4n2qz5f5hmrnxns3uga86fpwe7u28ga4n0qytkummnw3ez66tyvgaz7tmrv93ksefdwfjkccteqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qqs07jq6dlaw3rchwewccvgyc6uqav2fnx7s8malsl27wmmsadnavuc97ae6m

💯 nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx has all the data on relays. Check out nostr.watch

NIP-66 is what does and has been the dataset behind nostr.watch for 12 years. It's implemented in many clients: snort, nostrudel, jumble, etc.

jfc, 2 years 😂

JOB REQUIREMENTS: 12 years of nostr dev 😂