mister_monster on Nostr: So, suppose the p tags on *my* kind 3 could each have multiple relays like you said ...
So, suppose the p tags on *my* kind 3 could each have multiple relays like you said you tried for that I quite like. And suppose your kind 0 event had a list of relays that was updated by your client every time you added or removed a relay, just like if you changed your avatar or something. Could be kind 10002 as well, but I'm trying to simplify the protocol in my mind, rolling the contents of kind 10002 onto kind 0. If the relays in your p tag in my kind 3 were updated by my client when they don't match your kind 0 (or 10002), then we don't really have a rot problem or a bootstrapping problem, right? The likelihood that your followers' p tag for you in their kind 3 are out of date is very low, the likelihood that nobody can find your list of relays from just a couple of your followers' kind 3 events is extremely low, and if clients MUST update their kind 3 p tags from your 10002 or 0 in my hypothetical idea, then it looks like those two problems are practically solved, though I know not perfectly solved since there is a small chance that none of your followers have a single relay for you that you still broadcast to and therefore that will have an up to date kind 0 or 10002 event for you. To me this seems much more robust and less dirty than the brute force hack you just told me about.
Published at
2024-08-30 02:32:18Event JSON
{
"id": "1987331892b3129d859d3b6806804f13338b3a11e67716f01779f129c447ccb5",
"pubkey": "dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2",
"created_at": 1724985138,
"kind": 1,
"tags": [
[
"e",
"000060fd71eef355cf92cc70722baf7042b5c27482cb78339fe7b563bb9e871c",
"",
"root"
],
[
"e",
"3ff316d07fd4995c6cf7460a5510f567afcc23887d200c750d358d55c4e69829"
],
[
"e",
"e77606a0d68db685b8e972b3161b4897bdd86efaf99ba8016914d80b5c5ba7fb",
"",
"reply"
],
[
"p",
"dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"monero",
"83C7gGhRN5RdC21xKonJLpSW6rK2598MU8ho7C9fWu2UZuv127dXTygM81sH6tkBEHMua6pnaVGv15Fw1YHxu87uCQxeewP",
"1.0"
]
],
"content": "So, suppose the p tags on *my* kind 3 could each have multiple relays like you said you tried for that I quite like. And suppose your kind 0 event had a list of relays that was updated by your client every time you added or removed a relay, just like if you changed your avatar or something. Could be kind 10002 as well, but I'm trying to simplify the protocol in my mind, rolling the contents of kind 10002 onto kind 0. If the relays in your p tag in my kind 3 were updated by my client when they don't match your kind 0 (or 10002), then we don't really have a rot problem or a bootstrapping problem, right? The likelihood that your followers' p tag for you in their kind 3 are out of date is very low, the likelihood that nobody can find your list of relays from just a couple of your followers' kind 3 events is extremely low, and if clients MUST update their kind 3 p tags from your 10002 or 0 in my hypothetical idea, then it looks like those two problems are practically solved, though I know not perfectly solved since there is a small chance that none of your followers have a single relay for you that you still broadcast to and therefore that will have an up to date kind 0 or 10002 event for you. To me this seems much more robust and less dirty than the brute force hack you just told me about.",
"sig": "80dff79c1c5a883176a1111615d99164d351e3ec74bd1712ea4ca72d3d1693ca10dc17c7d8c404cd0b2787ecaefaa60d615b5cac02cf58e56d100e9e612680c7"
}
