An American cancer patient and Trump supporter was confronted by British police and told to apologise for her online posts or face an investigation.

Deborah Anderson, a mother of two, was visited at her home in June by an officer from Thames Valley Police. He told her someone had lodged a complaint about her social media posts. She told him she was an American citizen and a member of the Free Speech Union and he should be investigating burglaries and rapes, not hurty words on social media.

Chillingly, he told her he was there to get her to apologise to the person who was offended by her posts. If she refused, she’d be questioned down at the station.

What was Deborah’s supposed crime? The policeman didn’t tell her. Was it her passionate support of President Trump and the MAGA movement on her Facebook and X pages?

To make it worse, Deborah is in the midst of cancer treatment, including chemotherapy. She ought to be have been convalescing. Instead, she was harassed for her tweets.

The FSU took on her case and, as a result, the police have now dropped their investigation. But they still haven’t told Deborah which of her posts got her into trouble, claiming they’ve accidentally deleted the record of the complaint.

Thames Valley Police are responsible for guarding President Trump this week. What would he make of the fact that those same officers are visiting the homes of his supporters – including US citizens – and threatening them with arrest.

September 12, 2025

Configuration of Websphere and IBM MQ is taking longer than expected. We are moving all provisioning, build, and deploy stages for all repos from Ansible and Gitlab CI to Dockerfiles and docker compose files, which is a step that precedes running these containers as StatefulSets on Kubernetes. So far, we have functional containers for IBM MQ, Websphere, DB2, MariaDB, and all BOINC endpoints up and running, and what we are still struggling through is configuration.

This approach will benefit site reliability and scalability in an obvious way on Kubernetes, and will improve our development and QA lifecycles drastically. It was also necessary to preserve a maximum compatibility with the CentOS 7 virtual machines that the legacy stack was previously running on, a requirement for the redirected restore of the DB2 data for example, https://www.ibm.com/docs/en/db2/11.5.x?topic=restore-performing-redirected-operation.

So why are we not up, and when will we be up? We are debugging the entrypoint scripts for Websphere and IBM MQ containers. Website cannot be brought up until Websphere is up and configured correctly, receiving messages from all MQ sidecars across the stack, sending emails, etc. Each of the databases, the webserver, and the scheduler have to run MQ, and we are still adapting some of the previous mqsc and other runtime configuration for the MQ service to work with this new setup where each important container that requires one gets an MQ sidecar container that uses the Ubuntu 24.04 host VM network.

There is no known link between the interstellar object 3I/ATLAS and any radio signals, though the two share a common point of origin in the Sagittarius constellation. The famous "Wow!" Signal was detected in the 1970s from Sagittarius, and 3I/ATLAS is also traced back to that same region, sparking curiosity and debate about a potential connection, but current scientific consensus holds that 3I/ATLAS is an interstellar comet, not a source of radio signals.

"Why am I in cuffs because of something he shared, then I shared?"

"Because someone has been caused anxiety based upon your social media post. That's why you've been arrested."