From a UX perspective @ is useful only if you fire a search and let the user type some characters to autocomplete, and this is not so feasible on a generic event (maybe you can cache and filter already visited contents that have a title).
So for the UI should be sufficient to parse the plain nevent/nprofile/naddr without any prefix, possibly requiring it to be between whitespace chars. As soon the user paste the string, replace it with a sensible preview to confirm that it's correct.
At source level `nostr:` is robust and coherent with the scheme of the Nostr protocol.
dtonon / daniele
npub100…8vwqk
2024-08-13 20:37:05
in reply to nevent1q…c3r9
Author Public Key
npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqkPublished at
2024-08-13 20:37:05Event JSON
{
"id": "02c9cf4b9560aa97c54cea7197130538f0c2f5fdcf06a630d96f00ce172f30da",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1723581425,
"kind": 1,
"tags": [
[
"e",
"98bb9a824ec6ca05f966b4ab835b72c2c1f823439d829ddd4c583c5148de6eda",
"",
"root"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
]
],
"content": "From a UX perspective @ is useful only if you fire a search and let the user type some characters to autocomplete, and this is not so feasible on a generic event (maybe you can cache and filter already visited contents that have a title).\nSo for the UI should be sufficient to parse the plain nevent/nprofile/naddr without any prefix, possibly requiring it to be between whitespace chars. As soon the user paste the string, replace it with a sensible preview to confirm that it's correct.\nAt source level `nostr:` is robust and coherent with the scheme of the Nostr protocol.",
"sig": "e4683a02d05e98935bdf2ae459f111cbbb669f2d0cc8fe817df5af8396bf778b00802c596a3b1c18ccbb94b972e575a7dfd61593c93868db4598452356bf44ba"
}