Don't ₿elieve the Hype, PhD 🦊 on Nostr: "I would never join a platform like Nostr if there's no way notes can be deleted" ...
"I would never join a platform like Nostr if there's no way notes can be deleted"
"Why is that?"
"Depending what kind of platform it wants to be, if you have content creators like on tiktok or Instagram and someone disagrees with what they say, on these platforms people go as far as finding out addresses and phone numbers and post them in the comments. Mods remove such things. If notes can't be deleted, such information stands there forever. It's dangerous and a no go"
Had a talk this morning following yesterday's discussions about safety on Nostr. This reply is hard to argue with. If you're a nym it doesn't concern you much. If you create "social media content" like videos or images and people even know or recognize you, they might do the worst things for the worst reasons and there currently is no way to prevent or stop that.
Thinking about this a lot today. It's a fine line between censorship resistance and people feeling safe to use the protocol in a way they see fit.
If we want to always have a couple of Bitcoin anons, ignore what I said. If we want mass adoption it's a topic we need to address.
Can it be addressed tho? Yes, but we would need to shift from absolute censorship resistance to something compromised. Maybe some community based reporting mechanism that relays comply with in terms of deleting said notes. We would still not have a central instance but the community guiding such things.
Should it be done? Up for discussion. Especially now that we have a main focus on the outbox model and blastr, it would make it way harder to implement something like that as notes get spread out on many relays that all would need to comply to some mechanism like that. Almost impossible if it's not a standard part of the protocol.
I know this is not a popular topic. I'm interested what people think about it tho.
Published at
2024-04-02 09:45:29 UTCEvent JSON
{
"id": "7930634e350e6ef6cb10b010d915a7432257e3e94757ad8db2b920a56744270b",
"pubkey": "99bb5591c9116600f845107d31f9b59e2f7c7e09a1ff802e84f1d43da557ca64",
"created_at": 1712051129,
"kind": 1,
"tags": [],
"content": "\"I would never join a platform like Nostr if there's no way notes can be deleted\"\n\n\"Why is that?\"\n\n\"Depending what kind of platform it wants to be, if you have content creators like on tiktok or Instagram and someone disagrees with what they say, on these platforms people go as far as finding out addresses and phone numbers and post them in the comments. Mods remove such things. If notes can't be deleted, such information stands there forever. It's dangerous and a no go\"\n\nHad a talk this morning following yesterday's discussions about safety on Nostr. This reply is hard to argue with. If you're a nym it doesn't concern you much. If you create \"social media content\" like videos or images and people even know or recognize you, they might do the worst things for the worst reasons and there currently is no way to prevent or stop that.\n\nThinking about this a lot today. It's a fine line between censorship resistance and people feeling safe to use the protocol in a way they see fit. \n\nIf we want to always have a couple of Bitcoin anons, ignore what I said. If we want mass adoption it's a topic we need to address.\n\nCan it be addressed tho? Yes, but we would need to shift from absolute censorship resistance to something compromised. Maybe some community based reporting mechanism that relays comply with in terms of deleting said notes. We would still not have a central instance but the community guiding such things. \n\nShould it be done? Up for discussion. Especially now that we have a main focus on the outbox model and blastr, it would make it way harder to implement something like that as notes get spread out on many relays that all would need to comply to some mechanism like that. Almost impossible if it's not a standard part of the protocol.\n\nI know this is not a popular topic. I'm interested what people think about it tho.\n",
"sig": "6cc4bd3196a03bf7824d124397a04e5c20db60492b94ae180bffbe5e97b10efbe7a0f16711754aa3ee671a02dca65add1fc0b1530869ee6ef9903484a1a8cc32"
}