Fiatjaf/nostr – a censorship-resistant alternative to Twitter

Re:Fiatjaf/nostr – a censorship-resistant alternative to Twi... by vidarh on Friday December 31, 2021 @12:49PM (#29750476)

That's only true if you choose to introduce a global namespace. There's nothing requiring you to have just a single such catalog of users as long as the canonical reference is the pubkey any more than the contact list on my phone requires you to name people the same on your phone.

(and in fact on reading the protocol specs, they do have a way for relays to publish mappings [1] . EDIT: and that would seem to make it possible for crawlers to crawl relays to assemble non-canonical catalogs fairly easily).

There are downsides to having multiple namespaces, such as e.g. that there's no guarantee that your client will be able to map a given pubkey back to a human-readable name and/or dealing with collisions between mappings from different sources, of course, but this is reasonably well thread ground.

[1] https://github.com/fiatjaf/nostr/blob/master/nips/02.md

[ Parent | on HN ]

Re:Fiatjaf/nostr – a censorship-resistant alternative to Twi... by webmaven on Friday December 31, 2021 @07:49PM (#29754226)

Sure, you can have multiple namespaces, and each would have to be censored, but that's about as difficult as playing whack-a-mole with multiple domains pointed at an IP address.

[ Parent | on HN ]

Re:Fiatjaf/nostr – a censorship-resistant alternative to Twi... by vidarh on Friday December 31, 2021 @09:30PM (#29754853)

If you can censor the catalogs you can censor the relays. Not least because the protocols allows the relays to serve up catalogs of name to pubkey mappings. Having this lookup functionality makes no difference at all to the ability to censor. If you have an issue with the censorship resistance of this you have an issue with the core concept of this project.

That's fine. But it's entirely independent of whether or not you provide a lookup mechanism for names.

[ Parent | on HN ]