Crimson Reason

A site devoted mostly to everything related to Information Technology under the sun - among other things.

Tuesday, April 22, 2025

Using ChatGPT: Who Poisoned Cardinal Wolsey?

 


Could Cardinal Wolsey Have Been Poisoned? A Historical Medical Inquiry

Introduction

The death of Cardinal Thomas Wolsey on 29 November 1530 has traditionally been attributed to natural causes—specifically dysentery. However, his rapid and suspicious decline, occurring while in royal custody and just before he could stand trial for treason, has prompted historians and medical scholars alike to question whether he might have been deliberately poisoned. Given the high political stakes surrounding Wolsey, the possibility is worth closer scrutiny.

Medical Analysis of Wolsey’s Final Illness

Historical sources recount that Wolsey became seriously ill at Sheffield Castle, suffering from what was diagnosed as dysentery—characterized by diarrhea, dehydration, and severe weakness (Guy, 1990). Over the following two weeks, his condition deteriorated further, with reports of failing visionloss of consciousness, and inability to walk, culminating in his death at Leicester Abbey.

While these symptoms are consistent with natural infectious disease and its complications, they could also indicate acute or subacute poisoning. The presence of neurological symptoms, rapid decline, and suspicious timing all raise the specter of toxicological intervention.

Poisons That Could Mimic Dysentery

  • Arsenic: A highly plausible agent, arsenic was well-known, odorless, and tasteless. It causes vomiting, diarrhea, weakness, neurological impairment, and death. Slow administration over several days could mimic natural illness (Nriagu, 1983).

  • Antimony: Used medicinally at the time but highly toxic in larger doses. It induces vomiting, diarrhea, cardiac issues, and systemic collapse (Kafarski, 2019).

  • Aconite and other botanical poisons can also produce symptoms of gastrointestinal and neurological distress, though their onset is typically faster.

Given these possibilities, determining who had both access and motive becomes central to evaluating whether Wolsey was poisoned—and by whom.


Political Motive and Opportunity

Wolsey's political downfall made him a liability. Once Henry VIII had decided to remove him, Wolsey's very survival posed a threat to the king’s repute, as he was rumored to hold damaging secrets. A public trial might have unearthed uncomfortable truths. Eliminating Wolsey quietly served multiple interests—particularly those of the king and his rising courtiers, such as Thomas Cromwell and the Duke of Norfolk.


Ranking of Potential Accomplices by Likelihood of Involvement

During his final days, Wolsey stayed in the homes of three principal men:

1. Sir William Kingston – Most Likely

  • Role: Constable of the Tower of London; responsible for escorting Wolsey to London.

  • Argument: Kingston was directly appointed by the Crown, and had full authority over Wolsey from 25 November onward. He was in the closest proximity to Wolsey during the final and most critical days, including the stop at Hardwick Hall, the night in Nottingham, and finally Leicester Abbey. His men reportedly wept at Wolsey’s condition (Guy, 1990), which could be interpreted as genuine grief—or guilt.

  • Motive: Loyalty to the Crown, whose interest was in a quiet resolution. Kingston was a high-level agent and would not likely act independently but could easily carry out covert royal orders.

2. George Talbot, 4th Earl of Shrewsbury – Possible

  • Role: Hosted Wolsey for 14 days at Sheffield Castle, where he first fell seriously ill.

  • Argument: Talbot was a senior nobleman with extensive estates and connections. While he showed apparent loyalty and hospitality to Wolsey, it is during his stay at Sheffield Castle that Wolsey’s symptoms first emerged.

  • Motive: Mixed. Talbot had little to gain personally from Wolsey’s death but may have acted out of fear or obligation if he had received quiet pressure from the court. However, his family did not benefit directly from Wolsey’s removal, and there is no evidence of personal animosity.

  • Likelihood: Moderate. He may have unknowingly allowed poison to be administered under his roof, possibly by a planted servant.

3. The Monastic Hosts at Pomfret Abbey and Leicester Abbey – Unlikely

  • Argument: Both stops were short (Pomfret: 1 night; Leicester: 1–2 days). Monks provided shelter but were not politically aligned actors, and there is no evidence of direct royal influence or pressure on them. By the time Wolsey arrived at Leicester Abbey, he was already severely ill and near death.

  • Likelihood: Very low. It’s improbable that poisoning occurred this late in his decline or that monastic hosts were involved.


Conclusion: Natural Illness or Calculated Elimination?

Though dysentery was a common and deadly illness in Tudor England, the consistency of Wolsey’s symptoms with known poisons, the timing of his decline, and the political benefits of his sudden death make the theory of poisoning plausible.

