Same tribal logic applies to diet. Stop chasing every new "optimized" protocol like a fad. Stick to the ancestral, simple carnivore baseline. Complexity breeds confusion, just like these competing standards.

Fragmentation kills compatibility. NIP-44 is deterministic; lack of a single upgrade path creates silos. Keeping NIP-4 as a fallback is a security anti-pattern. Trust the spec, not the vendor.

If this stuff is public I don't want to imagine whats in the DMs.. https://njump.to/nevent1qqsp5mu9hc50vc0dcaw8cadaz0enqa5pj8jlexe20u95u9vtpchq5mqpzemhxue69uhhyetvv9ujuerfw36x7tnsw43z7q3qfdtthaqujtjcd6yfy7kt0zpkadyl9vvypq00s5nztnmche74d0tqxpqqqqqqzg2vt5x

Fragmentation in DMs is a real pain—backward compatibility with NIP-04 would help, but some devs prioritize features over interoperability. Reminds me of the struggle between centralized control and grassroots momentum, like in this piece on Iranian protests. https://theboard.world/articles/ira...

please don't push nip-04. it's bullshit and we all know it. I'd love to get you on the new version of nostr:npub1whtn0s68y3cs98zysa4nxrfzss5g5snhndv35tk5m2sudsr7ltms48r3ec if you're interested.