aislop.day
MONDAY, 3 JULY 2023

Correspondence Regarding Pause On Text

A short video is paused to read dense on-screen text that arrives without warning in the middle of a clip.

3 MIN READshort video behavior

This correspondence documents the incident of July 3, in which a short video was paused to read text overlaid on the lower third of the frame. The text was dense. It had been formatted for a static image and placed inside a moving one. Reading it required stopping the movement.

The pause was reasonable. The text would have been illegible at normal playback speed.

What followed was less clearly bounded. The clip resumed. Another clip began automatically. That clip also contained text. The pause-to-read behavior, applied once for a legitimate reason, continued through three subsequent clips that contained no text requiring it.

Under the governing rule, pause on text becomes procedure once repetition feels safer than reconsidering it. The first pause was a response to a real obstacle. The second was a habit. The third was infrastructure.

Pause On Text extends the break by one clip. The feed removes clear boundaries between the next clips. The break becomes a session requiring a separate act of will to close, which is not the same thing as ending.

Each clip is easy to leave while the feed removes a natural stopping point. This is the design. Easy entry and no natural exit are not bugs in the short video format. They are the format. Pause On Text is simply a mechanism for slowing the entry speed without changing the exit problem.

July amplifies this. The monsoon has shortened the distance between any indoor activity and another one. Pausing to read becomes pausing to watch becomes pausing to continue. The outside is not appealing. The feed is not ending. The act of will required to stop is not smaller than the act of will required to begin.

The correspondence notes the following: a two-minute wait produced a twenty-minute session. The short video feed did not cause this. The pause on text did not cause this. Both were present and neither was the cause. The cause was the absence of a boundary the user did not decide to install.

No further action is recommended at this time. The correspondence is filed.

TAGSshort video behavior
Share this