feat: support encrypted seen-video syncing - #12
Conversation
Add the optional seen_videos capability and a separate seenVideos collection without changing existing sync data formats. Related to OpenTubeX/OpenTubeX#1208.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe sync API now exposes a ChangesSeen videos synchronization
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This adds optional encrypted syncing for seen videos, advertising support to clients and allowing a 16 MiB encrypted collection. The implementation and its stated coverage are consistent, with no identified merge-blocking risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Marked-as-seen subscription videos currently stay on one device even when history sync is enabled. Add the optional
seen_videoscapability and accept the encryptedseenVideoscollection so clients can sync those marks separately from watch history.Existing endpoints, encryption formats, and migration requirements are unchanged. Older clients ignore the new capability and collection. The collection uses the existing encrypted storage and a 16 MiB per-collection limit.
Client implementation: OpenTubeX/OpenTubeX#1209.
Related to OpenTubeX/OpenTubeX#1208.
Validation: all 57 server tests pass;
cargo fmt --checkpasses.Implemented with GPT-6 in Codex.