The OS will try to open something? No, the app will parse that much more easily and display the quoted event, or turn it into a link of its choice. There are literally no downsides. It's super easy for the client that is publishing the event to automatically prefix quotes with a `nostr:`.
But if the normal thing is to expect all clients to parse all nevent strings for all events ever that is unnecessary overhead that literally overheats the planet much more than necessary.
What is next? Expecting clients to also go through all of the events' contents multiple times with a huge list of TLDs or an infinitely slow regex to try to find URLs because publisher apps can't be bothered to prefix URLs with `https://`?
fiatjaf /
npub180…jh6w6
2025-05-16 14:25:17
in reply to nevent1q…txxd
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2025-05-16 14:25:17Event JSON
{
"id": "3944639e9ec75d1fe3d61ad2c0c964d7b2edbe17718b0f511ca070befa122e76",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1747405517,
"kind": 1,
"tags": [
[
"e",
"82da8f332b8b238afa6d45bd4f8a8acb5d95a43543db3a41ab1c33c4db834a05",
"",
"root",
"619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23"
],
[
"e",
"cd65a8316f50ea201da5f6bdc2994b880f57ba50b31b754d3f3820306289d05f",
"wss://relay.damus.io/",
"reply",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"
],
[
"p",
"619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23"
],
[
"p",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"
]
],
"content": "The OS will try to open something? No, the app will parse that much more easily and display the quoted event, or turn it into a link of its choice. There are literally no downsides. It's super easy for the client that is publishing the event to automatically prefix quotes with a `nostr:`.\n\nBut if the normal thing is to expect all clients to parse all nevent strings for all events ever that is unnecessary overhead that literally overheats the planet much more than necessary.\n\nWhat is next? Expecting clients to also go through all of the events' contents multiple times with a huge list of TLDs or an infinitely slow regex to try to find URLs because publisher apps can't be bothered to prefix URLs with `https://`?",
"sig": "b1806aca00baea626c767b07a6c12308a3d27e0ec96efe1a9258e55d03afbe6b53ae659f409247521df235bc113aa8945d677d342e23072d76bfedeb252ab0f0"
}