You can just stick to the same plan.

Nostr feels like a spring of energy. Working now on PRs to go with the NIPs repo post because I want the vision to be complete for what it is and actionable on posting. It also helps when you do a final edit after all the pieces fit together. Ideally I can get this posted today but if not I'm sure I'll have learned enough to make the extra time worth it. GM, PV, and many thanks for following along.

That was fun. The reply is drafted but now have a small list of PRs to make which should help refine the draft. I want to put it all out there at the same time so everyone who sees the reply has the same picture. Again the purpose here is to point out a couple of the most fundamental problems with NIPs at the same time as offering solutions and labor to fix. Hopefully can work more on it tonight.

Hopes are high for Nostr. I'm working on a reply and PRs related to the discussion around NEPs, NIPs, and various external standards repos. I'm doing this because fixing problems at their root is best and we all have much to gain from improvements at the core of NIPs. I plan to seek consensus on how much can be done now and then volunteer as like a housekeeper to maintain on a daily basis.

There are certain things you're not going to write a Nostr-native app for. High performance, low latency, and large files for example. So how then can you build a catalog of apps that work and work the first time. It's important to have the debugging tools to iron out debug all the tricky bugs during integration.

In the end people don't care about protocol features. They want to achieve a goal. I want to chat with my friends. I want to share videos and memes. I want to kick back and see what's going on. From there it's about what apps exist and if one doesn't how easy is it to build a reliable one or improve on what exists.

A lot of Nostr's success comes down to making developers feel good. Packets are easy to read and it's never been simpler to create your experimental idea.

Developers tend to look at the packet format and network architecture when looking at a decentralized social network but these different protocols can be powerful in different ways. Devs can tell when a protocol is good design or accidental.

As I'm thinking about upgrades to Nostr I have to keep in mind that it's not about having the right answer. It's about getting the right answer.

What happens if we have a no op kind that says eventually we're not going to validate the wrapper? Instead we're going to validate this other scheme instead. In the beginning it's implemented the same inside as outside and eventually when some support flag reaches critical mass the second validation scheme goes into effect.

When everyone is going left, sometimes it's fun to go right. Being someone who digs into things that are taken for granted can also be really valuable.

When you work on stuff that matters it's much easier to make decisions. Trade-offs magically become less complicated.

If you've ever had a NIP left hanging or flat out denied get in touch!

Might be cool creating a relay plugin that translates into kinds to versioned strings maybe even pulling info from tags to do so.