Pablo won me over with that argument in the format discussion, if every special kind has a sensible fallback "content" it helps usability a lot.

Well, a zap event, for example, has either empty content or a random comment as the content. That will make no sense for a client that doesn't understand zaps.

Do you think going forward new event definitions should reserve the content field for a fallback self-descriptive string?