Mazin on Nostr: I think there are lots of reasons. Here are a few… - It’s complex to implement ...
I think there are lots of reasons. Here are a few…
- It’s complex to implement and requires a hardened ingester (sourcing notes from relays you didn’t select may be malicious)
- Performance and bandwidth penalties. Significant connection overhead increase.
- Clients who support NIP-65 often just copy kind 3 style 20 read/write relays in their list instead of the 2-4 the spec recommends
- Changes are still being made to NIP-65
Published at
2024-03-20 13:27:38Event JSON
{
"id": "b7bca0ef88f813fb24e434a35d5bef5453457c841554debd4b6b0040272b0b2e",
"pubkey": "3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d",
"created_at": 1710941258,
"kind": 1,
"tags": [
[
"e",
"5713539e51e11e7ad8309d0b5363292a0a68fc3f354d347d2f33917239538ad2"
],
[
"p",
"e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
],
[
"p",
"82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"
]
],
"content": "I think there are lots of reasons. Here are a few…\n\n- It’s complex to implement and requires a hardened ingester (sourcing notes from relays you didn’t select may be malicious)\n\n- Performance and bandwidth penalties. Significant connection overhead increase.\n\n- Clients who support NIP-65 often just copy kind 3 style 20 read/write relays in their list instead of the 2-4 the spec recommends\n\n- Changes are still being made to NIP-65",
"sig": "4276ccd1d4c8cb7ed0b8611b6226100e04e7026b0032bf2ec74a63b3f4101ced33946b5882cb50fb597942d56558664703de2eb02a93c18e7eeffaee899262fb"
}