joeruelle on Nostr: Is this a more serious risk if clients with traction stop writing events to outside ...
Is this a more serious risk if clients with traction stop writing events to outside (as opposed to reading events from outside)? I see that on the read side this introduces risks like seeing content that is out of date, or in the worst case purposefully altered.
Or is it that the read side alone comes with its own potential implications?
Published at
2025-01-15 00:39:58Event JSON
{
"id": "eaf3ea6019d47ce10347f95cc47e57381bd0647470d37bfd1a848229e4ce1aa8",
"pubkey": "b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823",
"created_at": 1736901598,
"kind": 1,
"tags": [
[
"e",
"108f5ff326c31ada8e70fddc17d8d47015e8d7b9273bd57c0389669ab8fd4b3e",
"wss://a.nos.lol",
"root"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
]
],
"content": "Is this a more serious risk if clients with traction stop writing events to outside (as opposed to reading events from outside)? I see that on the read side this introduces risks like seeing content that is out of date, or in the worst case purposefully altered. \n\nOr is it that the read side alone comes with its own potential implications? \n\n",
"sig": "61bb0211f2264c1e1580865488aad23131c94ff5c6e319cd2126fc022e77015b715abaf9257ff6fa0abca3f876ece51660cdcd0040f2f7ff963b7d63ba680ce1"
}
