NINO quiz applied to the Gossip client

- [ ] 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

- [ ] 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

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

- [x] 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

Explanations:

* Gossip includes 20 relays to get people started. I tried to be as fair as possible

in choosing these relays with an algorithm. Every major release I run the algorithm

again and the top 20 go in.

* For a few relays that require the Origin header, we send it. Those are hard coded.

* Gossip doesn't publish a 31990 (NIP-89) because although gossip handles lots of event

kinds, there is no way to specify how to launch a local application in such a way

that other applications could do it automatically.