What did you end up doing here?
I’ve found more success in asking it to generate code samples of patterns or frameworks I don’t understand and using that as an accelerator for teaching.
Agreed that having it generate boilerplate or known patterns is just less useful. At least you can just send the PR out and have #[2] review it instead for bugs! Less work for you!
This or we need to see broader use or the etag recommended relay. Right now we have neither.
https://github.com/nostr-protocol/nips/issues/354
Picking JSON serialization rather than a well specified binary serialization was a terrible idea. Satoshi got this right; nostr did not.
More issues like this will start to come out as adoption increases, but the sooner the better to start documenting the flaws.
#[0]
Going to be a big week
https://www.walletofsatoshi.com/disclosure
See section 5 for specifics
Lots of subtle taxes going from startup teams to companies with 500+ engineers (and public shareholders) like CashApp. Even more when going from 10s of thousands of active users to tens of millions. The amount of parallel development, business unit interop, and "stakeholder alignment" takes the wind out of plenty of features that should be straightforward to ship. The flip side is that everything that does ship gets immediate access to 10s of millions of people leading to a ton of leverage. I'm still very optimistic about the velocity of Nostr clients in the short term, but I suspect we will start to uncover more pain as the number of NIPs increase and the feature set between servers and clients becomes wider. Luckily, the FOSS community has a lot of preexisting knowledge on how to do this at scale so the tools exist and we get to see how they work. Not many other industries where the process is so transparent so don't forget to bring popcorn.