What changed
Backend is taking over sync responsibility. New API: pushResourcesToPeer. Frontend (TS) will start calling it whenever a document-related change needs to be pushed to a peer.
Testing + rollout
Frontend integration is straightforward; test on devnet after merge.
No DB migration. No mandatory protocol version bump.
Reverting is easy.
When the frontend must call pushResourcesToPeer
New comment
User copies URL (share flow)
Document publish
Document delete
Document move+redirect (call for both old + new locations)
Extra realization
Comments referencing other docs (A references B) require pushes for each referenced doc’s home server, so backlinks propagate correctly for self-hosters.
Same for doc-to-doc references.
Disagreements / nuances
Alex half-jokes about backend auto-pushing all blobs, but it doesn’t know the target site, and frontend needs to show progress/spinner.
periodic syncing does not support private docs, so push is even more important.
Worry: pushing to every referenced doc could become spammy.
Counterpoint: self-hosters relying on federation/backlinks will break without this.
Agreement: backlinks should only be expected within trust relationships (web-of-trust), not “the whole universe.”
Conclusion
Feature is doable but the TS side is more complex than expected because pushes must cover the primary document + all reference targets to keep federation/backlinks consistent for trusted self-hosted peers.
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime