docs: no exact tier — the file-hash tier was withdrawn
A stale reference to 'the runtime/exact tiers' as the fallback for media too short to carry an audio signature. The exact tier keyed on a file hash and was withdrawn on legal grounds: it fingerprinted the individual copy a user holds rather than the cut the timings describe. The pipeline never emitted a video_hash, so nothing in the code changes — but a spec that still names a withdrawn tier is what makes the withdrawal look like an oversight to the next reader, which is exactly how it nearly got re-added. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
+4
-2
@@ -997,8 +997,10 @@ rewritten.
|
|||||||
|
|
||||||
**Media shorter than 120 s.** The window `runtime/2 ± 60 s` underflows, so no
|
**Media shorter than 120 s.** The window `runtime/2 ± 60 s` underflows, so no
|
||||||
signature is emitted and **no sync offset is applied**. Such items fall back to
|
signature is emitted and **no sync offset is applied**. Such items fall back to
|
||||||
the runtime/exact tiers, which is adequate: a 90-second extra or trailer is not
|
the runtime tier, which is adequate: a 90-second extra or trailer is not the
|
||||||
the content whose cut alignment matters. Both producers must apply the identical
|
content whose cut alignment matters. (There is no `exact` tier: the file-hash
|
||||||
|
tier was withdrawn on legal grounds — it fingerprinted an individual copy rather
|
||||||
|
than the cut the timings describe. See the server spec §3.) Both producers must apply the identical
|
||||||
rule, or they diverge on exactly the short items most likely to be
|
rule, or they diverge on exactly the short items most likely to be
|
||||||
mis-identified.
|
mis-identified.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user