From b302ae3f3e2d90f2d9e73a46c20554f30e99f15c Mon Sep 17 00:00:00 2001 From: Cameron Aragon <69489633+camaragon@users.noreply.github.com> Date: Thu, 27 Aug 2026 01:20:19 +0000 Subject: [PATCH] docs(buzz): clarify reaction-only user precedence --- plugins/platforms/buzz/adapter.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/plugins/platforms/buzz/adapter.py b/plugins/platforms/buzz/adapter.py index 114ed9142e..c4114b3fe9 100644 --- a/plugins/platforms/buzz/adapter.py +++ b/plugins/platforms/buzz/adapter.py @@ -26,11 +26,13 @@ Configuration in config.yaml:: credentials_file: "" # JSON file holding the nsec (fallback for BUZZ_PRIVATE_KEY) allowed_users: [] # empty = allow all; entries are hex pubkeys or npubs reply_in_thread: true # false = post replies flat to the channel timeline + reaction_only_users: [] # acknowledge explicit tags without dispatching; allowed_users wins on overlap Or via environment variables (overrides config.yaml): BUZZ_RELAY_URL, BUZZ_CHANNELS, BUZZ_HOME_CHANNEL, BUZZ_POLL_INTERVAL, BUZZ_CLI_PATH, BUZZ_CREDENTIALS_FILE, BUZZ_ALLOWED_USERS, - BUZZ_ALLOW_ALL_USERS, BUZZ_REPLY_IN_THREAD, BUZZ_REPLY_TO_MODE + BUZZ_REACTION_ONLY_USERS, BUZZ_ALLOW_ALL_USERS, BUZZ_REPLY_IN_THREAD, + BUZZ_REPLY_TO_MODE The only secret is BUZZ_PRIVATE_KEY (nsec or hex) — it belongs in ``~/.hermes/.env``. It is passed to the CLI via the subprocess