Changeset ca25f360 in Klonkt for src/routes/posts.js

Timestamp:

06/25/2026 05:37:12 AM (3 months ago)

Author:

Robin Genis <roboburr@…>

Branches:

main

Children:

2923a95

Parents:

4c9c60b

Message:

feat(fediverse): federate post edits as Update (Mastodon refreshes cached copy)

Editing an already-published, federated post now sends Update(Note) to followers
(with an 'updated' timestamp), so Mastodon refreshes the cached post instead of
keeping the stale original — e.g. fixes a post that federated before content
handling existed. New-publish still sends Create; fan_only never federates.

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

File:

• src/routes/posts.js (modified) (1 diff)

src/routes/posts.js

@@ -354 +354 @@
   } catch (e) { /* FTS issues non-fatal */ }
 
-  // ActivityPub: federate when a post BECOMES published (draft/scheduled → published
-  // via the editor). A brand-new published post is handled in the create route.
-  if (finalStatus === 'published' && post.status !== 'published' && !fanOnly) {
-    ActivityPubService.deliverCreate(site, {
+  // ActivityPub: federate edits to followers. A post that BECOMES published →
+  // Create (new post); an already-published post that's edited → Update (so
+  // Mastodon refreshes its cached copy). fan_only posts don't federate.
+  if (finalStatus === 'published' && !fanOnly) {
+    const apPost = {
       id: post.id, slug: finalSlug, title: title || finalSlug,
       content: cleanContent, cover_image_url: cover_image_url || null,
       published_at: publishedAt, created_at: post.created_at,
-    }).catch(() => { /* best-effort */ });
+    };
+    if (post.status !== 'published') ActivityPubService.deliverCreate(site, apPost).catch(() => { /* best-effort */ });
+    else ActivityPubService.deliverUpdate(site, apPost).catch(() => { /* best-effort */ });
   }