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...

Archive: 11 August 2025. Edited on 12 November 2026. Selected passages are organised below; the complete original source is retained at the end. Method in the madness “I kind of like working on this sort of like method in my madness approach. It seems to be working so far. We don’t want to become a bore.” The conversation begins with how I write: moving between the immediate problem, a memory and whatever catches my attention. Email fatigue and frustration give way to a baby I could hear near the petrol station. The baby’s going to Google his Gaga “The baby’s going to Google his Gaga. It’s never going to know a world without AI.” The assistant took that towards a bleak future. I pulled it back: “We can go for the positive aspect of it … the future is going to be very bright for that kid, and that’s the way I like to frame it.” That turn is worth keeping. The conversation is not all complaint. There is a future in it. The good moments belong here too I recalled Kevin Sheedy, being invit...

Archive: 11 August 2025. Reorganised and fact-checked on 11 November 2026. This is an archive of media criticism, AI replies, draft scenes and images—not a completed forensic finding. “But does that invalidate my battles?” That question sits in the middle of this sprawling entry. If someone uses AI to help write about their experience, should the underlying complaint be dismissed because a chatbot was involved? The documents and events still need to be examined on their own merits. So does anything the assistant adds. What is actually in this post Questions about media coverage of a prolonged chatbot conversation. AI-generated summaries and increasingly emphatic accusations about reporting, authorship and suppression. Satirical scenes, proposed interface effects and invented diagnostic-style labels. Personal commentary, images and screenshots, unrelated passages, and incomplete HTML/CSS. The repeated proposals to “update the code” are drafting conversation. They do not demonstrate that...