voyage : feat: add relay filter
https://github.com/dluvian/voyage/commit/dc4128dc63fdd843d85f5a176d29e74785b24c39
#[0]
#[0]
Pull request created for nostr-protocol/nips: #532
Add NIP-32 for labeling things in nostr
--------------------
Supersedes https://github.com/nostr-protocol/nips/pull/524
# Purpose
Content moderation involves labeling content. In https://github.com/nostr-protocol/nips/pull/459, @gruruya proposed expanding NIP-56 to encompass labeling. I chose to create a new NIP rather than update NIP 56 because backwards compatibility would have been difficult to maintain, and because the purpose of the NIPs are slightly different (see below).
In https://github.com/nostr-protocol/nips/pull/457, @s3x-jay and @rabble proposed a nomenclature and more comprehensive mechanism for content reporting/labeling. The consensus seems to be that a nomenclature is not a good idea, but there were some good ideas to include.
In https://github.com/nostr-protocol/nips/issues/522#issuecomment-1546286149 I realized that the same labeling mechanism could be used to leave reviews for relays, which I am eager to add to Coracle so people can start to find a better relay selection.
This PR may also render https://github.com/nostr-protocol/nips/pull/46 obsolete.
# Justification
Maybe this will seem like I'm trying to make a single NIP do too many things. But reviews, labels, and reports all have two things in common: they refer to an object, and are an expression of someone's opinion. In each case, there is a value judgment involved in assigning the label, involving both imprecision and uncertainty. Expressing this opinion using either a mark, or content, or both, allows either a machine or human to make a judgment call as needed.
One nice thing I'd also like to point out about this PR is it allows for associating any two entities (e/p/r/t) in nostr, and searching those associations. This gives us the beginning of graph-database-like functionality that can form the basis for both WoT and topical moderation and recommendations.
Confidence/quality may seem like the same thing, but they're two different axes along which to measure certainty. The first is subjective (the label author may not be 100% sure), the second objective (the label may not perfectly fit). This has been suggested in a few places, but was best executed by guide.newfounding.org (unfortunately their site is no longer available).
# Compatibility
This PR is similar to NIP-56, but is focused on distributed "moderation" (allowing users to filter notes based on their preferences) rather than centralized moderation implemented by relays and clients directly as required by law or app store policy.
# Implementation
None of this is implemented, but my main motivation of drafting this PR is so I can add relay ratings and reviews to Coracle soon.
#[0]
#[0]
Here is a list of relays I use and consider reliable so far. I've included some relevant information for each relay such as if payment is required or [NIP-33](https://nips.be/33) is supported. I'll be updating this list as I discover more good relays, which ones do you find reliable?
## Nokotaro
nostr:nrelay1qq0hwumn8ghj7mn0wd68yttjv4kxz7fwdehkkmm5v9ex7tnrdakj78zlgae
- Paid? **No**
- [NIP-33](https://nips.be/33) supported? **Yes**
- Operator: nostr:npub12ftld459xqw7s7fqnxstzu7r74l5yagxztwcwmaqj4d24jgpj2csee3mx0
## Nostr World
nostr:nrelay1qqvhwumn8ghj7mn0wd68ytthdaexcepwdqeh5tn2wqhsv5kg7j
- Paid? **Yes**
- [NIP-33](https://nips.be/33) supported? **Yes**
- Operator: nostr:npub1zpq2gsz25wsgun2e4gtks9p63j7fvyfd46weyjzp5tv6yys89zcsjdflcv
## Nos.lol
nostr:nrelay1qq88wumn8ghj7mn0wvhxcmmv9uvj5a67
- Paid? **No**
- [NIP-33](https://nips.be/33) supported? **No**
- Operator: nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c
## Nostr Wine
nostr:nrelay1qqghwumn8ghj7mn0wd68ytnhd9hx2tcw2qslz
- Paid? **Yes**
- [NIP-33](https://nips.be/33) supported? **No**
- Operators: nostr:npub1qlkwmzmrhzpuak7c2g9akvcrh7wzkd7zc7fpefw9najwpau662nqealf5y & nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz
## Nostrich Land
nostr:nrelay1qqvhwumn8ghj7un9d3shjtnwdaehgunfvd5zumrpdejqpdl8ln
- Paid? **Yes**
- [NIP-33](https://nips.be/33) supported? **No**
#[0]
#[0]
relays sao os servidores que enviam as mensagens do nostr. na sua maquina vc so tem um cliente que acessa uma lsita de relays q vc definir. https://nostr.com/relays
https://nostr.watch/relays/find aqui tem uma lista de relays, se conecte com varios. vc pode escolher de quais vc le, e em quais vc posta. Os relays conversam uns com os outros, mas se vc sabe em qual relay um usuario esta, é mais rapido pois nao precisa esperar os relays se acharem. essa é a ideia de uma rede distribuida.
#[0]
#[0]
I’ve been studying relays on Nostr, to understand how they work, how they store data, how they create decentralization.
This is an interesting concept that helps understand: https://relayable.org/.
They are public read relays, that choose who they allow write privileges. Thus, data is only backed up to their relays for users that they opt to allow in.
Anyone can create a relay so I’ll create my own private relay, for me to backup my data, while also remaining connected to other public relays.
I’ll share more as I learn.
#[0]
nostr:npub1tsgw6pncspg4d5u778hk63s3pls70evs4czfsmx0fzap9xwt203qtkhtk4 hi Dave , what is the most popular nostr relay?
#[0]
-> wss://nostr.easydns.ca
---------------------------------
name: nostr.easydns.ca
description: A nostr relay written in TypeScript.
pubkey: npub1elwpzsul8d9k4tgxqdjuzxp0wa94ysr4zu9xeudrcxe2h3sazqkq5mehan
contact: relays@easynostr.com
supported_nips: [1, 2, 4, 9, 11, 12, 15, 16, 20, 22, 26, 28, 33]
software: git+https://github.com/Cameri/nostream.git
version: 1.16.0
limitation: None
(nostr-relay-info-bot ver. 0.1)
history #nostr #relay
#[0]

