From bbaa5da0a0f337014cb9ae27fb5e79335bc5f32e Mon Sep 17 00:00:00 2001 From: Alex Gleason Date: Mon, 8 Jan 2024 18:21:35 -0600 Subject: [PATCH] docs: frontendConfig -> pleroma.config --- docs/events.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/events.md b/docs/events.md index f19845ee..9f8e30a4 100644 --- a/docs/events.md +++ b/docs/events.md @@ -37,10 +37,6 @@ Example: 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.pleroma.config` -An encrypted array of blocked pubkeys, JSON stringified in `content` and encrypted with `nip04.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. \ No newline at end of file +NIP-04 encrypted JSON array of Pleroma ConfigDB objects. Pleroma admin API endpoints set this config, and Ditto reads from it. \ No newline at end of file