Skip to content

v0.2.4 — per-conversation mention requirements

Choose a tag to compare

@web3blind web3blind released this 24 Sep 11:51

Changes

  • Add require_mention_by_peer: opt selected conversations in or out of mention requirements without changing the global policy.
  • Accept strict YAML booleans with string or numeric peer IDs. Missing or invalid entries inherit the global setting.
  • Preserve authorization checks before invocation filtering; the override does not grant access.
  • Document configuration and test raw message intake, global fallback, authorization and YAML precedence.

Requires Hermes >=0.21.3. Existing YAML allowed_users_by_peer support is unchanged. No private configuration, credentials or client data are included.

Verification

This release does not modify installed user configuration or restart gateways.