PABLOF7z on Nostr: I think this is far simpler: don't support grossly broken implementations or the ...
I think this is far simpler: don't support grossly broken implementations or the surface area for the protocol will be infinite.
I would much rather use a client that either ignores bad events or even better displays them with a nice warning saying "person X published a horrible event, click here to tell them to complain about their broken client" -- Ideally it would check if there's a `client` tag with a NIP-89 and p-tag the author of the client.
Published at
2024-10-20 19:51:52Event JSON
{
"id": "bcac5aac5cafd8c1a6f7948f90854d747b79ae77e5158265f186c99b27699e1f",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1729453912,
"kind": 1,
"tags": [
[
"e",
"23aec616664d37222a3b6c6ecfbae5d2f03799d5a9d8b2c49d8d871ddb16f30a",
"",
"root"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "I think this is far simpler: don't support grossly broken implementations or the surface area for the protocol will be infinite.\n\nI would much rather use a client that either ignores bad events or even better displays them with a nice warning saying \"person X published a horrible event, click here to tell them to complain about their broken client\" -- Ideally it would check if there's a `client` tag with a NIP-89 and p-tag the author of the client.",
"sig": "0b9a53fbc24be088183f3983a6bfcc9b3d2120b4fcb7cd855abbcbc51fb2dd74921dc1b565547596f34a89efa6f8a8a8cdfaf6cf2d895f92849b94ac957aa37c"
}