diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-02-23 18:25:55 -0300 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-03-01 10:03:25 -0300 |
| commit | c4949ea7078ec96a373f77f725267b36316ee9e4 (patch) | |
| tree | 57d0c52e1845547afcf0fc1c8f47079710c7dc30 /78.md | |
| parent | b549a9809f94ca703b3b63b73cdacc5407a2edd0 (diff) | |
NIP-78: app-specific data.
Diffstat (limited to '78.md')
| -rw-r--r-- | 78.md | 21 |
1 files changed, 21 insertions, 0 deletions
| @@ -0,0 +1,21 @@ | |||
| 1 | NIP-78 | ||
| 2 | ====== | ||
| 3 | |||
| 4 | Arbitrary custom app data | ||
| 5 | ------------------------- | ||
| 6 | |||
| 7 | `draft` `optional` `author:sandwich` `author:fiatjaf` | ||
| 8 | |||
| 9 | The goal of this NIP is to enable [remoteStorage](https://remotestorage.io/)-like capabilities for custom applications that do not care about interoperability. | ||
| 10 | |||
| 11 | Even though interoperability is great, some apps do not want or do not need interoperability, and it that wouldn't make sense for them. Yet Nostr can still serve as a generalized data storage for these apps in a "bring your own database" way, for example: a user would open an app and somehow input their preferred relay for storage, which would then enable these apps to store application-specific data there. | ||
| 12 | |||
| 13 | ## Nostr event | ||
| 14 | |||
| 15 | This NIP specifies the use of event kind `30078` (parameterized replaceable event) with a `d` tag containing some reference to the app name and context -- or any other arbitrary string. `content` and other `tags` can be anything or in any format. | ||
| 16 | |||
| 17 | ## Some use cases | ||
| 18 | |||
| 19 | - User personal settings on Nostr clients (and other apps unrelated to Nostr) | ||
| 20 | - A way for client developers to propagate dynamic parameters to users without these having to update | ||
| 21 | - Personal private data generated by apps that have nothing to do with Nostr, but allow users to use Nostr relays as their personal database | ||