I agree with not rendering nip19 without the prefix.

Reply to this note

Please Login to reply.

Discussion

i further say that clients must add the nostr: prefix or deth

Before publishing, Jumble now automatically adds the `nostr:` prefix if it's missing.

Testing

nevent1qvzqqqqqqypzpqf9hyg76r55m03spzstujx0uhxsczc9jg70l7gh4elg0k5yqzyrqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qpqucsf94hwpa0t0qqqgj9cwqycavzhhejttxxyjg6jwpwqvzcjhs2qmmf8yx

What about render correctly posts with no nostr: prefix?

so, you want the client to have a whole logic for scanning for every nip-19 prefix instead of the prescribed proper protocol nostr:

the editor, ok, not the presentation, that is gonna slow it down

idk if you have used coracle on mobile but it's heinously slow at rendering

it's become very slow on web too, and the logical reason is that there is so much extra work being done for whatever reasons... Postell's Law apparently, which i think is silly

i don't think scanning for backticks to render plaintext has any great impact though, but scanning for every one of the nip-19 entities is at least like 6 scans for each post before it can be rendered to html

nip19 without the `nostr:` prefix will be displayed as plain text.

good. catch up client devs lol

editor should not expect the user to know nip-19