I would love to see all nostr clients implement something similar. A few lines of code allows us client creators to help further protect the users from footguns and malicious actors.
There could be a case made for filtering the regex out of kind 1 events to prevent this at a relay level too, but that's up to the relay operator and their own personal stance on data censorship.
#[0]
Ron Stoner
npub1qj…dz44v
2023-03-10 03:50:52 UTC
in reply to nevent1q…qpyj
Author Public Key
npub1qjtnsj6hks7pq7nh3pcyv2gpha5wp6zc8vew9qt9vd2rcpvhsjjqydz44vPublished at
2023-03-10 03:50:52 UTCEvent JSON
{
"id": "f085e9a690cd77a82689065162553703a9939a9b7a3ba1175a2025e9bff05115",
"pubkey": "0497384b57b43c107a778870462901bf68e0e8583b32e2816563543c059784a4",
"created_at": 1678420252,
"kind": 1,
"tags": [
[
"e",
"23f7b0b4d6d00da12c4649da6abd89aef06b30511820e7fd7f148db295e9266c"
],
[
"p",
"0497384b57b43c107a778870462901bf68e0e8583b32e2816563543c059784a4"
]
],
"content": "I would love to see all nostr clients implement something similar. A few lines of code allows us client creators to help further protect the users from footguns and malicious actors. \n\nThere could be a case made for filtering the regex out of kind 1 events to prevent this at a relay level too, but that's up to the relay operator and their own personal stance on data censorship. \n\n#[0]",
"sig": "dc386565216b333f327ae1aa135b3af7a7add72b02f8e0151b02170d917049f084e5f5707f8bc38c8ccfc178d3a35699919e43ec57a9d77a614238ce2a2ed8f7"
}