nip-66 positive interoperability tracker

[alltheseas]

SPEC: https://github.com/nostr-protocol/nips/blob/master/66.md

NIP-66 optimized relays 1 2 3 4 nostrpul.se first-principles NIP-66 demo, draft7 nostr.watch relay directory, draft1 relay.tools relay hub/browser, draft7 @nostrwatch/nocapd monitor daemon, draft7 active monitors: NE BR USA-W USA-E AU IN KR ZA monitorlizard daemon, draft7 monitor nostr-event-deleter site draft7 Snort.social NIP-66 relay settings implementation Nadar deplyoment Nadar code (find which relays an event is stored on) Jumble.social

NIP-66 vs local network scan

Insights by @dskvr

Conclusion:

1. NIP-66 is faster (between 10-500x faster)
2. NIP-66 provides larger dataset of online relays
3. NIP-66 allows monitors to take their time for purposes of accuracy
4. NIP-66 alows for discovery of relays based on geographic location, nip compatibility, software used, requirements, topics, etc...
5. client-side testing is necessary for localized round-trip time accuracy, and can use NIP-66 to achieve these results much faster. The client can then run a client-side scan to try and fill any gaps left by NIP-66.
6. client-side testing requires no trust, and is ideal in cases where speed and complete datasets are not a requirement. It is extremely important for users to be able to run these tests locally in cases of widespread ISP fragmentation, nationalized firewalls and for purposes censorship resistance.

[alltheseas]

• NIP-66 optimized relays 1 2 3 4
• nostrpul.se first-principles NIP-66 demo, draft7
• nostr.watch relay directory, draft1
• relay.tools relay hub/browser, draft7
• @nostrwatch/nocapd monitor daemon, draft7 active monitors: NE BR USA-W USA-E AU IN KR ZA
• monitorlizard daemon, draft7 monitor
• nostr-event-deleter site draft7

source

[alltheseas]

example client side implementation via @v0l snort.social

[alltheseas]

@dskvr updated Nadar to utilize NIP-66

https://njump.me/nevent1qgswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsqgx6w5a2vfx4t3gf3mpaacuu8xxahm7ugs3flznmtayze4uesxctky6zfrcs

https://github.com/sandwichfarm/nadar

Updated NADAR to use NIP-66 and to also support naddr elsat fiatjaf

Maybe I will deploy it eventually, otherwise, go for it.

[alltheseas]

https://nadar.sandwich.farm/

[alltheseas]

https://njump.me/nevent1qqswknlafcszxlyxhc0w0r56dta9zeav0n0h789e26h8urdtnxpuufgvq6pwh

there are two relays fully dedicated to NIP66 data that I know of. They are: wss://monitorlizard.nostr1.com (me) and wss://relaypag.es (nostr watch)

The monitors concept is interesting too, as anyone can run a monitor. It's just a pubkey, that if a user wanted to, they can subscribe to a set of these monitors by pubkey as well.

Amethyst could spread these events around more if you want more decentralization, currently, I'm not sure where all you can find them besides these relays.

Anyway, just another nip66 post. Eventually someone will use it (jumble does!) because it's awesome and solves a lot of relay problems. (Like geo / feature discovery). In this case, you could use it for liveness check without having to connect to the relay at all.

[alltheseas]

https://github.com/hzrd149/nostrudel/pull/334