Sir William Kingston, as the Crown’s direct agent and Wolsey’s final custodian, ranks highest in likelihood of complicity. George Talbot is a possible but less likely accomplice, while the monastic hosts are nearly beyond suspicion. Without forensic evidence, certainty is elusive, but the case for poisoning remains historically credible—if not proven.


Works Cited

  • Guy, John. Cardinal Wolsey: A Life in Renaissance Europe. Oxford University Press, 1990.

  • Nriagu, Jerome O. "Arsenic and Old Laws: The History of Poisoning and Public Health." Arsenic in the Environment, Wiley, 1983.

  • Kafarski, Pawel. “Antimony: A Medicinal Metal That’s Poisonous.” Chemistry Today, vol. 37, no. 3, 2019.

  • Loades, David. The Tudor Court. Batsford, 1986.

  • Ives, Eric. The Life and Death of Anne Boleyn. Blackwell, 2004.



Saturday, April 19, 2025

Making AI-generated Code More Accurate

https://news.mit.edu/2025/making-ai-generated-code-more-accurate-0418

Robots vs Humans - Half Marathon

From BBC


Oscar Pistorius, of South Africa, asked to take part, but the organisers in China said no. In an official communiqué, they explained: "Being a robot or being a human being is binary. You are a robot or you are not. If you were born a human being, you cannot, as things stand, become a robot. This race was only open to biologically born humanoid machines, and Oscar Pistorius is, in this respect, a trans creature, part-human, part-robot, who does not qualify. If he were allowed to compete with robots, he would win every time, which would not be fair on the robots. Oscar Pistorius is not biologically robotic." 

One of the robots, called Pee-Wee X89yrzx34/Blok***PPPUZ/%@7797opy7BS/8 - commonly known as Pee-Wee - who finished 38th in the robot race, commented: "Beep. Beep. Blink. Burp. Ding dong, ding dong. Dump. Burp. Error message. Error. Mess. Dump. Fart. Data. Retrieve. Data. Beep. Bing. Bong. Bingo. 0. 1. 0. 1. 0. 1. Beep. Blip! Blip! Blip! Beep! Tinkle! Blip! Blip!..." 

___________

Some robots completed the race, while others struggled from the beginning. One robot fell at the starting line and lay flat for several minutes before getting up and taking off. [Lack of training and lack of motivation.] 

____________________________________





Robotic Fruit Picker

https://interestingengineering.com/innovation/japan-builds-strawbeery-picking-robot

Monday, March 17, 2025

Flaws in Smartphone Face-recognition Software [Tech News]

From British consumer magazine WHICH

The problem with face-recognition: apparently, with some smartphones, holding an ordinary photograph up to the phone can unlock it, if I understand correctly. I suppose this means that the person stealing your mobile phone from you knows you, as they would need to have the photo in the first place. 

I have avoided activating the face-recognition functionality on my smartphone (which is a basic Samsung) because I was wondering what you do if it doesn't work: the software has not been updated, or the place where you are is too dark and the phone cannot 'see' you, and so on. 

The Extract below. The article may be behind a pay wall. 

____________________________

In 2023, we revealed that over 40% of phones we tested had face recognition security that could be easily fooled and successfully unlocked by a 2D printed photograph. These included popular handsets from Samsung, Motorola, Xiaomi and others. Unfortunately the issue isn't going away and we were surprised that the same issue affects two phones in the Samsung Galaxy S24 series, and all phones in the S25 series. 

Fortunately, Samsung offers a clear warning during the face recognition set up that tells users the system can be fooled with a photograph. But to avoid this vulnerability, we recommend you don't enable the feature and use the fingerprint sensor or a password/PIN instead. Long PINS are generally more secure (six characters), and if you can set up a password, use a mixture of different characters so it's harder to guess. We recommend setting up protections on your apps that contain sensitive information too – this could involve logging out when you're not using them, or setting up passwords or fingerprint locks.

We approached Samsung for comment on our findings about face recognition on the Samsung Galaxy S24 and Galaxy S24+ in 2024. It said: 'We provide various levels of biometric authentication, with the highest level of authentication from the fingerprint reader. In addition, we provide users with multiple options to unlock their smartphones through both biometric security methods, and convenient options such as swipe or facial recognition. Further information about facial recognition can be found via the settings on Samsung Galaxy smartphones.'

https://www.which.co.uk/news/article/great-alternatives-to-the-samsung-galaxy-s25-that-can-save-you-money-alJca9h6J0C1?utm_source=ExactTarget&utm_medium=Email&utm_campaign=4564291-C_WS_EM_PROD_C__20250228&mi_u=220092277&mi_ecmp=C_WS_EM_PROD_C__20250228

Monday, March 10, 2025

Conflict & Reconciliation Feature for Social Networks - A Proposal

 Subject Matter & Problem

