Jannis Braun 1a2bc0ec52 fix: use timestamp 0 for never-edited profiles in LWW comparisons ...

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.

2026-04-03 05:27:51 +02:00

..

src

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

2026-04-03 05:27:51 +02:00

package.json

perf(deploy): parallel deploys, preserve build cache, prod-only runtime deps

2026-04-01 13:13:17 +02:00

tsconfig.json

chore: Initial commit of Opencord base state

2026-02-18 02:49:21 +01:00

verify-livekit.ts

feat: Optimize WebRTC pipeline for 60fps screen sharing

2026-02-19 03:34:20 +01:00