index

Limits and Tradeoffs

LSS is useful because the action travels with the video. That also means it inherits the messiness of video: recompression, crop, scaling, filters, screen recordings, brightness shifts, and device cameras.

Current limitations

  • The carrier has not been benchmarked across TikTok, Instagram, YouTube Shorts, WhatsApp, or every screen-recording path.
  • The package visual carrier is still a low-level frame-plan prototype, not a benchmarked production image codec.
  • The audio carrier is not yet the primary reliability path.
  • Payloads are signed but not encrypted.
  • Demo keys are local; production needs issuer registry and revocation.

Alternative choices

yes no yes no yes no yes no yes no Need a scan-to-action trigger? Visible mark acceptable? Physical tap flow? Nearby radio flow? Only identify known media? Action should travel inside video? Use QR Use NFC Use BLE Use fingerprinting Use LSS Use watermarking

Pointer mode vs manifest mode

The payload type supports both pointer and manifest modes. Pointer mode is the compact shape to prefer when an app can resolve richer data online, because it reduces carrier size and gives product code more control. Manifest mode carries more action data directly and is useful when the scan result must survive without network access. The current resolver package does not perform online lookup by itself.

Network-layer tradeoffs

LSS borrows useful ideas from network protocols, but the tradeoffs are different because the path is media instead of routers.

  • Redundancy improves recovery but consumes carrier capacity.
  • Smaller payloads survive more platforms because fewer fragments are required.
  • More repetition improves confidence but increases the visual or audio time budget.
  • Checksums catch carrier corruption but do not replace signature verification.
  • Expiry limits replay, but short expiry windows can make old reposts stop resolving.
  • Parity fragments can recover loss, but they should be reported so weak scans stay visible.

The default production posture should be conservative: compact pointer payloads, repeated fragments, clear expiry, checksum-gated reconstruction, app-side signature verification, and app-side policy enforcement around resolver usage.

Honest positioning

LSS should not be sold as a QR replacement for every surface. It is strongest when the user is already watching or sharing video and the product wants a native scan-to-action layer without visible creative intrusion.