Files
KoalaSync/docs
Timo 6628eaa72d docs: correct the scoping claim in the frame-targeting handoff
The proposal said a registered content script could be scoped to the selected
tab's origin. It cannot, in two ways that both matter.

matches is evaluated against each frame's own URL, not the tab's, so a pattern
for the top-level site would never reach the embedded player frame — the only
frame the change exists to reach. Covering a player origin that is unknown
before discovery requires <all_urls>.

And registration has no tab scoping at all: with several tabs open on the same
site, every one of them gets the script.

The honest cost is therefore that a passive monitor runs in every frame of every
http/https tab while a target is selected, which is a privacy-posture change for
a project that advertises touching only the chosen tab. Recorded so the decision
is made against the real trade rather than the flattering version.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 20:56:07 +02:00
..
2026-07-15 04:45:45 +02:00

Technical Documentation

This directory contains deep-dives into the KoalaSync protocol, architecture, roadmap, and operational guidelines.

Start Here by Role

🏗️ Core Architecture & Design

  • ARCHITECTURE.md: Overview of the communication flows, Dual Heartbeat architecture, and synchronization logic.
  • HOW_IT_WORKS.md: Step-by-step walkthrough of every user flow, from room creation to synchronized playback. Ideal for store reviewers and manual testers.
  • host-control-mode.md: Design, requirements, and edge cases of the Host Control feature.
  • AI_INIT.md: Maintainer and AI-agent onboarding: non-negotiables, workflow order, and safety checks.

📡 Protocol & Synchronization

  • PROTOCOL.md: Low-level message format and payload descriptions for the KoalaSync sync protocol.
  • SYNC_GUIDE.md: Guide on keeping protocol constants synchronized across the workspace.

📋 Compatibility, Roadmap & Contribution

  • TESTED_SERVICES.md: Status of compatibility with major streaming services and contribution guidelines for testing new platforms.
  • KNOWN_LIMITATIONS.md: Threat model and accepted design limitations (NOFIX entries) for security audits.
  • PRIVACY.md: Privacy model and data-handling policy for users, reviewers, and contributors.
  • ROADMAP.md: Planned features, backlog items, and rejected proposals.
  • TRANSLATION.md: Guide for native speakers to contribute and audit dynamic extension/website translations.

🚀 DevOps & Releases

  • devops.md: Guide on the automated tag-based release pipeline.
  • CHANGELOG.md: Detailed history of releases and changes.

For high-level project information and developer setup instructions, refer to the root README.md.