"Hardened Events use event kind 30078 because previous interoperability back and forth isn't needed to pick the effective event kind" - quote from a draft NIP. The most grotesque side-effect of replaceable/addressables events shows up when you test a new bugged app and it wipes your follow list as soon as you add a new follow! Imagine if Facebook (in the good times) was on Nostr and you suddenly lose all your hand-picked FB follows due to a bug on another nostr app 😱 In an effort to fix this once and for all, I created a spec called "Hardened Events" that accidentally reverses the current school of thought from NIP repo maintainers of making atleast two clients interop before they (maybe - add politics to the soup) merge your NIP with these new event kinds you picked so that other people won't try using the same event kinds for other things. Now it's like: you pick a string as event kind prefixed with your app name or anything else. If someone wants to interop, they look at what events your client is producing and adopt'em. I kinda appreciate the outcome, it feels more organic. Though it's an (unintended) attack on Nostr. All new (effective) event kinds would use `kind 30078` as anchor. And to the despair of some, all newly created event kinds would be editable. Absolutely outrageous or ingenious? Not sure yet.