I just added such an event-definition file to my uploader, so that users can expand the optional tags used, and it's like...
Hold up. Why don't I have this everywhere?
Why do y'all hardcode every event type? An event is literally just a json data structure and yaml is the human-readable version...
It's hardcoded because not every client wants to support every type of event. If your new kind is actually compatible with the already supported kinds than opening a PR for it should be trivial.
I don't care, if it's trivial. If something has to be done over and over, and PRs are constantly trickling in to "add another event" or "add another tag to an event", and people are whining on Nostr that they STILL CAN'T SEE THE EVENT, HOW ANNOYING, then it makes sense to develop a feature where it can be done by a user directly. Especially as new kinds are popping up all over, now.
I also don't care if they implement that feature, by the way. Not all clients will make it and not all clients have power users who would utilize such a feature.
Just wanted to point out that it is a feature. And that I invented it. 😎
>An event is literally just a json data structure and yaml is the human-readable version...
Which is how I recently added yaml to my original json apps. Just convert yaml over to json (with a little coaxing because yaml only worth with strings)
