Changeset 2abd3d2 in Klonkt for .beads


Ignore:
Timestamp:
07/01/2026 10:15:27 PM (2 months ago)
Author:
roboburr <roboburr@…>
Branches:
main
Children:
fc229f5
Parents:
fe97cc3
Message:

chore: tracker housekeeping

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • .beads/issues.jsonl

    rfe97cc3 r2abd3d2  
    77{"_type":"issue","id":"prutfolio-src-k1q","title":"News/Circle: some remote video embeds do not render","description":"A Loops video in the News feed did not load like other providers; the Circle also lacks a video thumbnail for such posts. Reproduce first (regression or never supported?), then fix. Phase 1.","status":"open","priority":2,"issue_type":"bug","owner":"roboburr@gmail.com","created_at":"2026-07-01T22:02:57Z","created_by":"roboburr","updated_at":"2026-07-01T22:02:57Z","dependency_count":0,"dependent_count":0,"comment_count":0}
    88{"_type":"issue","id":"prutfolio-src-ovj","title":"Fediverse: verify outgoing reply mentions against remote receivers","description":"Reported case: a Klonkt reply to a remote (mastodon.xyz) post where the mention handling looked off on the receiving side. First verify against current main (the reporting instance may run older code), diff the note JSON against the expected Mention shape, then fix if real. Phase 1.","status":"open","priority":2,"issue_type":"bug","owner":"roboburr@gmail.com","created_at":"2026-07-01T22:02:55Z","created_by":"roboburr","updated_at":"2026-07-01T22:02:55Z","dependency_count":0,"dependent_count":0,"comment_count":0}
    9 {"_type":"issue","id":"prutfolio-src-xgg","title":"Fediverse: notification when mentioned in a non-reply post","description":"An inbound Create whose Mention tag targets one of our actors, but which is not a reply to our content, is currently ignored. Store + show it in the fediverse notifications. Phase 1.","status":"open","priority":2,"issue_type":"feature","owner":"roboburr@gmail.com","created_at":"2026-07-01T22:02:53Z","created_by":"roboburr","updated_at":"2026-07-01T22:02:53Z","dependency_count":0,"dependent_count":0,"comment_count":0}
     9{"_type":"issue","id":"prutfolio-src-xgg","title":"Fediverse: notification when mentioned in a non-reply post","description":"An inbound Create whose Mention tag targets one of our actors, but which is not a reply to our content, is currently ignored. Store + show it in the fediverse notifications. Phase 1.","status":"closed","priority":2,"issue_type":"feature","owner":"roboburr@gmail.com","created_at":"2026-07-01T22:02:53Z","created_by":"roboburr","updated_at":"2026-07-01T22:15:26Z","closed_at":"2026-07-01T22:15:26Z","close_reason":"Built on main: inbound Create with a Mention tag targeting one of our actors (non-reply) is stored (ap_mentions) and shown in fediverse notifications with a link to the original. Verified live Klonkt-to-Klonkt (democirkel -\u003e beta).","dependency_count":0,"dependent_count":0,"comment_count":0}
    1010{"_type":"issue","id":"prutfolio-src-412","title":"Fediverse: auto-link plain URLs in outgoing replies and posts","description":"A bare URL typed in a reply (and in post content) federates as plain text; it should become a clickable link in the outgoing note. Phase 1 bug sprint.","status":"closed","priority":2,"issue_type":"bug","assignee":"roboburr","owner":"roboburr@gmail.com","created_at":"2026-07-01T22:02:52Z","created_by":"roboburr","updated_at":"2026-07-01T22:07:43Z","started_at":"2026-07-01T22:03:23Z","closed_at":"2026-07-01T22:07:43Z","close_reason":"Fixed on main: bare URLs in outgoing posts + replies now federate as clickable links (anchor-aware, punctuation-safe). Verified live on beta.","dependency_count":0,"dependent_count":0,"comment_count":0}
    1111{"_type":"issue","id":"prutfolio-src-byh","title":"Retry Follow delivery so follows don't get stuck on 'pending'","description":"followActor() inserts the ap_following row as 'pending' and then delivers the signed Follow once, with no retry (unlike deliverCreate, which uses the ap_delivery retry queue). A single transient delivery failure therefore leaves the follow permanently 'pending' — the remote never received it, so no Accept ever comes back.\n\nBuild later:\n- Route the Follow delivery through the existing ap_delivery retry queue (backoff), OR\n- Add a periodic re-send / re-poll for follows still 'pending' after N minutes.\n\nNote: a legitimately locked (manual-approval) account also shows 'pending' until the person approves — that is NOT this bug and must stay pending. Only retry the *delivery*, don't auto-flip status.\n\nWorkaround today: unfollow + follow again sends a fresh Follow.","status":"closed","priority":2,"issue_type":"feature","assignee":"roboburr","owner":"roboburr@gmail.com","created_at":"2026-06-26T13:36:15Z","created_by":"roboburr","updated_at":"2026-07-01T00:45:55Z","started_at":"2026-07-01T00:43:31Z","closed_at":"2026-07-01T00:45:55Z","close_reason":"Fixed: followActor now delivers the Follow via deliverWithRetry() (immediate attempt + ap_delivery backoff queue), so a failed first delivery no longer leaves the follow stuck on 'pending'.","dependency_count":0,"dependent_count":0,"comment_count":0}
Note: See TracChangeset for help on using the changeset viewer.