Large files sent in parts now keep only the copy you see. When a photo or video over 64 MB goes up in parts, Kemble removes where it was taken before keeping it, and the original with the location is no longer kept in storage beside it. Each large file is stored once, finishing it uses far less memory on our servers, and two large uploads started at the same moment can no longer both take the last of a workspace’s storage.
The Trust centre now lists the providers Kemble uses, with Cloudflare, the network kemble.io is served through, first, and links to the full Subprocessor list. Search engines now get each page’s own address: the sitemap and every page’s canonical and sharing link name the address the page is served at, so none of them goes through a redirect.
Emails and notifications from Kemble’s servers, canvases, lists and Catch up now name the person: their name, their @handle if the name is blank, or “a former member” if the account is gone, and a message posted by an integration is named after that integration. They no longer fall back to “Somebody”. When the check of a link for a fake sign-in page cannot finish because the check is still starting up, Kemble now checks that link again a few minutes later instead of leaving it unchecked.
For developers, a new documentation page, Files and large uploads, explains how to send a file over 64 MB in parts and carry on after a dropped connection.