RE: NIPs, implementations and compatibility.

Specs are hard. They often are unclear and miss edge cases. It’s why the only Bitcoin consensus spec I trust is the Bitcoin core source code - no written documentation or alternative project.

Nostr is moving at such a pace, and development individuals and teams are all self-funded, and frankly keeping up with their own development roadmap is hard enough - let alone trying to keep up with the latest NIPs; either draft NIP input, awareness around proposals, and where the most difficultly lies.. supporting NIPs that break user-space and create a negative user experience and feedback.

Solutions.. not sure exactly. But here are some ideas.

1. A regular 7-14 day reoccurring NIPs updates and presenting via community open video call session.

2. Implement breaking changes in smaller isolated test/POC projects - and not directly into popular app beta builds.

3. Difficult to say.. but perhaps slow down. We have major fundamentals in Nostr that are not great today.. we scrape by. Building on rocky foundations is a future curse - much works pretty well too.

4. Understand that creating work for other devs who are already struggling to keep up, builds more stress and tension.

I have around 500 TODO comments across my Nostr projects… some easy and some hard. It’s not easy to keep up.