Changelog — 2.363–2.371
Releases 2.363.0 through 2.371.1. Current releases are on the main changelog, and every band is listed in the release archive.
Loading audio...
Version 2.371.1
October 15, 2026Our status page keeps up with a sister tool that now says less in public
- One of our sister tools now gives a shorter public answer when asked whether it is healthy,so that it says nothing about how it is built. Our own status page reads that shorter answer, and still turns red, in plain words, when something is wrong.
- Nothing to do at your end.
Version 2.371.0
October 15, 2026The software under the site, moved to a version that still gets security fixes
- The site now runs on a supported release of the software it is built on. The release we were on stopped receiving security fixes earlier this year, and fixes published since then would never have reached it. We moved before that could matter, and checked the site, its tests and its build on the new release first.
- Two small services behind the site moved too, including the one that turns a place name into a location for prayer times and events.
- Nothing to do at your end.
Version 2.370.1
October 14, 2026Our release guide, brought up to date after today’s release
- A one-off check, done: the first release of today’s translation changes had to look by hand for translations and articles in progress, because the version it replaced could not report them. That release has gone out, with nothing running when it did, and our guide now says that every later release makes the check by itself.
- Nothing to do at your end.
Version 2.370.0
October 14, 2026Translations keep going when you close the tab
- A translation carries on if you close the page or lose your connection. It used to stop, and the parts already translated were lost. Come back to the page and it shows how far it has got.
- An article that finished while you were away now stays finished. Closing the tab while one was being written could mark it as failed, even though it had been saved.
- One job at a time on each project. A translation or an article now won’t start while other work on the project is running, and a transcription won’t start over a translation or an article. A note says what is running. Before, they got in each other’s way.
- Opening a project in the middle of a translation no longer resets it. If the site restarts during a translation or an article, the project now says so and lets you start it again.
- A project can’t be deleted while work on it is running. Cancel the work first. When a delete is refused, it now says why.
- Cancel stops a translation or an article within half a minute, even in the middle of a slow step. A cancel could previously be missed, and the cancelled work saved anyway.
- Smaller fixes: a failed transcription now shows its error, where the page used to keep spinning. A cancel that could not reach the server no longer pretends it worked.
- Nothing to do at your end.
Version 2.369.0
October 14, 2026Cancel stops your job, and only yours
- Who can stop a job: the person who started it, or a super-admin. On the audio screens any author could cancel or delete anyone’s narration, because the check meant to prevent it could never refuse. That is fixed, and each cancel is now recorded.
- Cancel in an editor stops that editor’s work: it stopped whichever image was being made at the time, which could be someone else’s. It now stops exactly the job you pressed it for, and a Cancel pressed just before the work begins still stops it.
- A narration that is still running now has to be cancelled before it can be deleted, so it is not left working on a record that has gone.
- Clearer words: a cancelled job now says it was cancelled, rather than that the connection dropped, and cancelling voice work says it finishes the part it is on.
- Nothing to do at your end.
Version 2.368.0
October 14, 2026Generation screens pick their work back up
- A dropped connection keeps track of your work: if the connection drops while something is being made — a voice recording, artwork, a title card, a video, a story or character portraits — the screen now goes on following it, shows its progress or its place in the queue, and shows the result when it is ready. Until now the screen could report a failure while the work carried on and finished out of sight.
- Coming back picks it up too: something you started that is still running now shows at the top of its screen when you return to it.
- The voice studio: a progress update that arrived in two pieces could be read as a failure. It is now read whole.
- Cancel on character portraits now stops the work itself, not just the page’s view of it.
- Saving no longer undoes work that finished out of sight: when an editor picks a comic, a video or a title card back up, it now takes in what that work made, and the character pages take in new portraits without losing what you were typing. Before, saving afterwards could put the old version back.
- A cancel that arrives just after the work finished now says it finished, and shows the result, where it used to call the result cancelled.
- Nothing to do at your end.
Version 2.367.0
October 14, 2026A stopped job now lets go, and updates wait for work in progress
- A job stopped by an update now lets go: on 13 October an update to the site stopped a narration part-way. Its hold on voice generation was left behind, so studio recordings waited behind work that had already ended, for about two hours. Each hold now records who took it and, where there is one, the job it belongs to, and is released as soon as that job is known to have ended, or within a couple of minutes of whatever took it stopping.
- Updates wait for work in progress: before an update restarts the site, it now checks for anything still running and waits for it to finish, rather than stopping it. Something that genuinely cannot wait can still go ahead, but only on purpose, with the reason written down.
- The voice studio keeps its place in the queue: a recording waiting its turn now stays in line properly, says what it is waiting behind and when that will be free at the latest, and waits up to two hours rather than giving up after five minutes. It can still be cancelled while it waits.
- A way out for administrators: the Jobs page now shows what is holding each kind of generation and when it frees itself, and lets an administrator release a stuck hold — after explaining what will happen, including anything it cannot check.
- The nightly Reflection video now waits its turn for voice generation instead of running alongside other work.
- Nothing to do at your end.
Version 2.366.4
October 13, 2026Tidying up after last week’s storage move
- A temporary account removed: the account we made only to copy files during last week’s storage move has been deleted, now that nothing needs it.
- No recycled numbers: new machines now get numbers above any we have used so far, so a new one is not mistaken for a machine we retired.
- Nothing to do at your end.
Version 2.366.3
October 13, 2026No wall, no start
- A wall that cannot be skipped: the machines we walled earlier today now refuse to start anywhere their wall is not in place. We proved it both ways on each: with the wall removed the machine would not start, and with it back the machine started normally.
- Nothing to do at your end.
Version 2.366.2
October 13, 2026A backup warning that can clear again
- Our own backup check: it had been warning all day about a few machines we decided not to back up, so a new problem would have looked like more of the same. Those machines are now named as deliberate exceptions, each with its reason, and the check can read clear again.
- Kept honest: an exception that no longer matches a machine, or a machine that starts being backed up after all, is flagged for us to tidy away.
- Nothing to do at your end.
Version 2.366.1
October 13, 2026Our code host, brought up to date
- Security updates: the service that holds our code and runs our checks has moved to its latest release, which its makers asked everyone to install promptly.
- Old check results: the record of each finished automated check is now kept for 400 days, a choice we have written down rather than left to a default.
- The machines that run those checks were brought up to date as well, one at a time.
- Nothing to do at your end.
Version 2.366.0
October 13, 2026Walls that let through only what is named
- A stricter kind of wall: some of our newest machines may now reach only the few things they need, by name, and only the few machines that look after them can reach in. Everything else is refused and counted.
- Proven from both sides: each wall was tested from inside the machine and from outside it when it went up. Every refusal was checked against the same destination answering from elsewhere, so a refusal shows the wall at work rather than a destination that happened to be down.
- Nothing to do at your end.
Version 2.365.0
October 13, 2026Rewrite one scene’s narration, and keep the story whole
- For our story writers: each scene now has a “Rewrite with AI” button, for a scene whose words you would like told differently. The AI writes that one scene again from the story and the scenes around it, and an Undo puts back what was there.
- Keeping the story whole: what the AI writes is checked before you see it. It is turned away if it repeats a scene’s dialogue (you would hear it twice) or comes back unchanged, and it is marked for you to check if it names someone or somewhere the story does not.
- Nothing to do at your end.
Version 2.364.0
October 13, 2026A story’s missing narration, written in the editor
- For our story writers: each scene in the story editor now shows the words that will be read aloud, and you can change them. If a scene has none of its own, one button asks the AI to write them from the story, for that scene only, and you read them before you save.
- Nothing to do at your end.
Version 2.363.18
October 13, 2026A story video read its picture notes aloud
- What went wrong: in a story video made this morning, two scenes were read from the notes that describe each picture (“close-up of …”), not from the story. The AI that writes our stories had left those two scenes without words of their own, and the step that saves a story filled the gaps with the picture notes. Every check after it saw text and let it through.
- Why we missed it: we fixed the same mistake in August where the video is made, and did not look for its twin where the story is saved. They had been written on the same day.
- What changed: if a scene comes back without words of its own, the story is now written again. If one is still missing, the editor marks it, and the video will not start until it has words. The editor also shows what will be read aloud for each scene. Each scene is now read only from its own story text, and the picture notes are not read aloud or shown as captions.
- Nothing to do at your end. The story will be made again.
Version 2.363.17
October 12, 2026The new service’s machines, set up and checked
- Behind the scenes: the machines for the service we are building are now set up, and we checked that everything they need comes back by itself after a restart. Nothing runs on them yet.
- Nothing to do at your end.
Version 2.363.16
October 12, 2026The retired machines’ backups, gone too
- Behind the scenes: the backups of the machines we retired earlier today have now been removed as well, so nothing of them is left to look after.
- Nothing to do at your end.
Version 2.363.15
October 12, 2026New machines for a service we are building
- Behind the scenes: the machines for a service we are building now appear in our own records and checks. Nothing runs on them yet; each will be set up and proven before it does.
- Nothing to do at your end.
Version 2.363.14
October 12, 2026The old storage, retired for good
- Behind the scenes: the storage we moved away from on Friday has now been retired for good, along with a few other machines that were already switched off. Our own records and maintenance pages no longer list them, and their backups are kept for now.
- A tool that waited too long: one of our own checks, meant to give up on a silent address in a second or two, could wait for many minutes instead. It now gives up in seconds, and its self-test proves it.
- Nothing to do at your end.
Version 2.363.13
October 12, 2026A small tool follows our files to their new home
- Behind the scenes: when our files moved to their new home last week, one small tool that works on them directly stayed behind. It now finds the files by name, so it can follow them, and we tightened two of its safety checks along the way.
- Nothing to do at your end.
Version 2.363.12
October 11, 2026A restore, tested as it would be used
- Behind the scenes: our files are backed up every night. We have now brought back the most demanding collection in full from that backup, and checked it the way the tool that reads it does. Along the way we fixed a gap that would have made those restored files unreadable to that tool.
- Nothing to do at your end.
Version 2.363.11
October 11, 2026Housekeeping for the old storage
- Behind the scenes: our own maintenance stopped trying to reach the storage we moved away from on Friday. It stays switched off as a fallback for now, and will be retired once the new storage's backups have been tested.
- Nothing to do at your end.
Version 2.363.10
October 11, 2026A tighter check on account changes
- Checked when it happens: when an administrator changes someone's account, we now check their own access against our records at that moment, rather than against what was true when they signed in. Nobody can change their own account's status either; another administrator has to.
- Nothing to do at your end.
Version 2.363.9
October 11, 2026A home for one account
- Behind the scenes: we've set up the home for a new service that will, in time, let everyone who uses our tools sign in to all of them with one account. Nothing is built yet; we're writing its plan first.
- Nothing to do at your end.
Version 2.363.8
October 9, 2026Our files have moved to their new home
- The move is done: the pictures, audio and recordings behind this site and our other tools now live on their new storage, which repairs itself if a disk fails. Every file was checked before and after the switch, and the old storage is kept as a fallback for now.
- A check that was watching the wrong place: our own status page was still checking the old storage. It now follows the new home.
- Nothing to do at your end.
Version 2.363.7
October 9, 2026A recording known to be in one language can now say so
- Working it out stays the default: our AI transcription works out a recording's language for itself, piece by piece, and that is the right choice for a lesson that moves between languages. On our first measured lesson, it followed the switches well.
- New: a recording known to be in one language can now say which, and the transcription then works in that language throughout.
- Nothing to do at your end.
Version 2.363.6
October 9, 2026Getting ready to move where our files are kept
- A careful move: the pictures, audio and recordings behind this site and our other tools are moving to new storage designed to repair itself if a disk fails. The new home is ready and checked, and nothing has moved yet.
- When it does, the switch should take a few minutes, and the old storage stays in place as a fallback until the new one has proven itself.
- Nothing to do at your end.
Version 2.363.5
October 9, 2026Our checks were queueing, so they got more room
- A queue behind the scenes: this morning the automated checks that every change goes through before it reaches you were waiting in line behind a few long-running tests.
- More room for them: we have added capacity, so changes, fixes included, can reach you sooner.
- Nothing to do at your end.
Version 2.363.4
October 9, 2026Our development sites now check every visitor's pass themselves
- A sign-in, checked twice: earlier today our development copies of our sites went behind a sign-in. They now also check, themselves, that each visit really passed it, so the sign-in can't be stepped around.
- It never touched this site. Only the development copies we test changes on are affected.
- Nothing to do at your end.
Version 2.363.3
October 9, 2026Old side projects switched off, and their addresses now lead somewhere useful
- namaaz.net now leads here: our old prayer-times site was years out of date, so we have switched it off. Its address now brings you to this site's home page, where our prayer times already live.
- Some older project sites now point to our studio: a few earlier project sites that nobody was using now lead to our studio's site, while one of them is rebuilt properly from the start.
- Nothing to do at your end.
Version 2.363.2
October 9, 2026Our in-house AI got quicker, and can read much more at once
- Faster writing: the AI behind our drafting and checking tools now writes noticeably faster. It proposes a few words ahead and checks them together, and every word it keeps is one the same model chose, so the answers come from the same model as before.
- Longer texts in one go: it can now take in a long talk's whole transcript in a single request, which until today was too long for it.
- A door closed: a debugging entrance that belongs only to our development copy of the site could be reached from outside. It is now refused everywhere. It never touched this site, and we found no sign that anyone used it.
- Nothing to do at your end.
Version 2.363.1
October 9, 2026Security fixes from the framework the site is built on
- Behind the scenes: the open-source framework this website is built on published fixes for several security issues, and we have moved to the fixed version. Our own routine check of the libraries we depend on is what flagged it.
- Nothing to do at your end.
Version 2.363.0
October 9, 2026Our record said a step was skipped when it had run
- Behind the scenes: when a recording is transcribed, we now keep a record of how its language was decided: what the language detection heard, what the transcription heard, and which of the two settled it. Until now our own record said the language detection had been skipped, when in fact it had run and its answer had counted.
- Both listen mostly to the opening. So a lesson that opens in Arabic and continues in Persian can be labelled Arabic. The new record lets us measure how often that happens before we change which answer counts.
- Transcripts are labelled exactly as before. Nothing to do at your end.