Computer-to-phone transfer

How it works

The phone's free space is the cap. A 6 GB master may not fit. Mobile data policies may block the download. A Wi-Fi download of a link is the usual remote path.

A producer sends a 400 MB review cut by link. The phone on Wi-Fi downloads it. A 12 GB master is refused by free space. They send a proxy to the phone and the master to the suite.

How it differs

This direction hits storage and radio limits the computer did not have.

A sync client that downscales images will not deliver the print file.

Turn off optimize-storage for masters.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For computer to phone transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive computer to phone transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.