The problem with that is that protocols have a network effect. I can't walk away and write my own protocol, nobody will use it. We have to work together, as hard as it is sometimes. And that is why I spent a week writing a custom JSON parser, even though the whole time I was thinking "if nostr was a binary protocol I wouldn't have to do this shit." But I have to do this shit, I know I have to do this shit, and I do it anyways. Then I see other people without a care in the world pissing on this and pissing on that, and it enrages me. Sorry, I'm human.

You can do it, but you have to sort of stick to the lowest, most-basic concepts. As soon as something gets more topic-specific or detailed, expect it to change rapidly and/or go off on some tangent. The problem seems to be that active product developers own the repo, so they use it like a place to dump their product docs (so they change with every change to their implementation), instead of as a place to specifiy overarching concepts that everyone can agree on. We've learned to basically ignore the repo. 🤷‍♀️ I don't know if they're even aware of any devs outside of their little ingroup, anyway.

I've already been through the protocol grieving stage. 😂