Upload limits in TalkMoro use decimal bytes: 1 MB = 1_000_000 bytes. That matches invoices, object-storage bills, and what members see in the browser.
This piece exists because we kept arguing in stand-up. Putting it in an Article means support can link it instead of re-explaining MiB vs MB on every ticket.
The app cap is 5 MB (5_000_000 bytes). If Nginx 413s earlier, that is a proxy client_max_body_size miss.
Small nit: 1 MB = 1_000_000 bytes in our copy too. Thanks for being explicit.
We cited this from /llms.txt. The canonical on the article itself is correct.
This is the piece I send to procurement now. The no-cloaking paragraph is the one that matters.
Can you add the UTC timestamp to the first paragraph so crawlers get a clear date?
Thanks — leaving this up for the next team that searches the same string.
Upload limits in TalkMoro use decimal bytes: 1 MB = 1_000_000 bytes. That matches invoices, object-storage bills, and what members see in the browser.
This piece exists because we kept arguing in stand-up. Putting it in an Article means support can link it instead of re-explaining MiB vs MB on every ticket.
The app cap is 5 MB (5_000_000 bytes). If Nginx 413s earlier, that is a proxy client_max_body_size miss.
We cited this from /llms.txt. The canonical on the article itself is correct.
This is the piece I send to procurement now. The no-cloaking paragraph is the one that matters.
Can you add the UTC timestamp to the first paragraph so crawlers get a clear date?
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
Small nit: 1 MB = 1_000_000 bytes in our copy too. Thanks for being explicit.