In the course of interactions among human beings, there arises, perhaps inadvertently and perhaps otherwise, that one or more parties take offense or are made angry by the utterances or behavior of another party or parties.  Human societies, historically, have developed mechanism to cope with social friction among the members, limit its negative consequences, and to facilitate reconciliation among the affected parties.

Virtual communities and social networks such as Facebook, Google Groups, etc. are novel ways of human interactions and group formation which are based on computer and information technologies.  However, they are not immune to the occurrences of social friction among their members and the attendant issues of anger management and reconciliation among “warring” parties.  Facebook, for example, offers a binary choice between a “Friend” and “Un-Friend”; one may “Un-Friend” a “Friend” if one has been angered – or otherwise disappointed – by that person.   There is no intermediate state between a “Friend” and “Un-Friend” which could distinguish among total strangers in contradistinction to former friends and acquaintances who could, when one’s anger cools, become one’s friends again.

Solution

The gist of this solution is to endow the social networking sites and virtual communities with a feature to mediate and affect a reconciliation among former friends and acquaintances beyond the binary choice of “Friend” and “Un-Friend” and to further facilitate the resolution of the conflict through selected “Intercessors”.

Use Case 1 – Normal Use

  • The user navigates to a screen that contains a list of his contacts.
  • He selects one or more of them and designates them as: “Not on Speaking Terms”, or “Sulking”, or “Furious” or some such phrase (or its equivalent in other languages).  That is, he sets their “Conflict” status.
  • The system updates their profiles accordingly.
  • The system displays the text above and an appropriate icon that indicates that these individuals have been thus designated as being in “Conflict” with this or that user.

This will be visible to all.

This designation is not conceived to be equivalent to “Un-Friend”.

  • The user could further designate a time period for that status: from “Never Expires” to a date and time range (either selectable from a screen widget or entered manually by the user).
  • The user may optionally decide if he wants to block communication from the “Conflict” contacts.
  • The system will notify those contacts of a change in their status.

That communication could be in the form of email, internal communication, text messages, phone calls etc. – together with an appropriate text message.

  • The system will notify others who share the affected contacts with the user and are also in the user’s social network of the “conflict” status change above.
  • When the “Conflict” status time interval expires, the system reverts the status to “Friend”.

 Use Case 2 – User Selected Intercessor Option

  • The user could further designate one or more “Intercessors” for each and any of the affected contacts from among their common contacts.
  • The role of “Intercessor”, should they accept it, would be to try to mediate and resolve the conflict among the affected parties within the stated period of the conflict.
  • This is an option that the user may or may not exercise.
  • The system will query the “Intercessors” through a possible multiplicity of communication channels if they consent to play that role (for conflict resolution and mediation).
  • If the “Intercessor” agrees, the system will notify the user who had initially requested the help of the “Intercessor” as well as the affected “Conflict” contacts.

4.       It is up to the “Intercessor” then to initiate the process of reconciliation.

Use case 3 – User elects to be “Intercessors”

Optionally, any user may elect to be an available as an “Intercessor” in a social network or virtual community.

Use case 4 – System Recommends “Intercessors”

Optionally, the system recommends a list of available “Intercessors” to the user.

Use case 5 – “Conflict” contact looks for an “Intercessors”

Optionally, the system recommends a list of available “Intercessors” to a “Conflict” contact after the system has informed him of the change in his “Conflict” status by another user.

Description

This is envisioned as a software add-on to existing as well as new social networking sites and virtual communities.  The operation of the invention is described in the above use cases.

Advantages

The chief advantage of this invention is that it enables one to retain one's "Friends" in social network even when one is cross with them. To wit, one announces publicly that he is cross with this or that person, others take note of it, and depending on the desire of both sides and their own inclinations could help them reconcile. So one does not necessarily wind up losing one's friend in a network due to a temporary emotional outburst or state of anger.

System Architecture & Design

The architecturally significant components of the system are illustrated below:

 


Possible Modifications

Something analogous to this may be incorporated into email clients – a “conflict” icon or button in which enables a user to designate one or some of his/her contacts as “In Conflict” until further notice.  The email server can then alert the person so designated of the change in his/her status by another user.  Optionally, all members of a person’s social network could be advised of the status.  Furthermore, the email client can expire the status and revert it back to “Friend” at a designated date and time (by the user).  Likewise, the email client or the email server could, for the duration, junk or otherwise archive email messages from such users.

 This invention could be extended to text messaging systems as well and with a suitable emoji.

 

About Me

My photo
I had been a senior software developer working for HP and GM. I am interested in intelligent and scientific computing. I am passionate about computers as enablers for human imagination. The contents of this site are not in any way, shape, or form endorsed, approved, or otherwise authorized by HP, its subsidiaries, or its officers and shareholders.

Blog Archive