NIP-89 was that one last missing piece to make the experience of transitioning through multiple microapps cohesive. It provides two simple building blocks: a way for apps to "register" kind applications handlers (e.g. app X supports kind Y using such-and-such URL)

NIP-89 was that one last missing piece to make the experience of transitioning through multiple microapps cohesive. It provides two simple building blocks: a way for apps to "register" kind applications handlers (e.g. app X supports kind Y using such-and-such URL)

As these microapps enable all types of niche use cases while maintaining interoperability and leveraging discoverability and distribution through nostr, the use cases of nostr begin to blend in and the artificial use-case silos break down.

While I admire the effort, I think it’s a mistake to build a custom db for nostr. Scuttlebuttl went down that path repeatedly and it never worked out. The reason strfry works so well is that it was the quadrable database first, then a Nostr relay second. Also Doug Hoyte is somebody who’s worked on databases for a long time.

At every moment from the very first patch, our product is shippable. This is essential, because a large proportion of patches will be wrong (10-30%) and only by giving the product to users can we know which patches have become problems and themselves need solving.

We apply one measure of quality to patches, namely "can this be done any simpler while still solving the stated problem?" We can measure complexity in terms of concepts and models that the user has to learn or guess in order to use the patch. The fewer, the better. A perfect patch solves a problem with zero learning required by the user.

We take the simplest, most dramatic problem and we solve this with a minimal plausible solution, or "patch". Each patch solves exactly a genuine and agreed problem in a brutally minimal fashion.

I’ve heard of many writers who had found their niche, built families around that sole income source, and then the agencies that they built disappeared overnight. These weren’t low-effort content mills either, but technical writing requiring knowledge of finance and the law.

Nostr is the best censorship resistant, user-controlled application to write and interact with people across the web. You sign up for ONE public and private key, keep them at a place where you can remember your private and public key (your private key is basically your password and is hashed), and you use your public key everywhere, and apps and extensions "remember" them. Eveything is seamless, and you move from app to app, website from website within this ecosystem interacting with everyone. As long as you configure your suite of servers called "relays", you are all set to explore the world of Nostr with your public keys. How cool can it be?