In His Name, the Most High
Changelog — 2.403–2.418
Releases 403.0 through 418.5. Current releases are on the main changelog, and every band is listed in the release archive.
Loading audio...
Version 2.418.5
October 27, 2026Planning one search engine for our research tools
- We wrote down how our research tools could share one search engine, before building anything. Each tool keeps its own rules for matching Arabic and Persian spellings, so a search finds what it found before, and the plan asks that nothing you search for is ever kept. The tools’ own teams read it next. Nothing to do at your end.
Version 2.418.4
October 26, 2026Practising for things going wrong, safely
- We added a careful way to rehearse a fault on the new account service’s test machines: one machine is cut off from the others for a few minutes, so we can watch the rest carry on without it. The cut always ends by itself, even if we cannot reach the machine. Our own first check of it found two mistakes before it was ever used, and both are fixed. Nothing to do at your end.
Version 2.418.3
October 26, 2026Our second try of the new sign-in found two more faults
- Confirming it was you could send you round in a circle. After you confirmed, part of the site was still remembering, for a few seconds, that you had not, and asked again. Every part of the site now works from one memory, and nothing it remembered from before you signed in is used afterwards.
- The “Confirm it is me” button could fail with an error. A setting meant to keep other sites from learning which of our pages you came from also stopped some of our own forms working. Other sites still learn nothing; our own forms work again. This is on the test site only so far, and there is nothing to do at your end.
Version 2.418.2
October 26, 2026The older copies are gone, and a check that did not check is fixed
- The older copies of our front door’s records, which still held search words, are removed, and the records it keeps now stay for about two days. We checked the result directly afterwards. One of our own checks during that work could not read what it was counting and passed anyway; the work was right, the check was not, and it is now fixed so that it cannot pass that way again. Nothing to do at your end.
Version 2.418.1
October 26, 2026Search words are no longer recorded; one check was too strict
- Our front door now records no search words, no address details and no internal credential, checked before and after the change. The next step, removing the older copies, stopped itself because its check counted a line it should not have; nothing was lost, and the check now counts only what it means to. Nothing to do at your end.
Version 2.418.0
October 26, 2026One account, a step closer, and editing pages kept out of the offline copy
- The pages our writers and editors use are no longer saved in the browser’s offline copy. They hold other people’s details, and a saved copy could be shown on that device after signing out.
- Signing in with one account of our own, at account.tpcloud.solutions, is being tested. The first trial found three things to fix, and they are fixed: in the trial, signing in now goes straight to that account, and signing out signs you out there as well. Readers do not need an account. Nothing to do at your end.
Version 2.417.4
October 26, 2026One more place search words were kept, and a safety check that stopped us, rightly
- Search words can also travel inside a page that sends you somewhere else, such as a sign-in page, and our records were keeping them there too. They are now removed from that as well.
- Before changing anything, the tool that removes search words from our records checks that it can see them first, so that its later “they are gone” means something. On one of our sites they were already removed last week, so the check stopped the run before it changed anything. The check now expects that site’s state, and its own tests now start from how things really are. Nothing to do at your end.
Version 2.417.3
October 26, 2026Keeping fewer records of your visits
- The words people search for on our sites should never be recorded, and we found our front door was recording them, along with a credential one of our own tools uses. It was also keeping a second copy of its visit records for about five weeks, and that copy still held things we had stopped recording a week earlier, because last week’s fix only changed what was written from then on. We now record no searches and no such credentials, and we are removing the second copy and what it held. Nothing to do at your end.
Version 2.417.2
October 26, 2026Writing down what we changed today
- Our records now describe today’s changes to how our research tools reach one another, and one detail we measured about how our backup storage protects each copy. Each was read back from the machines before it was written down, and one older line that had fallen out of date was corrected. Nothing to do at your end.
Version 2.417.1
October 26, 2026A short-lived test bench for faster search
- Our research tool’s library is about to grow sharply, so we have set up a temporary, sealed-off test machine to measure whether software built only for searching would serve it better than what it uses today. It can read the material it needs and nothing else, and it will be removed once the measurements are written up. Nothing changes for anyone until the numbers are in. Nothing to do at your end.
Version 2.417.0
October 26, 2026Backups that keep themselves, and cannot be cut short
- Our research tool’s backups now go into storage that protects each copy for a fixed time on its own: hourly copies for two days, daily for a week, weekly for four weeks and monthly for a year. The program that writes them is not allowed to shorten that time or delete a copy, so a mistake or a stolen key should not be able to wipe them. Our first attempt asked the writer to set the time itself, which would have needed exactly the power we want it never to have; this way it does not. Nothing to do at your end.
Version 2.416.0
October 25, 2026Getting ready for one account across our services
- When the site moves to our own account service, it will check every quarter of an hour that your sign-in there is still valid, so signing out there, or having access changed, reaches this site within minutes even if the message telling us about it went astray. If the account service is briefly unreachable, you stay signed in. This is not switched on yet. Nothing to do at your end.
Version 2.415.1
October 25, 2026Our fonts now come from us
- The site’s two typefaces are now served entirely from our own site, the way the scripture reader’s already were. A change at the font provider briefly stopped us building the site; that can no longer happen. The page looks exactly as it did. Nothing to do at your end.
Version 2.415.0
October 25, 2026Short-lived passes, and a machine we no longer need, gone
- A team member’s own computer now reaches our systems with a pass that lasts less than a day and renews itself, instead of a key that never expires. The secret half never leaves that computer, and the pass can only ever do ordinary work, never administration. We proved it works on its own before relying on it. Nothing to do at your end.
- We retired the isolated test machines built for recovering books from an old disc collection. We will fetch those books from the publisher’s own website instead, with permission, so we can see each change as it happens. Their copies and backups are gone too, so nothing is left behind. Nothing to do at your end.
Version 2.414.1
October 24, 2026Our search can no longer change quietly under us
- The models behind our passage search, which also grounds Reflections and Vignettes, are now held to the exact versions we tested, and are checked against answers we recorded from them. Until now a routine restart could have picked up a newer version without anyone noticing, and search would have quietly got worse while every check stayed green. Nothing to do at your end.
Version 2.414.0
October 24, 2026We will now notice when backups stop arriving
- The admin dashboard now warns us when any system’s backups stop reaching our protected storage, even when the system itself has stopped and cannot say so. It also warns when it cannot check at all, rather than staying quiet. Nothing to do at your end.
Version 2.413.0
October 24, 2026The address book's backup gets an off-site copy too
- The backup of the system that tells our machines how to find each other can now be sent to the same protected storage as our database backups, using the same, single piece of code, so the two cannot drift apart. We tested it, including what happens when sending fails, before switching it on anywhere. Nothing to do at your end.
Version 2.412.0
October 24, 2026A way to notice backups that stop arriving
- We added a key that can only see which backups have arrived and when, never what is in them. It is the first part of an alert that tells us when a system's backups stop, even if that system has stopped too. We tested what it can and cannot do on a spare copy first. Nothing to do at your end.
Version 2.411.1
October 24, 2026The backup storage is ready on our test systems
- The storage for our database backups now exists on our test systems, where copies are kept for a shorter time than on the live site. We checked what each system may and may not do there before any backup uses it. Nothing to do at your end.
Version 2.411.0
October 23, 2026Each backup now checks how long it will be kept
- Our database backups now go to the storage for their kind, and each one checks, after it is saved, that it will be kept for the right length of time. A backup sent to the wrong place is reported as a failure rather than kept quietly. We tested a full backup and a restore from it on spare copies first. Nothing to do at your end.
Version 2.410.0
October 23, 2026A safer home for database backups, decided by a test
- Before any backup used it, a test showed that our first design would have let a system shorten how long its own backups are kept. So we changed it: each kind of backup now goes to its own storage, which keeps it for a fixed time on its own, and the systems that write backups cannot change that or delete what they wrote. We set this up and tested it on a spare copy first. Nothing to do at your end.
Version 2.409.0
October 23, 2026Database backups that leave the building, locked
- Our nightly database backups can now be encrypted and sent to separate storage, and each one is checked after it arrives. Each backup also records a fingerprint of every table, so a restore can be checked against it table by table. We tested a full restore this way, with changes still being written while the backup ran. It is switched on one system at a time over the coming weeks. Nothing to do at your end.
Version 2.408.5
October 23, 2026The shared code for backups is ready
- The shared piece of code that our systems will use to put their backups away, and to prove each copy afterwards, now has its first release, built and checked by our own build system. This release updates our notes on how such shared code is published and used. Nothing to do at your end.
Version 2.408.4
October 23, 2026One way to store a backup
- We have started one shared piece of code that every one of our systems will use to put its backups away and to prove each copy afterwards, rather than each system doing it its own way. This release only records it in our notes. Nothing to do at your end.
Version 2.408.3
October 23, 2026Saying what our backups do, accurately
- Our internal notes said some backups were already kept away from our premises. They were not: they were kept twice, in the same place. We corrected the notes, and the work to keep a copy elsewhere is under way. Nothing to do at your end.
Version 2.408.2
October 23, 2026Backing up the address book
- We wrote and tested the nightly backup of the system that lets our services find each other, kept only in encrypted form. It is not switched on yet; that comes once the place it uploads to is ready. Nothing to do at your end.
Version 2.408.1
October 23, 2026A safe place for one more kind of backup
- We prepared a home for the encrypted copies of one of our research tool's account records, each kept only as long as it is useful and then removed by itself. Part of our work this autumn to keep proper, tested backups of everything. Nothing to do at your end.
Version 2.408.0
October 23, 2026Your work stays put while you confirm it is you
- If a save arrives just after your 12 hours are up, your work is kept in your browser, and a note says so. Confirm it is you in a new tab, come back, and press Save again. This covers the Reflection, Vignette, Dispatch and Event editors on our test site. Nothing to do at your end.
Version 2.407.0
October 23, 2026Confirming it is you, every 12 hours
- On our test site, the people who can change the site now confirm it is them every 12 hours, with a passkey or the way they usually sign in, and carry on where they were. A little before the 12 hours are up we offer it once, so nobody is stopped in the middle of something. We also found and fixed a gap before it reached the live site: signing in again could count as confirming without actually doing so. How you sign in to the live site has not changed. Nothing to do at your end.
- When your account changes at our new account service, the test site now catches up by itself the next time you open a page, without asking you anything. Nothing to do at your end.
Version 2.406.0
October 22, 2026Hearing when you sign out elsewhere
- Our test site can now be told when someone signs out, or loses access, at our new account service, and ends their session here too, rather than waiting for it to run out. A message that is not genuinely from the account service is refused and changes nothing. This is still preparation: how you sign in to this site has not changed. Nothing to do at your end.
Version 2.405.2
October 22, 2026Our own code, checked in the right place
- Before each release we check every outside library the site uses. That check now looks up our own shared code on our own shelf, rather than asking a public one that has never heard of it, and holds it to the same waiting rule as everything else. Nothing to do at your end.
Version 2.405.1
October 22, 2026Switched off now means switched off
- When a team member's access to one of our internal tools was switched off, their devices could stay connected to it, and the same was true when an account was suspended. Our own note in the code said the opposite, and nothing checked it. Both now end the connection, and a test fails if that ever slips. This affects team tools only, not the public site. Nothing to do at your end.
Version 2.405.0
October 22, 2026Our own shelf for shared code
- The site now takes the code it shares with our other services from our own private shelf, rather than from a copy pasted in by hand. Each piece comes in at one exact version, and the site checks its fingerprint every time it is built, so nothing can change underneath it without someone reading the change first. This is preparation for the new sign-in: how you sign in has not changed. Nothing to do at your end.
Version 2.404.2
October 22, 2026A narrow door, tested before it is fitted
- We have written, and tested, the one narrow exception our test site will need so that our account service can tell it when someone signs out. Everything else stays behind the same lock as before. It is not switched on yet, and it refuses to be switched on until the part of the site it protects exists. Nothing to do at your end.
Version 2.404.1
October 22, 2026A private road, checked
- Our test site now talks to our account service over our own private connection rather than the open internet, and we have a check that proves it does, and that the other end is who it says it is. This is preparation only: how you sign in has not changed. Nothing to do at your end.
Version 2.404.0
October 22, 2026Getting signing in ready for our own accounts
- When this site moves to our own account service, a session here will end soon after it ends there, and the people who edit the site will be signed in for at most twelve hours at a time. This release lays the groundwork. How you sign in today has not changed, and won't until we tell you, well ahead of time. Nothing to do at your end.
- A message from our account service can only take access away, never give more. We check that here rather than trusting it, so a message that tried to raise someone's access would be ignored and recorded.
Version 2.403.3
October 21, 2026An open question, answered by testing
- A detail of how this site will prove who it is to our account service was an open question yesterday. It was settled today by testing the real service rather than reading about it, and our notes now say so. Nothing changes on the site. Nothing to do at your end.
Version 2.403.2
October 21, 2026Each machine keeps to itself
- The machines behind our sites can no longer talk to each other through our private network,only to the one point that serves you. We watched for a day first to be sure nothing relied on it, then closed it, and checked from one of the machines that the door really is shut. Nothing on the site changes. Nothing to do at your end.
Version 2.403.1
October 21, 2026Saying it once
- A list in the admin pages showed some people's email address twice in a row. It now shows it once. Nothing to do at your end.
Version 2.403.0
October 21, 2026No duplicate accounts, by design
- When someone signs in with our new account service and we cannot match them to their account here, we no longer guess. An administrator connects them to their existing account, or creates a new one, and the admin pages now show who is waiting. Signing in here works exactly as before. Nothing to do at your end.