Everything runs through CIND3R3LLA.
A firewall pipeline: consent first, then screening, and only then the public archive. Consent is enforced in code today. The screening stage is in development.
The bot joins a public group and asks before anything is read. Capture starts only after an explicit opt-in, and stops the moment consent is withdrawn. Every opt-in and opt-out is recorded, so the archive can always prove why a message is there.
The heart of the firewall: every image and video is hashed and checked against known-abuse databases before it can be stored. Flagged media is blocked and never reaches the archive. The operator sees it in a review queue, nowhere else.
Only what clears screening is published. What remains becomes permanent public pages: full-text search across every message, filters by group, author, date and media, infinite scroll, inline video, and SEO-friendly stable URLs. Search engines index it, people actually find it.
A second line after screening: anyone can report a published message. Reports reach the operator's console for review, takedown, and audit. Moderation is a first-class workflow, not an afterthought.
Planned capabilities
In development or design. Order and scope may change, because this is alpha software and we would rather ship the safeguards first.
The same consent-first archive and bot suite for Matrix rooms.
Automatic topic grouping across archived content.
A dedicated browsing surface for archived video and images.
Bulk actions, policies, and reviewer queues.
Screening and summaries that run on your own hardware.
One deployment, many isolated archives.