diff options
| author | Ricardo Arturo Cabral Mejía <me@ricardocabral.io> | 2022-08-17 23:43:14 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-17 23:43:14 -0400 |
| commit | 8a94cc2f9889b725edd14d2311cf6c686e9460a1 (patch) | |
| tree | fa5142c39606e6a6df04867f9de8bde9bc2619fd | |
| parent | 072783319dd969efe5c5d47a44a499ec66afd449 (diff) | |
feat: add uses cases for nip-27
| -rw-r--r-- | 27.md | 16 |
1 files changed, 16 insertions, 0 deletions
| @@ -66,3 +66,19 @@ up to date. Both would construct the following message to subscribe: | |||
| 66 | } | 66 | } |
| 67 | ] | 67 | ] |
| 68 | ``` | 68 | ``` |
| 69 | |||
| 70 | # Use Cases | ||
| 71 | |||
| 72 | 1. Subreddit/IRC-like channels (e.g. `{ "#m": ["#newbies", "r/nostr", "#mp3s", "r/oldschoolcool"] }`) over Nostr. | ||
| 73 | 1. Forums over Nostr. (e.g. `{ "#m": ["itguys.com/IT/Support/Hardware", "itguys.com/General/Announcements", "itguys.com/General/New Users", "itguys.com/Social/Memes"] }`) | ||
| 74 | 1. Clients wishing to filter out all the noise from public events may choose to only subscribe to multicast groups. Apps/games/bots leveraging Nostr may prefer communicating over a multicast group to avoid collision with the broader public. | ||
| 75 | 1. A hard-to-guess multicast group can be used for increased (but not total) privacy over a trusted relay. A "channel-hopping" algorithm shared by clients may improve privacy in this scenario where a channel is a multicast group. | ||
| 76 | 1. Two or more parties may initiate contact publicly using Direct Messaging and agree privately on a hard-to-guess multicast group before continuing their exchange hiding further metadata from being leaked to the public. Parties can re-negotiate a new hard-to-guess multicast group at any point. | ||
| 77 | 1. Live events can take advantage of ephemeral events and previously-shared multicast group for communication during the event. | ||
| 78 | 1. Smart contracts may communicate in privacy-preserving way with individual clients using unique short-lived multicast groups. | ||
| 79 | 1. Clients interested in Bitcoin prices in USD may subscribe to the multicast group "prices:btc:usd". Many providers may publish their events to the same multicast groups. | ||
| 80 | |||
| 81 | # Notes | ||
| 82 | |||
| 83 | 1. Events sent to multicast groups should be considered public, after all they are readable by relays and can also be reshared by any client subscribed to the multicast group. | ||
| 84 | 1. Multicast groups are not a replacement for encrypted direct messages but can work in conjunction. | ||