russell@unturf.com f1cffe2e79 Resolve all 14 tracked tickets (T0-T13)

High priority fixes:
- T0: Profile page now filters comments by namespace (was leaking cross-site)
- T1: URI hostnames and namespace names normalized to lowercase (was causing
  duplicate threads and "stock comments" bug). Includes merge script.
- T2: Thread detail API now paginated with SQL-side filtering (was 502 on
  267+ reply threads)

Features:
- T3: GDPR account deletion (tombstone user with scrubbed PII) and data export
- T4: Customizable button text and comment labels per namespace
- T5: Self-service namespace deletion for owners
- T6: @mention notifications with profile links
- T7: Webmention receiving endpoint with h-card extraction
- T8: Configurable max nesting depth and collapse depth per namespace
- T9: AJAX thread title search to prevent duplicates
- T10: Browser push notification support (VAPID/service worker)

Docs and housekeeping:
- T11: Documented thread_uri behavior when moving embeds
- T12/T13: Drafted community replies for resolved feature requests
- Collapse depth defaults to infinite (load-more disabled unless configured)

364 tests pass, 4 skipped.

2026-02-01 20:02:47 -05:00

2 KiB

Raw Permalink Blame History

T13: Reply to lock/archive thread confirming done

Status: resolved Priority: low Source: meta 7e9d5864-84e3-11ea-836b-040140774501 Filed: 2026-02-01

Problem

The "lock and read-only archive a thread" feature request on meta has no replies, but the feature is fully implemented. Moderators can lock/unlock threads from the UI (show-node.j2), backed by views/authenticated/lock.py. The API also enforces locked thread restrictions.

Proposed Fix

Post a reply to the thread confirming the feature exists, explaining where to find the lock button (next to the watch button, visible to moderators on root threads).

Resolution

Reply drafted below. Ready to post to meta thread 7e9d5864 using the Python client or API.

Draft Reply

The following reply is ready to post to meta thread 7e9d5864-84e3-11ea-836b-040140774501:

This feature is now implemented. Moderators can lock and unlock threads directly from the Remarkbox UI.

How to lock a thread:

Navigate to the root thread you want to lock.
Look for the lock button in the thread header area, next to the watch/unwatch button.
Click lock to prevent new comments on that thread.
The button changes to unlock so you can re-open the thread later.

Who can lock threads:

Only namespace moderators (owners and users with moderator roles) see the lock/unlock button. Regular commenters cannot lock threads.

What happens when a thread is locked:

The reply form is hidden for all users.
Existing comments remain visible and readable.
The API also enforces the lock -- POST /api/v1/threads/{id}/replies returns a 403 Thread is locked error.
Moderators can unlock the thread at any time to allow new comments.

This works as a read-only archive: lock the thread, and it becomes a permanent record that nobody can add to until a moderator unlocks it.

Acceptance Criteria

Reply posted to meta thread 7e9d5864 confirming the feature is implemented

2 KiB Raw Permalink Blame History