Also if you see a specification being broadcasted on a relay you can expect there's a chance that it is being used on those relays. Could reinforce territorial dynamics though. But beyond that, a registry can stand as endorsement of the content, and endorsements of the specifications it links to. Other users endorsing that article can gauge the level of concensus for specifications. Rather than a specified length, it will decay for less known/used nips, Then there is Vitor's demo of running a webserver from nostr events. How can you determine the trustworthy events on a relay where anyone can send events? You can read a registry from a trusted user (at this point, i mean actual trust, not computational WOT stuff) and that can act as a dns server to other nostr events. If we were to computationally do it, we'd need a strong metric that cant be gamable. Otherwise I'd see how that'd be a big safety hazard.
liminal ๐Ÿฆ 's avatar liminal ๐Ÿฆ 
@Vitor Pamplona, would I be correct that a registry could help this project? What about that dns alternative you've mentioned? https://github.com/vitorpamplona/nostr-web-server View quoted note โ†’
View quoted note →

Replies (6)

I love the scaling dynamics. Keeping versions is optional for you, you can keep however many versions you want for your data needs. Though, if your ideas/specs/product are popular, they'd be cloned to keep a backup of. The trust dynamic would work that if one of your endorsements ever become malicious, you are incentivized to remove them asap. Or move to another list - known malicious users.
Think we need to work on the ux for "nostr registries" - public documents from an npub you trust showing you the npubs, relays and clients they trust/endorse. View quoted note โ†’
liminal ๐Ÿฆ 's avatar liminal ๐Ÿฆ 
*cough cough* nostr registries *cough cough* @Laeserin ๐Ÿ‡ป๐Ÿ‡ฆ *cough* *cough* first as an answer to centralized nips repository. Next as an answer to trusted relay operators and developers. Close will be our answer to DNS. Thoughts @Vitor Pamplona? https://wikifreedia.xyz/nip-event-register/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl
View quoted note →
Ux needs work, but i think we can fix this with "nostr register" or just wiki entries with endorsments of clients or npubs
liminal ๐Ÿฆ 's avatar liminal ๐Ÿฆ 
Also if you see a specification being broadcasted on a relay you can expect there's a chance that it is being used on those relays. Could reinforce territorial dynamics though. But beyond that, a registry can stand as endorsement of the content, and endorsements of the specifications it links to. Other users endorsing that article can gauge the level of concensus for specifications. Rather than a specified length, it will decay for less known/used nips, Then there is Vitor's demo of running a webserver from nostr events. How can you determine the trustworthy events on a relay where anyone can send events? You can read a registry from a trusted user (at this point, i mean actual trust, not computational WOT stuff) and that can act as a dns server to other nostr events. If we were to computationally do it, we'd need a strong metric that cant be gamable. Otherwise I'd see how that'd be a big safety hazard. View quoted note โ†’
View quoted note →
โ†‘