In His Name, the Most High
Changelog — 2.395–2.402
Releases 395.0 through 402.0. Current releases are on the main changelog, and every band is listed in the release archive.
Loading audio...
Version 2.402.0
October 21, 2026Our own sign-in, built and waiting
- The new way of signing in to this site is built, and switched off. It checks every sign-in for itself rather than taking another system's word, connects each person to their existing account only when their email is proven, and never creates a duplicate. It goes on to our test site first, when our account service is ready. Signing in here works exactly as before. Nothing to do at your end.
Version 2.401.1
October 21, 2026Testing it the way it will really run
- We test our new sign-in on our test site as closely as we can to how it will run for real, and we have written down the few places where the two cannot be the same, so that each one is checked on purpose before the change reaches this site. Testing this way has already found one gap, now being fixed. Nothing on the site changes. Nothing to do at your end.
Version 2.401.0
October 21, 2026Laying the groundwork for our own sign-in
- We have added the places our new sign-in will keep its records, such as which account belongs to whom and which sessions are still open. Nothing uses them yet, and signing in works exactly as before. Nothing to do at your end.
Version 2.400.3
October 21, 2026A plan for signing in to this site with our own accounts
- We have written down how signing in to this site will move to our own account service,so that the people who write here keep their work and their access when it does. We will try it on our test site first. Nothing on the site changes yet. Nothing to do at your end.
Version 2.400.2
October 21, 2026The test version of our account service has its address
- Our team can now reach the test version of our new account service, its sign-in page behind the same protection as our public sites and with a limit on how fast anyone can try to sign in, and its admin pages for our team only. We checked each of those from outside before calling it done. Nothing on this site changes. Nothing to do at your end.
Version 2.400.1
October 21, 2026Our own safety check stopped us, correctly
- The careful steps we prepared yesterday check everything before changing anything,and this morning one of those checks refused to go on because it had asked a slightly wrong question. Nothing had been changed. We have corrected the question. Nothing on the site changes. Nothing to do at your end.
Version 2.400.0
October 21, 2026Getting ready to open the door of our new account service
- Our new account service is nearly ready to be tried by our own team, and we have prepared the careful, checked steps that will give its test version a public address. Its sign-in page is reached only through the protection that already sits in front of our sites, and its admin pages only by our team. Nothing on this site changes. Nothing to do at your end.
Version 2.399.3
October 20, 2026Writing down the steps while they are fresh
- Connecting a new machine safely to our private network has several steps that must happen in order, and tonight we missed one of them before our own checks caught it. We have written the whole sequence down, including the step we missed, so the next machine starts from the full list. Nothing on the site changes. Nothing to do at your end.
Version 2.399.2
October 20, 2026A locked door we forgot to open, and it stayed locked
- Our new account service's machines are walled so they can only make the connections we list, and the one that joins them to our private network was not on the list. When we joined them this evening, the connection was refused, our own check noticed within a minute and put everything back as it was. We have added that one connection to the list. Nothing on the site changes. Nothing to do at your end.
Version 2.399.1
October 20, 2026New machines can be set up to talk only to what they need
- Behind the scenes, the way we connect a new machine to our private network can now limit it to the one connection it needs, so it can neither reach nor be reached by our other machines. Nothing on the site changes. Nothing to do at your end.
Version 2.399.0
October 20, 2026Our own machines will keep to their own lanes
- Behind the scenes, we found that some of our machines could reach each other more freely than they need to, and we have built a careful way to close that. First we watch, for a day, what would be affected, so that nothing which relies on it breaks; then we close it. Nothing on the site changes. Nothing to do at your end.
Version 2.398.5
October 20, 2026Our records kept up to date
- Behind the scenes, our internal records now say that the smaller request record described in 2.398.0 is in place, and how we checked it. Nothing on the site changes. Nothing to do at your end.
Version 2.398.4
October 20, 2026Our own check stopped us, and found a second record to tidy
- Behind the scenes, before changing what our request record keeps (2.398.0), our check found that a request which goes wrong is written down a second time, in a separate record, with the same details. It stopped before changing anything. That second record now leaves out the same details as the first. Prayer times still use your approximate location exactly as before. Nothing to do at your end.
Version 2.398.3
October 20, 2026Two of our own checks made more patient and more careful
- Behind the scenes, a check we ran this morning reported a failure that was only a delay:one service took a few seconds longer than we allowed to pick up its renewed certificate. The check now waits long enough, and only reports a real failure. A second test of ours can now run alongside another copy of itself without the two interfering. Nothing on the site changes. Nothing to do at your end.
Version 2.398.2
October 20, 2026Our certificate warning now watches the new service as it runs
- Behind the scenes, our new account service is now running on its test machines, and our certificate warning checks what each part of it actually presents, not only the file on disk. We also gave ourselves a careful way to renew those certificates early, to prove the service picks up a new one without a restart. Nothing on the site changes. Nothing to do at your end.
Version 2.398.1
October 20, 2026Releases name exactly what was tested
- Behind the scenes, naming a release could quietly wrap the tested build in a new package,which our own release check then refused, correctly. We found it on one of our newer services this morning. The naming step now copies the tested build exactly, and a new test proves it. Nothing on the site changes. Nothing to do at your end.
Version 2.398.0
October 20, 2026Our records of each visit now keep less about you
- Our servers keep a short record of each request, and it was keeping more than it needed: the approximate location our network provider attaches to a visit, and, for the few of us who sign in to our test sites, our sign-in details. We found it while checking a question about search. Those details are no longer written down, and the record itself is kept only for a short time.
- Prayer times still use your approximate location, exactly as before: only the record changed, not what the site receives. Nothing to do at your end.
Version 2.397.0
October 19, 2026Ready for our new account service
- Behind the scenes, we can now give a new set of machines their certificates safely, and our certificate warning watches them from the moment they have one. This prepares for the account service we are building. Nothing on the site changes. Nothing to do at your end.
Version 2.396.1
October 19, 2026Our records kept up to date
- Behind the scenes, our internal records now include a connection set up today between two of our research tools. Nothing on the site changes. Nothing to do at your end.
Version 2.396.0
October 19, 2026The warning now checks what is really in use
- The certificate warning we added earlier today looked at the saved copy of each certificate, not the one actually in use. Those can differ if a renewed certificate is never picked up, which is exactly the problem the warning is for. It now checks both, and warns if they still differ a day after a renewal. Nothing on the site changes. Nothing to do at your end.
Version 2.395.0
October 19, 2026A warning before a certificate runs out
- Our team's certificate warning now also watches certificates that our machines renew for themselves, so if a renewal keeps failing, someone is told weeks before anything stops working, rather than finding out when it does. Nothing on the site changes. Nothing to do at your end.