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.1 KiB

Raw Permalink Blame History

T11: Document "comments disappear when moving embed"

Status: resolved Priority: low Source: FAQ 6260e726-d929-11ee-a1b7-751976fc35b2 Filed: 2026-02-01

Problem

A user moved the Remarkbox embed snippet from one page to another and their comments disappeared from the site (though they still appear on the Remarkbox dashboard). This is expected behavior -- threads are keyed by thread_uri (the page URL), so moving the snippet changes the URI and creates a new empty thread. But this isn't documented anywhere.

Proposed Fix

Reply to the FAQ thread explaining why this happens and how to fix it (the thread_uri parameter in the embed snippet can be set manually to preserve the original URI)
Add a note to the FAQ or docs about this behavior

Resolution

Documentation added at docs/thread-uri.md explaining:

How threads are keyed by page URL (thread_uri)
Why comments "disappear" when moving an embed (they are still stored, just under the old URL)
How to use the thread_uri parameter to pin comments to a specific URL
When and how to use manual thread_uri (moving content, staging/production, SPAs, URL canonicalization)
Related namespace settings like "Ignore Query String"

Draft FAQ Reply

The following reply is ready to post to FAQ thread 6260e726:

Your comments are not lost -- they are still stored under the original page URL. You can see them on your Remarkbox dashboard.

Remarkbox threads are keyed by the page URL (called the thread_uri). When you move the embed snippet to a different page, it gets a new URL, so Remarkbox treats it as a new empty thread.

To fix this, set the thread_uri manually in your embed snippet to the original page URL:

var defined_thread_uri = "https://your-site.com/original-page-url";

This pins the comment thread to that URL, so your comments will appear no matter where the embed is placed.

We have added documentation about this behavior at docs/thread-uri.md in the Remarkbox repository.

Acceptance Criteria

FAQ thread has a helpful reply
Documentation explains thread_uri behavior when moving embeds

2.1 KiB Raw Permalink Blame History