Replying to Avatar Niel Liesmons

Great write up sir!

I think we can get the best of both on Nostr. Withe the **onNostr** being the important part.

The central repo on GitHub = :110percent: the issue. As soon as you take that of the picture and imagine a Nostr spec on Nostr, there's opportunity to introduce the best of what lexicons bring.

I'm personally leaning towards:

1️⃣ Wikis as the best way to publish specs

2️⃣ App Releases as a potentially more suited place to reference which specs your app is built on
Avatar
Garbage nsec 9mo ago

> 2️⃣ App Releases as a potentially more suited place to reference which specs your app is built on

Makes a lot of sense to me. Without that real-world context you can be forced into a kind of lowest-common-denominator-of-possibilities outlook.

Reply to this note

Please Login to reply.

Discussion

Avatar
Niel Liesmons 9mo ago

True story!

Will pitch the idea to nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 , but it's not priority now.

Step one = Getting the communities running where we can collab on these NIPs in the first place.

Avatar
Garbage nsec 9mo ago

For sure. If you get it up I'm happy to test sending join events with some throwaway nostr:npubs. This here web UI seems like it'd make testing pretty easy for a small test group.

https://nostrtool.com/