THAT is your beef with nostr? Among all the problems, you notice that kind could just be another tag and for that you want to start over?  That is trivial.

But on that topic, I think instead of a kind field there should be bitflags.  One or two bits meaning ephemeral/replaceable, one bit meaning restricted to tagged people, one bit meaning only uploadable by the author, etc.  And tag "keys" should be binary, a number not a letter. Events should be binary and don't need to be "read" by humans outside of using a note reader library (which can express them in nice english words) or in code (where they are expressed again as nice english words).  E se preferir português pode usar nomes portugueses na sua biblioteca em vez de inglês. 

 I was only half joking in case that wasn't clear. Bikeshedding over trivialities is what we do.

I agree with your latter point. The only thing better than enums is bitfield enums, so much more flexibility. The only issue is that would limit us to 64 different composable kinds, but we could just make new fields for other things. 

 Where is the punchline, cracker?
Heroin kills https://image.nostr.build/2969efc50b9061a5f16a37ddebd056bbab5fdc926a57117fd411ebb924bcada4.jpg