Do not put private keys, credentials, backups, database files, or personal messages into a public issue. Use the repository owner's private security reporting channel if one is enabled, or arrange a private report with the owner. No reporting email address is configured by this source package.
Reports should identify the affected release, concrete reproduction steps using disposable data, expected behavior, and impact. The implementation protects a small personal public-post server; it does not include a multi-user abuse/moderation service, automatic resource quotas, OAuth, or private messaging.
Keep PHP, Python, Caddy, Docker and the host current. Test upgrades with a copy of the private volume, retain recoverable backups, and use the federation acceptance process before announcing a release.