beta · overview · 0.1.0

Community Interaction

Community Interaction lets a Project Backend store and edit Community Comments, one level of direct replies, anonymous reaction summaries, structured reports, and reversible moderation state against an opaque resource type and ID. MiniCenter owns comment identity, immutable text revisions, ordering, reaction state, report intake, moderation state, and idempotency; the Project Backend owns the resource, Project Membership, visibility, and the decision that a Platform Account may read or contribute.

The beta supports comments, direct replies, author-owned immutable edits and tombstone removal, reactions, structured report intake, reversible Comment restriction, a read-only moderation queue, permanent report decisions, a read-only embedded top-level thread, and durable accepted, edited, removed, and moderated outcome events through a Project Backend. Reporter lists, free-text evidence, account restrictions, reply trees, hard deletion, browser interaction controls, and other lifecycle events are not supported.

Start with create and list comments or the hosted Comment form, continue with direct replies, immutable edits, tombstone removal, then embed a read-only thread. Add reactions, report APIs or the hosted report form, restrict and restore Comments, page the moderation queue, and resolve a report as needed.

Guides

• Create and list resource comments — Authorize in the Project Backend, then idempotently create and page through top-level comments.
• Create and list direct replies — Add one level of replies beneath a resource Comment without crossing client or resource boundaries.
• Edit comments with immutable revisions — Let an author idempotently replace Comment text without losing history or duplicating events.
• Embed a hosted Comment form — Let an authorized browser post one plain-text Comment without exposing a Project Credential.
• Set and summarize reactions — Set one account reaction on a Comment and read anonymous aggregate counts.
• Remove comments into tombstones — Let an author idempotently hide Comment content while retaining operational history.
• Submit and retrieve Comment reports — Submit one structured report and retrieve its received status without exposing reporter identity.
• Embed a read-only Comment thread — Render a centrally operated Comment thread without sending a Project Credential to the browser.
• Restrict and restore Comments — Apply a reversible Comment visibility state without deleting or rewriting content.
• Page the moderation queue — Read reports, decisions, and current Comment moderation state without reporter identity or content.
• Resolve moderation reports — Permanently decide a report and atomically set its Comment moderation state.
• Embed a hosted Comment report form — Let an authorized browser submit one fixed-reason report without exposing a Project Credential.

API Reference

• Create a top-level Community Comment — POST /api/v1/community/comments
• List top-level Community Comments for one resource — GET /api/v1/community/comments
• Consume a Browser Resource Grant and render a read-only Comment thread — POST /api/v1/community/comments/embed
• Render or submit a resource-bound hosted Comment form — POST /api/v1/community/comments/create
• Render or submit a Comment-bound hosted report form — POST /api/v1/community/comments/{commentId}/report
• Create a direct reply to a top-level Community Comment — POST /api/v1/community/comments/{commentId}/replies
• List direct replies beneath one top-level Community Comment — GET /api/v1/community/comments/{commentId}/replies
• Replace a Community Comment body with a new immutable revision — PUT /api/v1/community/comments/{commentId}
• Replace an author-owned Community Comment with a tombstone — DELETE /api/v1/community/comments/{commentId}
• Set or clear one Platform Account reaction — PUT /api/v1/community/comments/{commentId}/reaction
• Read anonymous aggregate reaction counts — GET /api/v1/community/comments/{commentId}/reactions
• Submit one structured Comment report — POST /api/v1/community/comments/{commentId}/reports
• Retrieve one structured Comment report — GET /api/v1/community/comments/{commentId}/reports/{reportId}
• Resolve a report and set Comment moderation state — PUT /api/v1/community/comments/{commentId}/reports/{reportId}/decision
• Restrict or restore a Community Comment — PUT /api/v1/community/comments/{commentId}/moderation
• Read a Community Comment moderation state — GET /api/v1/community/comments/{commentId}/moderation
• Page received reports with current moderation state — GET /api/v1/community/moderation/reports

Event Reference

• Community Comment accepted — A top-level Community Comment or direct reply was accepted.
• Community Comment edited — A top-level Community Comment or direct reply received a new immutable text revision.
• Community Comment moderated — A permanent report decision changed a Community Comment's moderation state.
• Community Comment removed — A top-level Community Comment or direct reply became a tombstone.