Good, this is why we worked on the recipe kind (comming soon).
Also, if this new 240 chars tweet kind has edits, will that make you drop edit and markdown support for kind 1?
I am becoming an "opinionated event kind" maxi. Nostr kinds could be designed for specific user experiences instead of general types. Like the picture kind Olas uses. Right now it accepts multiple image sizes but we could have one kind that only takes squared images for those clients to use.
It's similar to nostr:nprofile1qy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsr4ma0r 's pitch of kind 1s with a 240 chars limit. We could copy kind 1 into a new kind whose expectation is to render only the first 240 chars of content and ignore all the rest. We could have Nostr clients that only render (and make the best UI for) those events.
Discussion
I am never gonna drop support for edits. It's just waaaaay too used right now to remove it.
Markdown and ASCIIDoc will be enabled for all kinds on Amethyst. If users are writing on that format, we will always render it.