nostrdev on Nostr: As I see it this will lead to a scenario where there are two classes of Nostr, one ...
As I see it this will lead to a scenario where there are two classes of Nostr, one with censorship enabled and the "free-speech clients".
Much like KYC BTC and non-KYC BTC, and eventually they will break compatibility.
This already happened to the Fediverse and it's why it failed.
Published at
2024-05-03 17:52:06Event JSON
{
"id": "f878026d02923e79ff2a423a8290725d905fbaf15d5bcc0dd0861d7deb8c3545",
"pubkey": "58b295a1a5f7b8e7d507777acbcbf7691a0b39c768da2695220a89a6da85ca67",
"created_at": 1714758726,
"kind": 1,
"tags": [
[
"e",
"792bdc3d8bd92b1440c909155f0f6d2b556f4559566847ec29b1baa7a87aa52e",
"",
"root"
],
[
"e",
"ceabc0d6a461e9689d3319252cbde5a43359361016ec0db2328b4f75544b4dc4",
"",
"reply"
],
[
"p",
"3c07d68edf71f6d22374dffae054e6801468594e7b0d0625fb5bcd24b202264d",
"",
"mention"
]
],
"content": "As I see it this will lead to a scenario where there are two classes of Nostr, one with censorship enabled and the \"free-speech clients\".\nMuch like KYC BTC and non-KYC BTC, and eventually they will break compatibility.\nThis already happened to the Fediverse and it's why it failed.",
"sig": "ea5aef074f1a999dc71f2bc2e79027906779a15366c8b11efc858ce458840a2d0cafe1040b3d742e517177bc5107b29dcbbdb0c7565cbda031a7763ba1848029"
}
