Shoulda done this so long ago.
STERRY
npub17dmm...tduz
Explorer and early adopter, painter, musician, coder, movie buff, bitcoiner, family man.
If you had to pick one NIP to preserve in posterity for all time what would it be? Supply a commit hash as well please.
There are two hard problems in computer science and yes I need to tackle naming this new Nostr-adjacent spec process. I have a domain that's premium and can definitely work, very rhymable, animal-based, and fun. In the end nothing's perfect and we don't decide what people call anything anyway.
For each BIP there's a champion who is responsible on the author side of things for driving the process. I wonder if that'd be good to include. Author seems like enough?
When I've stopped in I recall hearing web of trust was implemented in some relays. Will be neat to learn more about that.
Imagine short form videos that aren't all clickbait and instead teach people some PV goodness. One can dream...
One thing I'm surprised not to have seen yet is a short-form video app for Nostr that works based on dwell time. Apparently this technology of dwell-time and ML is what enabled ByteDance to grow so fast and after all that they don't have much of a most.
So to sum up, I'm creating a new spec process. On my phone now so not the best place to do any real work on it but figured it'd be good to put it out there.
A big next step is to stand-up the repo. Github is the natural place but it's never been more bigtech i.e. antithetical to decentralization.
I like Codeberg a lot since it's a non-profit with clear funding runway and based in Germany. Most contributors would need to register an account to get involved. Not sure if that's a good thing.
Apologies for the tweet storm but I just heard a rather inspiring talk about courage, compassion and kindness and it felt like the right time. Rather than hmm and ha about when to release this I figured it's better to just share and go from there.
Cool thing about JSON is that extra fields are often ignored so should be possible to implement many things in parallel and let the market decide what to support.
Another exciting area of work can be in compatibility as far as signaling not just which specs are supported but which versions and schemas. It's never been so possible to automate APIs and testing AND this is something that everyone feels users/devs/admins alike.
And again it's fun to propose things to open up possibility, but there'll be an encoding aspect that goes beyond JSON to MessagePack, CBOR or whatever to give bandwidth efficiency where it's desired.
Another thing I'm not sure about but have hopes for are DIDs. As a W3C spec I think it could make integration with many systems more straightforward. Also seems flexible with various forms of resolution supported.
Also going to try to have delegation in there from the start. I know it's controversial but why not try all the ways? Or at least document them in a place that's easy to read, compare and experiment.
One of the ideas I'm excited about is type schemas. In the spec garden there'll be a place to publish json schemas for every event type which will be versioned right along with the specs. I imagine this will make generating code so much easier.
It's kind of amazing to think of the millions/billions of things a living creature does every second to keep the machine going and I love the idea that so much could be happening in a system like Nostr without central control. Each spec is like another chemical pathway.
Sucks to see zaps on and off again. Money seems to be a front-and-center battleground for the establishment.
Today I was looking at governance and the need for facilitators. Facilitators basically run the program that is the spec process. Merging drafts after a sanity check, maybe helping generate IDs and ensure there are tracking and discussion issues. I can see some need for CI dev and maintaining shell or python scripts.