Uploads, and the previews and files Kemble reads from storage for you, now ride out a busy moment at our file storage provider. Kemble waits and tries again by itself, and a large upload sent in parts keeps every part that arrived. A large upload whose last step finished at the storage but whose reply was lost on the way back is recognised as whole and finished, instead of getting stuck. If the storage is still busy after Kemble has waited, you see “File storage is busy — try again in a moment” rather than an unexpected error.
Kemble no longer stands in “Someone”, “Somebody” or “Unknown member” for a person. In messages, replies, threads, files, lists, canvases, workflows, notifications and search you see their name, their @handle, the app that posted, or “Former member” when the account no longer exists. Streamer mode, which you turn on to hide who is calling, still says “Someone is asking you into a call”. A few places still said “Former member” for someone whose name had not loaded yet; the next update fixed that. While a name is still loading, the typing line and reaction lists count people (“Naledi and 1 more are typing…”, “1 person”) rather than inventing one, and a notification whose sender cannot be named yet says what happened and where, such as “You were mentioned in #design”. In Kemble Circle, a reply to a message from before you joined shows no name, as in Kemble Work.
Kemble updates itself in an open tab. If a tab was opened before an update, Kemble loads the new version the first time it needs a part it doesn’t have yet. It does this once, and saves what you’re writing first. It waits while you’re in a call, while files are still uploading and while you have changes that aren’t saved yet; then it tells you Kemble was updated and offers a Reload button for when you’re done. Links between pages on kemble.io now go straight to each page’s own address, so a link opened in a new tab arrives without a redirect.
For developers: when file storage is busy, a request that has to reach it answers 503 storage.busy with a Retry-After header, and sending the same request again is safe; the Files and large uploads page and the list of errors explain it. The page now gives the switch to parts and the part size exactly, as 64 MiB and 16 MiB (16,777,216 bytes).