Take the NINO quiz! Here's how flotilla fares:

- [ ] There's no NIP for your data format

- [ ] There's a NIP, but no one knows about it

- [ ] Your NIP imposes an incompatible/centralized/legacy web paradigm onto nostr

- [x] Your NIP relies on trusted third parties

- [ ] There's only one implementation of your NIP

- [ ] Your core value proposition doesn't depend on relays, events, or nostr identities

- [x] One or more relay urls are hard-coded into the source code

- [ ] Your app depends on a specific relay implementation to work

- [ ] You don't validate event signatures

- [ ] You don't publish events to relays you don't control

- [ ] You don't read events from relays you don't control

- [ ] You use legacy web services to solve problems, rather than nostr-native solutions

- [ ] You use nostr-native solutions, but you've hardcoded their pubkeys or URLs into your app

- [x] You don't use NIP 89 to discover clients and services

- [ ] You haven't published a NIP 89 listing for your app

- [ ] You don't leverage your users' web of trust for filtering out spam

- [ ] You don't respect your users' mute lists

- [ ] You try to "own" your users' data

That's a 3 on the NINO scale. The "trusted third parties" thing is debatable; in this case I'm counting relay operators, most of which are nip29 multi-tenant relays and relay.tools currently, but ideally that will improve as people run their own infrastructure.

How does your app fare?