nip78: add pub.ditto.frontendConfig
This commit is contained in:
parent
387ddb9dfb
commit
22ea907e86
|
@ -2,6 +2,12 @@
|
||||||
|
|
||||||
[NIP-78](https://github.com/nostr-protocol/nips/blob/master/78.md) defines events of kind `30078` with a globally unique `d` tag. These events are queried by the `d` tag, which allows Ditto to store custom data on relays. Ditto uses reverse DNS names like `pub.ditto.<thing>` for `d` tags.
|
[NIP-78](https://github.com/nostr-protocol/nips/blob/master/78.md) defines events of kind `30078` with a globally unique `d` tag. These events are queried by the `d` tag, which allows Ditto to store custom data on relays. Ditto uses reverse DNS names like `pub.ditto.<thing>` for `d` tags.
|
||||||
|
|
||||||
|
The sections below describe the `content` field. Some are encrypted and some are not, depending on whether the data should be public. Also, some events are user events, and some are admin events.
|
||||||
|
|
||||||
## `pub.ditto.blocks`
|
## `pub.ditto.blocks`
|
||||||
|
|
||||||
An encrypted array of blocked pubkeys, JSON stringified and encrypted with `nip07.encrypt`.
|
An encrypted array of blocked pubkeys, JSON stringified and encrypted with `nip07.encrypt`.
|
||||||
|
|
||||||
|
## `pub.ditto.frontendConfig`
|
||||||
|
|
||||||
|
JSON data for Pleroma frontends served on `/api/pleroma/frontend_configurations`. Each key contains arbitrary data used by a different frontend.
|
Loading…
Reference in New Issue