Joe on Nostr: Ah yeah, a bit mushy worded. I mean I could react to your note (repost, quote-post, ...
Ah yeah, a bit mushy worded. I mean I could react to your note (repost, quote-post, straight-up reply) for the purpose of starting a conversation with my own gang about it, not wanting you to be notified. On X that doesn't work, since any user can see which posts of theirs have recently been reposted or quote posted by who, and of course everyone's notified of replies. I'd have to screenshot your post and then tag my gang in the post with the screenshot. On nostr, however, I can loop in my gang without having to screenshot, so they have the benefit of the original post and full context. To do that, when reacting I just use the relay or set of relays my gang/community uses, and which I know you're not subscribed to since these are niche relays just for us. (In both cases I accept that it's all public behind the scenes and you might find out somehow or other, but that's fine, as long as you're not notified in the normal way.). In other words I want to fork your post on purpose, not by accident. Call it awareness-forking. If my client sees me doing that and thinks "I better divulge those niche relays so the poster will know about them", and then they're declared in the signed event, and then you see that notification and jump in to our gang chat to ask why we're being so rude, then I'm not going to be happy about that, and I go back to screenshotting, which is a bummer, because this awareness-forking seemed like a cool nostr feature that legacy social media doesn't have. This all can be solved via client outbox settings, like the ability to mark certain relays as do not divulge, etc. For what it's worth I see this ability to fork posts as something with a lot of utility. It's cool that posts can go in different directions. (The goal of outbox is of course to prevent awareness forking by keeping the original poster aware.) But if it's agreed this is a feature and not a bug then it means clients need to get even smarter, and that's a struggle.
Published at
2024-11-23 17:45:26Event JSON
{
"id": "1639a49a6b08b6150decdae5ba0bb515a66486eab45812ef124927dcb4054f59",
"pubkey": "8ec44004cbe32b091c29d6c3274f481c13b8b6e4d7c9fc0b526d849277494e4d",
"created_at": 1732383926,
"kind": 1,
"tags": [
[
"e",
"51f08d27750373c8b99b3fbe695491e3d07ff92b0bb709bce67ec93c405019c8",
"",
"root"
],
[
"e",
"36eb478ac47db99c6556e9234e6f80cb0590eb7a83e9fb38b987999abcfcbdee",
"",
"reply"
],
[
"p",
"d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
],
[
"p",
"8ec44004cbe32b091c29d6c3274f481c13b8b6e4d7c9fc0b526d849277494e4d"
]
],
"content": "Ah yeah, a bit mushy worded. I mean I could react to your note (repost, quote-post, straight-up reply) for the purpose of starting a conversation with my own gang about it, not wanting you to be notified. On X that doesn't work, since any user can see which posts of theirs have recently been reposted or quote posted by who, and of course everyone's notified of replies. I'd have to screenshot your post and then tag my gang in the post with the screenshot. On nostr, however, I can loop in my gang without having to screenshot, so they have the benefit of the original post and full context. To do that, when reacting I just use the relay or set of relays my gang/community uses, and which I know you're not subscribed to since these are niche relays just for us. (In both cases I accept that it's all public behind the scenes and you might find out somehow or other, but that's fine, as long as you're not notified in the normal way.). In other words I want to fork your post on purpose, not by accident. Call it awareness-forking. If my client sees me doing that and thinks \"I better divulge those niche relays so the poster will know about them\", and then they're declared in the signed event, and then you see that notification and jump in to our gang chat to ask why we're being so rude, then I'm not going to be happy about that, and I go back to screenshotting, which is a bummer, because this awareness-forking seemed like a cool nostr feature that legacy social media doesn't have. This all can be solved via client outbox settings, like the ability to mark certain relays as do not divulge, etc. For what it's worth I see this ability to fork posts as something with a lot of utility. It's cool that posts can go in different directions. (The goal of outbox is of course to prevent awareness forking by keeping the original poster aware.) But if it's agreed this is a feature and not a bug then it means clients need to get even smarter, and that's a struggle.",
"sig": "1664e779fc6a80baf04679239215289469922badc942550a9472e5c525b58d6685f35443bd668fdc828b24dccac58a21e126b6960f0201c50d08499f3868173a"
}
