If you expect nostr app A to interact seamlessly with nostr apps B, C… and Z, which NIPs are “required” in your view? Which are not? Which are nice to have?
Discussion
I’m not sure this is “answerable”… in general. Might be client specific. Different NIP needs for different use cases.
Aaaand given that Nostr has the potential of obliterating “typical” app definitions (due to its being an open protocol for interoperability) … even saying “app A is a microblogging client, what NIPs are critical to interoperate with app B?” might not be so useful in the near future.
IMHO: App use cases will blur the lines, and each app will depend on its own collection of NIPs as “essential” to its operating in the Nostr ecosphere. And … if nips don’t exist for new use cases (or are not written to specifically serve them) … then developers will author new ones “on the spot”. Nostr will become (already is?) a wonderful shit show of “decentralized interoperability”.
“Essential NIPs” (and NIP understanding in general) is a rabbit hole with no end…. But kinda important questions to ask also…
nostr:note1seckzhrntq3zlmpfqcl8atwu7ptjq4k4zs74a9lpd6mm3w046alqa96urt