Changeset 67c1f24 in Klonkt for CHANGELOG.md

Timestamp:

07/17/2026 12:38:54 AM (8 weeks ago)

Author:

Robin <roboburr@…>

Branches:

main

Children:

92a2c46

Parents:

3778ddb

git-author:

Robin <roboburr@…> (07/17/2026 12:38:34 AM)

git-committer:

Robin <roboburr@…> (07/17/2026 12:38:54 AM)

Message:

Feature: owner moderation of incoming replies (remove + tombstone + report)

The site owner could not remove an incoming reply, and thread-filling would
re-fetch a locally deleted one (crawlThread seeds its dedup set from
ap_interactions). New ap_rejected_objects table: rejectInteraction() (tenancy-
scoped to the owner's site) deletes the row and tombstones the object URI;
handleInbox and crawlThread skip tombstoned URIs, so a removed reply never
returns via re-delivery or thread-filling. A report action feeds sendReport
from the locally stored object/actor URIs, so flagging also works for private
notes that authorize_interaction cannot fetch (401/404). Thread nodes get
owner-only report + remove buttons (confirm via the global data-confirm
handler); i18n NL/EN/DE. Covered by test/reply-moderation.test.js (59 tests
green); full flow verified in a browser: buttons render for the logged-in
owner, remove deletes the reply and writes the tombstone. Beads: klonkt-demo-qul.

Co-Authored-By: Claude Opus 4.8 <noreply@…>

File:

• CHANGELOG.md (modified) (1 diff)

CHANGELOG.md

@@ -13 +13 @@
   collapsed "Unreachable" section for cleanup. Old /following and /followers
   links redirect to /connect.
+- **Moderate incoming replies on your own posts.** As the site owner you can now
+  remove a reply from your thread (it stays removed: re-delivery and
+  thread-filling are blocked by a tombstone) and report it to its author's
+  server, straight from the thread. This also works for private replies, which
+  cannot be handled via the fediverse interact flow.
 
 ### Fixed