Changeset 2d6a9c3 in Klonkt for src/services

Timestamp:

07/16/2026 12:20:51 PM (8 weeks ago)

Author:

Robin <roboburr@…>

Branches:

main

Children:

af21002

Parents:

8878814

git-author:

Robin <roboburr@…> (07/13/2026 05:21:50 AM)

git-committer:

Robin <roboburr@…> (07/16/2026 12:20:51 PM)

Message:

Spoor A step 1: bake post display HTML at save (ActivityPub source model)

Introduce the source/rendered split: posts.content stays the raw source (what
the editor round-trips), a new content_rendered column holds the baked display
HTML. bakePostContent() runs the linkify pipeline once at create/edit and
caches it; the render route serves content_rendered (falling back to an
on-the-fly bake for not-yet-baked posts) and no longer re-linkifies every view.
Verified: baked and fallback paths render byte-identically and a baked lone URL
still becomes an embed. This is the seam for step 2 (resolve @mentions once at
save instead of per page view) and removes the per-render linkify cost.

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

File:

• src/services/ActivityPubService.js (modified) (2 diffs)

src/services/ActivityPubService.js

@@ -1464 +1464 @@
 }
 
+// Bake a post's raw source into its display HTML (the ActivityPub `source` model): done ONCE
+// at save and cached in posts.content_rendered, so page views serve it statically instead of
+// re-linkifying every render. Step 1 = #hashtags + bare URLs (cheap, no network). Step 2 will
+// resolve @mentions here too (webfinger once at save instead of per page view).
+export function bakePostContent(source) {
+  return linkifyBody('', source || '');
+}
+
 // Extract the AP Hashtag tag objects from already-linked reply content.
 function hashtagTags(base, content) {
@@ -2463 +2471 @@
   deliverWithRetry, enqueueDelivery, processDeliveryQueue, startDeliveryWorker,
   getReplyUris, markNotificationsSeen, countUnseenNotifications, hasPlayableAudio,
-  linkifyBody, listFollowers, removeFollower,
+  linkifyBody, bakePostContent, listFollowers, removeFollower,
 };