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.
Mike Dilger /
npub1ac…9p35c
2025-01-30 23:38:28
in reply to nevent1q…9gpq
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2025-01-30 23:38:28Event JSON
{
"id": "646a35f811bd517ed7fb2a027f2ac8c05c8d08570240b5c4afa1caafc3cb4e46",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1738280308,
"kind": 1,
"tags": [
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"e",
"6571298684f4a073ded615154a04f8011a56a179a700837161e119e4c5a0d4d9",
"wss://nos.lol/",
"root",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
]
],
"content": "NINO quiz applied to the Gossip client\n\n- [ ] There's no NIP for your data format\n- [ ] There's a NIP, but no one knows about it\n- [ ] Your NIP imposes an incompatible/centralized/legacy web paradigm onto nostr\n- [ ] Your NIP relies on trusted third parties\n- [ ] There's only one implementation of your NIP\n- [ ] Your core value proposition doesn't depend on relays, events, or nostr identities\n- [x] One or more relay urls are hard-coded into the source code\n- [ ] Your app depends on a specific relay implementation to work\n- [ ] You don't validate event signatures\n- [ ] You don't publish events to relays you don't control\n- [ ] You don't read events from relays you don't control\n- [ ] You use legacy web services to solve problems, rather than nostr-native solutions\n- [ ] You use nostr-native solutions, but you've hardcoded their pubkeys or URLs into your app\n- [ ] You don't use NIP 89 to discover clients and services\n- [x] You haven't published a NIP 89 listing for your app\n- [ ] You don't leverage your users' web of trust for filtering out spam\n- [ ] You don't respect your users' mute lists\n- [ ] You try to \"own\" your users' data\n\nExplanations:\n\n * Gossip includes 20 relays to get people started. I tried to be as fair as possible\n in choosing these relays with an algorithm. Every major release I run the algorithm\n again and the top 20 go in.\n\n * For a few relays that require the Origin header, we send it. Those are hard coded.\n\n * Gossip doesn't publish a 31990 (NIP-89) because although gossip handles lots of event\n kinds, there is no way to specify how to launch a local application in such a way\n that other applications could do it automatically.\n",
"sig": "32ff8e7061968a1a4a73dc6e246bf96b24a6575216fc3c56618ef6e328cff9441c797c630784442acfbade8ad2f5b4a92596bf758a38722c7df044ab3846b592"
}