Direct file transfer

How it works

AirDrop, a cabled copy, and a direct SFTP push are direct. A link upload is not: the bucket holds the bytes. Direct fails when the two ends are not online together.

Two edit bays copy 40 GB over the studio LAN in minutes. No cloud bill, no expiry. The same cut for a remote client cannot use that path. They upload. Direct was the local case only.

How it differs

Direct is not peer-to-peer swarming. A swarm has many recipients uploading. Direct has two ends.

NAT often blocks inbound direct connections. A relay appears and the transfer is no longer direct.

Say if a relay is in the path.

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 direct file 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 direct file 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.