Oddbean

yeah, that's why I didn't go with "NIP", because some nips are quite broad, e.g. if you say you support nip-51, what does that mean? *all* the kinds nip-51 defines? instead a simple "mute list" feature flag would be more precise the main problem with this idea would be standardizing around names, e.g. "mute list" vs "mute-list", but we can easily normalize this like we did for the wiki nip. and ultimately developers can take a very simple quick look to see how other developers spelled "mute list"

@PABLOF7z I still think this will be useful. Lmk how I can help. We can use nostrability repo if you like. Thinking about this through the day, self-signed attestations are still in the “trust me, bro” universe. Useful, necessary, and insufficient. I foresee compatibility issues due to differing implementations of the same functionality. Ideally instead of self-attestations in nostr we have an automated scorecard of how nostr app A interacts with a pre-defined rubric of “correct” or more likely “acceptable” and “non-acceptable” behavior (“ erify, don’t trust”). I coined this #nostrCI and hopefully @santos and team will have the BBB workshop talk ready soon for me to share with yall. To assuage doubts I am not in crazy land at least three CI/devops bros have either chatted with me about this, or independently come to an understanding of the nostrCI problem, and thought about solutions. cc @sandwich @nourspace @miketwenty1 https://image.nostr.build/a4bb3cd57aa10742fc23a47317b682f07c35b6a1dbbd6f4465eefa34c58cfb2e.png