FOI Warfare

Archive: 20 August 2025. Editorial repair: 12 November 2026. A webpage shell in the archive This entry originally contained a complete HTML page rather than an article. It identifies a Form.io application shell, with an empty view container, template variables, stylesheet references and script references. The source is now displayed as text below so its markup does not interfere with the blog. What the capture contains An application named formioApp in the markup. References to loading and configuration states, an authentication footer and application-version placeholders. Relative paths such as hosted.js , scripts.js and config.js . These are source references, not useful links from this Blogger page. What it does not establish The saved shell contains no completed form, submitted answers, receipt or transaction outcome. It does not identify the original hosting URL. It therefore cannot, by itself, show which service was being used or whether a submission succeeded. This is a techni...

Archive: 20 August 2025. Edited on 12 November 2026; original source retained below. “Your request could not be processed” This entry preserves a Queensland Transport and Motoring error page. Its useful evidence is the message presented to the person trying to use the service: Your request could not be processed at this time. This may be due to an expired session. What the message tells us The page reports a processing failure and suggests an expired session as a possible explanation. It does not identify the request, confirm the cause, or record a successful submission. The original capture directs the reader to an online-services help page and a business-hours phone number. Why keep a failed page? A failed page is part of the access record too. Keeping the exact wording makes it possible to distinguish the failure that was shown from later explanations of what caused it. No finding of deliberate blocking can be made from this capture alone. Archive repair The original included a comp...