devsyncwrld/backspace
1
0
Fork 0
Code Issues Pull Requests Actions 28 Packages Projects Releases Wiki Activity

fix: use timestamp 0 for never-edited profiles in LWW comparisons

Browse Source 
profileUpdatedAt ?? createdAt treated freshly registered users as having
"newer" profiles than users with real edit history, because createdAt is
always NOW at registration time. This broke federation profile sync:
the client correctly pushed home → remote, but the remote server's LWW
guard rejected the write (stored createdAt > incoming profileUpdatedAt).

A null profileUpdatedAt means "never edited" — that's timestamp 0, not
the user's creation time.
This commit is contained in:
Jannis Braun
2026-04-03 05:27:51 +02:00
parent 02a44c201d
commit 1a2bc0ec52
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/server/src/utils/sanitize.ts
+1 -1
View File
@@ -49,7 +49,7 @@ export function sanitizeUser(row: typeof schema.users.$inferSelect, isSelf = fal
customStatus: row.customStatus,
isAdmin: row.isAdmin === 1,
discoverable: row.discoverable !== 0,
profileUpdatedAt: row.profileUpdatedAt ?? row.createdAt,
profileUpdatedAt: row.profileUpdatedAt ?? 0,
createdAt: row.createdAt,
homeInstance: row.homeInstance ?? null,
homeUserId: row.homeUserId ?? null,