In His Name, the Most High
Changelog — 2.447–2.455
Releases 447.0 through 455.1. Current releases are on the main changelog, and every band is listed in the release archive.
Loading audio...
Version 2.455.1
November 20, 2026A home for signing our agreements
- We are setting up our own place to sign agreements. Until now an agreement meant a PDF passed back and forth. We are building our own signing service instead, run by us, so the documents stay with us. The people who sign never need an account: they follow a link in an email. Its home exists now, walled off from everything it does not need, and it shows on our status page before anything runs there. Nothing to do at your end.
Version 2.455.0
November 19, 2026Our transcription address now leads to Katib
- tpscribeflow.com now takes you to Katib. Our transcription service has joined the IlmFlow family under the name Katib, the scribe, and its old address now leads to Katib's page among the IlmFlow tools. Until now it led to our studio's home page, which said nothing about it. Nothing to do at your end.
Version 2.454.0
November 19, 2026Two more old transcription parts switched off
- The steps that cleaned up recordings before transcribing them are gone. One reduced background noise and the other separated a voice from music. The new transcription service will work from the original recording, which modern speech models handle well, and music is never transcribed. Nothing has used either since our transcription tool was paused. Nothing to do at your end.
Version 2.453.0
November 19, 2026Clearing out the old transcription parts
- Two parts of our old transcription pipeline are switched off for good. One turned speech into text and the other guessed which language a recording was in. Nothing has used them since our transcription tool was paused, and the language guesser came under a licence that does not allow the way we work. Transcription is being rebuilt as its own service, and it will bring its own parts. Captions on our videos are not affected. Nothing to do at your end.
Version 2.452.1
November 19, 2026Our records catch up with the caption change
- The new caption timing from 2.452.0 is now in place, and our own records say so. We checked it on three of our published videos after switching: every word came back, and the timings matched the old captions almost exactly. This version only updates our internal notes to match. Nothing changes on the site, and nothing to do at your end.
Version 2.452.0
November 19, 2026The captions on our videos, now on parts we are free to use
- The part that times each word of a video's captions has been replaced. Our Reflection and Vignette videos show their captions word by word, in time with the narration. The part that worked out those timings came under a licence that does not allow the way we work, the same reason our transcription tool is resting, and so did a library it relied on. Both are gone, and the new part is under an open licence. Before switching we checked it against fourteen of our published videos: in almost every caption the timing lands within a tenth of a second of the old one, so the captions you see stay the same. Nothing to do at your end.
Version 2.451.1
November 18, 2026Two backups that had quietly stopped
- One nightly backup never restarted after we reinstalled it. Our setup step switched its schedule on for the next restart, but not for now, and our own check only asked whether it was switched on, not whether it was running. It is running again, tonight's copy is already made, and the setup step now refuses to finish until the schedule is actually running. Nothing to do at your end.
- Another backup was refusing, as it should, after a tidy-up we asked for. We removed a few old duplicate files, and the backup saw fewer files than the night before and refused to keep a copy that looked incomplete. That is its job; we had simply never written down how to tell it the drop was intended. It is backing up again, and the step is written down. Nothing to do at your end.
Version 2.451.0
November 18, 2026Our transcription tool is resting while we rebuild it
- ScribeFlow, which turns our editors' recordings into transcripts and subtitles, is read-only for now. We are rebuilding it as one transcription service shared by this site and our research tools. Two of the parts it uses today come under licences that do not allow the way we work, so rather than keep using them we have paused new transcriptions for everyone until the new service is ready. Every past project stays where it was, to read and download. Nothing to do at your end.
Version 2.450.2
November 15, 2026Our research library stands on its own storage now
- The last shared folder our research library used is disconnected. Earlier today the library stopped needing a shared folder for its list of books; tonight it stopped needing one for the readings it keeps of every page, which now live only in its own storage, and we first restored all of them from that storage to prove they were whole. Before disconnecting, our check found one task still holding the folder open, so we waited for it to finish rather than pull it away, and taught the check to look for that next time. Nothing to do at your end.
- A time we wrote down was wrong. Our technical notes for the last release gave the wrong time for one of its checks: we wrote it from memory rather than reading the clock. They are corrected. Nothing to do at your end.
Version 2.450.1
November 15, 2026The check we forgot to write
- Every change we release now comes with a check that proves it reached you, and the last one shipped without it. The privacy fix in 2.450.0 left us without the small check we run before and after a release, which shows the old wording on the live site first and the new wording after. We wrote it before releasing, ran it against the live site to see it fail in the right places, and it now goes out with the fix. Nothing to do at your end.
Version 2.450.0
November 15, 2026Our privacy page was wrong about our short links
- Our privacy page described the wrong short-link address, and we were keeping more than it said. It named an address we no longer use for short links; the ones we use are tp313.me. It also promised that a click keeps only the website it came from, while we were keeping the whole address of the page, which can show what someone was reading. We now keep only the website, and the page says so plainly. Nothing to do at your end.
Version 2.449.4
November 15, 2026One less thing our research library leans on
- Our research library no longer depends on a shared file store for the list of its books. It now keeps that list in its own storage, and today we disconnected the old shared folder. One fewer piece has to be working for the library to work, and one fewer thing to restore after a disaster. We checked first that nothing still used it, and searches and health checks were normal afterwards. Nothing to do at your end.
Version 2.449.3
November 15, 2026A number that stopped being true
- Our notes for one backup test said how many checks it runs, and the test had since grown by forty. A number written in a document goes out of date the moment the thing it counts grows, and nothing warns anyone. The notes now point at the test's own report of its count instead, and we checked the other counts like it: they were right. Nothing to do at your end.
Version 2.449.2
November 15, 2026A test that waited instead of failing
- One of our backup tests, when something went wrong, sat waiting for input that was never coming, for more than a day, rather than saying it had failed. A test that never finishes tells you nothing, which is worse than one that fails loudly. It now fails at once, and we proved it by breaking it on purpose both ways. Our backups themselves were never affected. Nothing to do at your end.
Version 2.449.1
November 13, 2026A check that asked for too much, and a test that comes first
- Our backup check refused to run on a machine that lacked a tool it did not even need for that check. It worked where we built it, because that machine had the tool; it now asks only for what it uses.
- Any change to the model our translations run on is now tested before translation uses it. Our translation is tested against attempts to trick it every time it is released, and from now on that test also comes first whenever the machinery underneath it changes. Nothing to do at your end.
Version 2.449.0
November 13, 2026Backed up before anyone signs in
- Our new sign-in service will be backed up, and the backup proven to restore, before the first real account is made in it. A copy that comes back is only useful if everyone can sign in to it, so our restore check now proves that too, with a deliberately wrong password that must be refused. Nothing to do at your end.
Version 2.448.0
November 13, 2026Told when your account gains a device
- We are getting ready to email you whenever a new device is added to your account, so you would know at once if it was not you. The email will say only what kind of device it was and when, never anything typed into it, and adding a device never waits for it. It starts when our new sign-in does. Nothing to do at your end.
Version 2.447.7
November 13, 2026One door, for one caller
- Our translation service now answers only the one tool that uses it so far, and we watch its certificate like every other. Another tool that was allowed in ahead of time is not using it yet, so it waits outside until it does. Nothing to do at your end.
Version 2.447.6
November 13, 2026Proven before it was switched on
- Our new translation service is backed up, and the backup has been brought back and checked, before it was switched on. Our most closely fenced machines can only be reached through one of our own, so the first check could not connect; the instructions for those machines now say how. Nothing to do at your end.
Version 2.447.5
November 13, 2026Backed up before it holds anything
- Our new translation service will be backed up, and the backup proven, before it is switched on. Getting ready, we found that our check of a brand-new, empty database could not actually fail, so it would have passed without testing anything. It now tests an empty one properly too. Nothing to do at your end.
Version 2.447.4
November 13, 2026Our own building blocks, without the wait
- Code we wrote ourselves no longer waits three days before we use it, as long as our own build system made it. The wait exists to give the world time to spot a bad release from someone else. For our own, we have already read every line, so we now check instead that it really came from our own build, and anything that did not still waits. Nothing to do at your end.
Version 2.447.3
November 13, 2026Who watches the watcher
- The check that tells us when a backup has stopped arriving now has a watcher of its own. A check that has quietly stopped running looks exactly like one with nothing to report. Now it checks in each time it finishes, and if a day passes without that, we are told. Nothing to do at your end.
Version 2.447.2
November 13, 2026Brought back, and it matched
- The new copy of how our web addresses are set up now runs every night, and we have brought it back and found it matches the real thing exactly. That was the last part of our setup with no copy of its own. Nothing to do at your end.
Version 2.447.1
November 13, 2026A check that failed for the right reason
- The first test of our new copy of how our web addresses are set up failed, and it was right to. The service we copy from stamps each copy with a fresh number every time it is asked, so no two copies could ever match, and our test of the real thing found what our rehearsal had not imitated. Each copy now records that number the same way, and the rehearsal imitates it too. Nothing to do at your end.
Version 2.447.0
November 13, 2026The last part of our setup that had no copy
- We are adding a nightly copy of how our web addresses are set up with the service that answers for them. Until now that setup lived only with that service, so a mistaken change, or losing the account, would have meant rebuilding it from memory. The copy is read with a key that can only read, kept encrypted beside our other backups, and checked by bringing it back and comparing it with the real thing. While testing it, one of our own checks caught a clean-up step that would have emptied the wrong folder if pointed at one; it now looks before it tidies. Nothing to do at your end.