bitman on Nostr: I can see why this can be confusing for a user of a protocol that does hard forks ...
I can see why this can be confusing for a user of a protocol that does hard forks practically every year to stay relevant and somehow continues to fail.
Published at
2025-02-17 19:44:36Event JSON
{
"id": "8803e3de8a755bf7aabc62179ae3d88279db32a2b387b20aa46f667aaf14ea6e",
"pubkey": "314072c16fa9433e1374f62e5b02c8163946ed298a9cde3b1541513c29d19fff",
"created_at": 1739821476,
"kind": 1,
"tags": [
[
"e",
"037842353bc211e6a4d656ef49f0e20fd27c90fd746d30237388ec96c66390d3",
"ws://192.168.18.7:7777",
"root"
],
[
"e",
"9970d2335c793f0d04278b874ee75d7ddab6abb46ea8441e09f3e130e91f1388",
"wss://nostr-verified.wellorder.net",
"reply"
],
[
"p",
"232950265e7a6eeb1b9ff0b802096ce2f794020d91317ece290eaf06919b4065"
]
],
"content": "I can see why this can be confusing for a user of a protocol that does hard forks practically every year to stay relevant and somehow continues to fail. ",
"sig": "b3c34515ac25a080d646ece6d73f07d77f008f6e0a7a3e05a003c72b68e8e7eb791ca74741c59704732becf9e57a874331cf3f771a260cd2c657b376efb939d1"
}