What else would I assume?
If there's a 1TB limit I would expect that to be described as "create files up to 1TB in size".
But I doubt they're getting much support burden from this; the product targets home users, providing fixed-price single computer backups. This isn't their B3 blob storage offering.
The most bloated triple-A games out there are only ~100GB. The entirety of OpenStreetMap's data, in XML format, only reaches 147 GB [1]. The latest and greatest 670-billion-parameter LLM is only 600 GB... and they ship it as 163 x 4.3GB files [2]. Among PC gamers [3] about 45% of people have less than 1TB of hard drive space, total.
IMHO it's very unlikely they have a big support burden from this undocumented limitation.
It's clearly a bug though - trying to upload the same file in every single backup, failing every time? There's no way that's the intended behaviour.
[1] https://planet.openstreetmap.org/ [2] https://huggingface.co/deepseek-ai/DeepSeek-R1/tree/main [3] https://store.steampowered.com/hwsurvey
Seems like there is a bug somewhere - whether artificially imposing a file size limit, or in not imposing the limit correctly.
”Should” most certainly. However, often client teams don’t work so closely with backend teams. Or the client team is working from incorrect documentation. Or the client team rightfully assumes that when it reports a file size before uploading, the backend will produce an acceptable error to notify the client.
I guess different kinds of people are drawn to different careers, and people with loose morals, hubris, and a propensity to lie are drawn to marketing. Don't even need an incentive to lie, it's just who they are.
I think you will find that there are people that see "limit <humongous>" and pick the "no limit" or no limit stated option.
> people with loose morals, hubris, and a propensity to lie are drawn to marketing
You are jumping the gun here.