Observation: if I reduce my concurrent relays limit, Coracle is often unable to find a lot of note context, because relay.damus.io (the most popular relay) is searched less frequently.
This would be ok because of NIP 65, but Damus (the most popular client) doesn't provide relay hints, so Coracle doesn't know where to look for the requested information.
Question: Does this make nostr effectively centralized around Damus?
jb55 (nprofile…j99z)
hodlbod /
npub1jl…jynqn
2023-08-07 17:53:19
Author Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnPublished at
2023-08-07 17:53:19Event JSON
{
"id": "159d2bcd7c2998ddb9de8e6764d62fc61f1ab647fe72d53e661f796f3e306230",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1691430799,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"wss://nos.lol",
"Will"
],
[
"client",
"coracle"
]
],
"content": "Observation: if I reduce my concurrent relays limit, Coracle is often unable to find a lot of note context, because relay.damus.io (the most popular relay) is searched less frequently.\n\nThis would be ok because of NIP 65, but Damus (the most popular client) doesn't provide relay hints, so Coracle doesn't know where to look for the requested information.\n\nQuestion: Does this make nostr effectively centralized around Damus?\n\nnostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegwcj99z",
"sig": "19c275c4abf5b6b90fae13afd5030d2359d80d173885f8346520af88515146982cd4baf52fa2e7a3aa46b785cc5f707526c8c8fac862255a3eeda049ae9ca22c"
}