Large files upload reliably. Cloudflare’s network accepts at most 100 MB in one request, so a file over 64 MB now goes up in parts, and files up to your plan’s limit (500 MB on the largest plan) arrive in full. The progress ring counts every part. If the connection drops, the upload waits until you are back online and carries on from the parts already sent instead of starting over; choosing the same file again after a reload carries on too, and cancelling throws the parts away. Files of 64 MB or less go up exactly as before, in the app and in Kemble Desktop alike.
kemble.io is now served through Cloudflare’s network, which protects it from attacks and delivers it from close to you. For about an hour and a half after the move on 29 October, Kemble Desktop and some visits failed with a secure-connection error (525): one of Cloudflare’s settings offered Kemble’s server only a newer kind of key exchange that the server cannot use yet. That setting is off. Kemble now checks every five minutes that kemble.io answers both through Cloudflare and straight from its own server, so a fault like that one, an expired certificate at the edge, a challenge page or no answer at all is noticed within ten minutes instead of being reported by people. The sound and video of calls, and email, still go straight to Kemble’s own server, and the privacy policy now names Cloudflare among the companies that handle your data.
Deleting a space, a community or a channel with many files now answers promptly, and whatever is left of its stored files is removed in the background.