It adds an immense amount of complexity that is better left for more specialized applications and use cases.
At least for now, kind1 is the common ground everybody has and it should remain that for the foreseeable future, at the basic level it's super easy to get started, easy to read, easy to write, easy to display.
If you start publishing kind1 notes with HTML, Markdown, editing capabilities or kind1 notes that depend on custom interpretation of new tags or requiring fetching or other notes for them to be rendered correctly you're breaking that.
nostr:nevent1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qghwaehxw309ashgmrpwvhxummnw3ezumrpdejz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qythwumn8ghj7un9d3shjtnwdaehgu3wd9hxvme0qydhwumn8ghj7un9d3shjtn0wfskuem9wp5kcmpwv3jhvtcpr4mhxue69uhkummnw3ez6un9d3shjtnhd3m8xtnnwpskxef0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxrhwden5te0wfjkccte9e3h2unjv4h8gtnx095j7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqqf4gx2x2gd639jgwqccvgm4p7vlwrfh9t8yej68e2tpa03ay55nq9rygsw
So, go back to my original proposal to have a separate kind that can be edited that everybody hated back then?
Please Login to reply.
That's also bad.
So, don't do this, don't do that. What can I do? Either way, Edits are happening.
I gave my opinion, what else do you want?
Some would implement that kind, others wouldn't.
That's not normally a bad thing. It's part of how Nostr is meant to work. But it's bad in this case because those events would serve the same purpose as kind1 events most of the time, for most users, in most circumstances.
