Another lawsuit after a mentally ill person commits murder after chatting with #AI: https://arstechnica.com/tech-policy/2026/06/florida-sues-openai-sam-altman-after-multiple-chatgpt-linked-murders/ #ArtificialIntelligence

@mttaggart
“it's just business” reminds me: in _The Godfather_ when Michael assures his family that he will murder not for revenge, as “it's not personal, just business”. While the film is upsettingly violent, the truth it speaks is: there are *only* personal reasons, even for capitalists.

This #LLM-gen-#AI onslaught is primarily about control. Those who want all this computing to just be an 🏧 seek to *control* the craftspeople.

We should use the tools of the oppressor against the oppressor.

It’s absurd

People are paying for AI tokens to create bot accounts on #Mastodon to post nonsense, increasing the costs for servers, storage and emails all while making the #AI hype even bigger so our servers are gonna costs a lot more

And some wonder why I hate pointless LLMs (AI) so much🤔

Perfectly logically, but perhaps unpredicted by the virtual economy boosters, a range of construction & equipment corporations are seeing a real bump in their share prices as investors realise that.... yup, someone has to actually build all those data centres!

And so, once again (like the cloud) the services & technologies of the information age, are (of course) grounded in physical infrastructure and investors want a bit of that.

#infrastructure #investing #politics #AI #DataCentres

h/t FT

“My Students Can’t Read

The generational collapse in literacy is measurable, persistent, and likely to get worse.”

—> Terrifying article, and it’s not just the USA

https://archive.ph/ZXtQ5

#Education #Literacy #Academia #Universities #AI #SmartPhone #Online #Digital #SocialMedia #Internet

Colleges and universities use document revision history (or lack thereof) as one mechanism to check for AI use in document creation.

More technically adept students use Pandoc, Org-Mode, or LaTeX and a git repo, which has no in-document revision history when converted to an .ODT or .DOCX file.

Is there a way to capture git revision history and merge it into a .DOCX or .ODT file's internal revision history.

Seeking a defense against profs who don't know git.

#askfedi #git #ai #education

Darth Vader, the cyborg. Motorized valves breathe for him. Camera lenses mediate his vision. Blinky lights in his belly remind him and us that he is partially embodied within a machine. His evil is mechanized, impersonal, industrialized.

The machine, the bureaucracy, the state, the corporation.

Even this culture, even this callow amnesiac deracinated superficial illiterate culture, has myths about this.

#ai #fuckai #bigtech #oligarchy

Backlash against the developer of rsync after it emerged he used #AI to generate some of the code in recent versions: https://www.theregister.com/ai-and-ml/2026/06/04/please-do-not-vibe-f-up-this-software-broken-backups-spark-ai-coding-row-in-rsync-project/5251189 #ArtificialIntelligence

”Meta, Spotify, and Google don’t just host AI-generated imagery, ads, and music; they’re also responsible for making the tools that create it. … Allowing users to filter it out regardless would go against all the effort these platforms have undertaken to profit from AI: They want you to embrace the slop factory.”

https://www.theverge.com/ai-artificial-intelligence/942909/let-us-filter-ai-slop-google-youtube-meta-instagram-tiktok

#tech #google #meta #spotify #ai #generativeai #artificialintelligence

@scalzi this is even more ridiculously sad when you consider how awful any of Meta's automation is. Scammers, spammers, and content pirates are rampant on their platform and it truly boggles me how they can't stop the most basic of scams that literally cut and paste the same text to trick unsuspecting people to send money or gift cards to the wrong account.

Their stupid AI automatically tries to help you write better Ad copy when you buy advertising from them. Only once in 3 years have I found their AI rewriting to be even of the slightest use.

Their AI suggestions for how to improve my ads always make everything perform worse.

They are just bad at this and they want more compute so they can scale out how bad they are even more.

#facebook #ai #meta

I've been running Follow the Crypto since 2024. Today I'm relaunching it as Tech Influence Watch, expanded to cover AI political spending alongside crypto. They’ve spent more than $400 million this election cycle, and now you can follow it in close to real time.

https://influence.citationneeded.news/

Here’s the full story behind the Tech Influence Watch launch, including what I found while building it and why it matters now: https://www.citationneeded.news/tech-influence-watch/

#crypto #cryptocurrency #AI #ArtificialIntelligence #USpol #USpolitics #CitationNeededNewsletter

The crypto industry spent $130 million buying the 2024 elections. Over a dozen pro-crypto Congresspeople were installed, and regulatory destruction followed. Now AI is running the same play, with the same strategists and funders. Following only crypto would be telling half the story.

#crypto #cryptocurrency #AI #ArtificialIntelligence #USpol #USpolitics #CitationNeededNewsletter

Crypto and AI companies have also poured $7 billion+ into Trump directly. Afterwards, 21+ SEC cases/investigations against crypto companies were dropped, regulators did a U-turn on crypto policy, and the industry was invited to write their own rules.

https://influence.citationneeded.news/analysis/quidproquo

#crypto #cryptocurrency #AI #ArtificialIntelligence #USpol #USpolitics #CitationNeededNewsletter

Alt...

Featured Tracker Quid pro quo Besides their Congressional election spending, companies have poured billions into Trump and his family. Enforcement cases were dropped, investigations were closed, and industries were invited to write their own regulations. $7.4 billion+ to Trump & family by tracked entities United Arab Emirates $4.3B Advanced AI chips access, 15% stake in TikTok, ... Saudi Arabia $2B F-35 fighter jets agreement Justin Sun and Tron $232.7M SEC case settled, criminal investigation likely ended, ... Andreessen Horowitz $139.9M Four employees installed in White House positions View full tracker →

Most voters have no idea any of this is happening. These PACs run ads about jobs and immigration — never mentioning crypto or AI. 73% of voters disapprove of officials having crypto business ties, but 55% didn't even know Trump is personally involved in the industry (per CoinDesk).

But when voters do find out, the spending can backfire. In Illinois, candidates who called out the crypto money against them won their primaries despite being vastly outspent. Transparency is the only counter to this.

#crypto #cryptocurrency #AI #ArtificialIntelligence #USpol #USpolitics #CitationNeededNewsletter

Alt...

Money involved in this election Raja Krishnamoorthi (D): Raised $31.4M ($57.8k from industry donors), $412k in outside spending to support ($30.2k from crypto PACs), $3.34M in outside spending to oppose Juliana Stratton (D): Raised $4.79M ($1k from industry donors), $9.07M in outside spending to support, $10.4M in outside spending to oppose ($9.99M from crypto PACs) Robin Kelly (D): Raised $3.47M ($2k from industry donors), $1.28M in outside spending to support ($285k from crypto PACs) Dick Durbin (D): Raised $2.38M Don Tracy (R): Raised $2.33M Jeannie Evans (R): Raised $1.28M Casey Chlebek (R): Raised $202k Spending by crypto- and AI-focused committees FairShake (crypto) Total spending $9,866,091 to oppose Juliana Stratton in the primary $9,866,091 Protect Progress (crypto) Total spending $434,834 to oppose Juliana Stratton in the primary $119,643 to support Raja Krishnamoorthi in the primary $30,183 to support Robin Kelly in the primary $285,008

Alt...

Money involved in this election La Shawn Ford (D): Raised $653k, $2.48M in outside spending to oppose ($2.48M from crypto PACs) Anthony Driver Jr. (D): Raised $249k, $564k in outside spending to support Danny Davis (D): Raised $101k Kina Collins (D): Raised $54.9k Chad Koppie (R): Patricia Easley (R): Spending by crypto- and AI-focused committees FairShake (crypto) Total spending $2,475,780 to oppose La Shawn Ford in the primary $2,475,780

The site updates in close to real time from FEC filings. Look up your state, your district, your candidates — particularly if you're in Alabama, California, Georgia, Oklahoma, or South Carolina where primaries are coming up and these super PACs are active.

If you know journalists covering these races, researchers studying tech policy, or voters in targeted districts — send them to the site. Here’s the full launch announcement: https://www.citationneeded.news/tech-influence-watch/

#crypto #cryptocurrency #AI #ArtificialIntelligence #USpol #USpolitics #CitationNeededNewsletter

Hatred of AI

<https://gist.github.com/grahamperrin/ecd4f2b6699f7e228af33b80b0e9b141#file-ai-hatred-md-readme>

#AI

@TheBreadmonkey@beige.party
a series of visual metaphors for what the Asian market drop means. ALT for more context.

https://inv.nadeko.net/watch?v=1IV_flAouGY

#AI

Alt...

A car has lost its rear wheel. This immediately devalues the vehicle and the passengers are now in danger of being injured. The entire video consists of racing cars losing their wheels as a metaphor both for the utility of LLMs to anyone but a small niche, and that the value of each car evaporates the minute it ceases to win races.

Any software license that denies users their #freedom is by definition nonfree and unethical, and so-called "Responsible #AI" Licenses (RAIL) are no exception: https://u.fsf.org/4b3

@hvdsomp

Source:
https://www.newyorker.com/cartoons/daily-cartoon/friday-may-22nd-alien-commencement-address

#Ai #Art #Capitalism #Cartoons #DataCenters #JoeDator #educationworkers #KevinMaher #students

Alt...

Text: “And, as you head out into the world, your fresh, meaty torsos will be ripped apart and roasted to feed your new alien overlords - wait, why are you all booing ?” Art: Joe Dator & Kevin Maher Image graduation students boo the speaker.

#JulieNolke: You love your #algorithm
https://www.youtube.com/watch?v=zQ4_Otz9gXk 😉

#Enshittification on every service that comes with #AI and #AIslurp

Yeah, tracks well #ai

RE: https://mastodon.bsd.cafe/@grahamperrin/116708332410403878

Preparing for a ‘vulnerability patch wave’ | National Cyber Security Centre

https://www.ncsc.gov.uk/blogs/prepare-for-vulnerability-patch-wave

＂Patching alone won’t address the systemic problems that my previous blogs have addressed. I’ve appealed to technology producers and vendors to ensure systemic technical security debt is minimised by including - where appropriate - memory safety and containment technologies such as CHERI and others. …＂

#CHERI #AI #cyberstrategy #CNI

cc @david_chisnall FYI I found this NCSC blog post indirectly via the closing line at <https://www.aisi.gov.uk/blog/our-evaluation-of-claude-mythos-previews-cyber-capabilities>.

Graham Perrin » 🌐 2026-06-07
@grahamperrin@mastodon.bsd.cafe

RE: https://shkspr.mobi/blog/2026/05/gds-weighs-in-on-the-nhss-decision-to-retreat-from-open-source/

AI, open code and vulnerability risk in the public sector - GOV.UK

https://www.gov.uk/guidance/ai-open-code-and-vulnerability-risk-in-the-public-sector

Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.

＂Technology leaders are asking whether AI-accelerated vulnerability discovery means that public sector departments should stop publishing source code ‘in the open’ by default.

User research suggests that the primary driver of exploitation risk is the presence of weaknesses in systems - including unpatched vulnerabilities, insecure implementation, and unsafe configuration or deployment - and the inability to remediate them quickly. Publishing source code does not create those weaknesses, but it can modestly reduce attacker uncertainty and speed up analysis (an effect that may increase with AI assistance), especially where maintenance is weak and fixes are slow. This guidance reinforces the minimum operational capability already assumed for safely operating publicly-accessible services. …＂

#AI #security #vulnerability #discovery #defence #cybersecurity #opensource #LLM #Anthropic #Claude #Mythos #NCST #DSIT #government

Graham Perrin boosted

Terence Eden’s Blog » 🌐 2026-05-17
@blog@shkspr.mobi

GDS weighs in on the NHS's decision to retreat from Open Source

https://shkspr.mobi/blog/2026/05/gds-weighs-in-on-the-nhss-decision-to-retreat-from-open-source/

Within the UK's Civil Service you occasionally hear the expression "being invited to a meeting without biscuits". It implies a rather frosty discussion without any of the polite niceties of a normal meeting

0

. In general though, even when people have severe disagreements, it is rare for tempers to fray. It is even rarer for those internal disagreements to spill over into public.

Which is what makes GDS's latest guidance so surprising. At the start of the month, NHS England made the bizarre and irresponsible decision to close all their Open Source repositories due to unfounded fears of AI hacking

1

. Lots of people within the NHS were outraged. As were many outside - with this petition against the move gathering over 2,000 signatures.

Within other parts of government there was also alarm. Although I no longer work for Government Digital Service, I was contacted by several concerned people there who remembered all my work on Open Source. The brilliant team in Whitechapel have now published their guidance "AI, open code and vulnerability risk in the public sector".

It is brutal.

They utterly repudiate the NHS's stance and forensically eviscerate it. I'll let you read the whole thing, but here are a few choice excerpts:

Recent public reporting about organisations restricting access to public repositories due to AI-enabled code analysis illustrates how quickly leaders may reach for blanket closure in response to uncertainty.

Basically, non-technical managers need to stop over-reacting.

Private repositories can create a false sense of security.

I think that's the crux of the argument. Closing code doesn't solve the underlying problems.

Making code private is not an appropriate mitigation for lack of ownership, patching capability, or operational assurance, so systems that cannot be safely maintained should be remediated or retired.

If you are so concerned about the poor security of your systems, you should shut them down completely to mitigate the threat.

Closure can become a one-way door.

As I said to the BMJ, "nothing lasts longer than a temporary fix".

Where code has been developed in the open, making a repository private later may not remove access for a capable adversary as popular repositories are often mirrored or forked

Indeed. A friend of mine has already archived all of the NHS's repositories. You can see the ones they've tried to hide.

But the killer blow, I think, is this:

Moving code from public to private as a substitute for investment in secure-by-design delivery, ownership and remediation is a warning sign because it reduces sharing and scrutiny, can slow coordinated improvement across government and suppliers, and does not remove the underlying weaknesses in a running service.

Exactly! Coding in the open has been shown time and again to produce high quality and secure work. The looming threat of AI vulnerability scanners doesn't change that - security is a shared responsibility. Technical teams need to be well enough resourced to create secure systems; hiding code is as reliable as papering over structural cracks.

GDS was created was to be a strong centre with vast technology expertise. This was to counter the frankly shoddy approach to tech in other departments. Back then, a Service Assessment was a way for a department to prove that they were actually capable of designing, launching, and managing a complex IT project.

Most departments have become significantly better at the development and running of these sorts of projects, so the raison d'etre of GDS has somewhat waned. Departments feel more confident in running off on their own. Usually I'd celebrate that - it's important that GDS doesn't become a bottleneck and that the talent is distributed throughout the whole Civil Service.

But NHS England has always been a bit of a weird one. One of the reasons NHSX was created

2

was to ensure that the health service had strong expertise in technology and its deployment. As the Head of Open Technology there, I helped craft the policies which embedded Open Source and Open Standards within it

3

.

I don't know what discussions have taken place within NHS England - although I looking forward to receiving a response to my FOI request. It looks to me like a small group within NHS England have received a report showing some potential vulnerabilities discovered by Mythos. Rather than following their own internal guidance, they've over-reacted and slapped a blanket ban on coding in the open.

I fervently hope that this new guidance will encourage DHSC to bring NHS England into line with best practice. If not, perhaps GDS ought to reassert itself as the technical authority with power to veto a department's incomprehensible decisions?

---

1. Of course, all the budget cuts mean that biscuits cannot be purchased for any meetings. Which may explain some of the morale issues within the Civil Service. Thanks Austerity. Thausterity. ↩︎

2. As of today, they've shut down nearly 200 repositories. More may be coming. ↩︎

3. I was there right before the start of NHSX and helped set it up. ↩︎

4. Which, I suppose, is why I'm bitter and angry that all our hard work is being undone. ↩︎

#AI #gds #government #nhs #nhsx #OpenSource

Alt...

Guidance. AI, open code and vulnerability risk in the public sector. Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.

RE: https://shkspr.mobi/blog/2026/05/gds-weighs-in-on-the-nhss-decision-to-retreat-from-open-source/

AI, open code and vulnerability risk in the public sector - GOV.UK

https://www.gov.uk/guidance/ai-open-code-and-vulnerability-risk-in-the-public-sector

Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.

＂Technology leaders are asking whether AI-accelerated vulnerability discovery means that public sector departments should stop publishing source code ‘in the open’ by default.

User research suggests that the primary driver of exploitation risk is the presence of weaknesses in systems - including unpatched vulnerabilities, insecure implementation, and unsafe configuration or deployment - and the inability to remediate them quickly. Publishing source code does not create those weaknesses, but it can modestly reduce attacker uncertainty and speed up analysis (an effect that may increase with AI assistance), especially where maintenance is weak and fixes are slow. This guidance reinforces the minimum operational capability already assumed for safely operating publicly-accessible services. …＂

#AI #security #vulnerability #discovery #defence #cybersecurity #opensource #LLM #Anthropic #Claude #Mythos #NCST #DSIT #government

Graham Perrin boosted

Terence Eden’s Blog » 🌐 2026-05-17
@blog@shkspr.mobi

GDS weighs in on the NHS's decision to retreat from Open Source

https://shkspr.mobi/blog/2026/05/gds-weighs-in-on-the-nhss-decision-to-retreat-from-open-source/

Within the UK's Civil Service you occasionally hear the expression "being invited to a meeting without biscuits". It implies a rather frosty discussion without any of the polite niceties of a normal meeting

0

. In general though, even when people have severe disagreements, it is rare for tempers to fray. It is even rarer for those internal disagreements to spill over into public.

Which is what makes GDS's latest guidance so surprising. At the start of the month, NHS England made the bizarre and irresponsible decision to close all their Open Source repositories due to unfounded fears of AI hacking

1

. Lots of people within the NHS were outraged. As were many outside - with this petition against the move gathering over 2,000 signatures.

Within other parts of government there was also alarm. Although I no longer work for Government Digital Service, I was contacted by several concerned people there who remembered all my work on Open Source. The brilliant team in Whitechapel have now published their guidance "AI, open code and vulnerability risk in the public sector".

It is brutal.

They utterly repudiate the NHS's stance and forensically eviscerate it. I'll let you read the whole thing, but here are a few choice excerpts:

Recent public reporting about organisations restricting access to public repositories due to AI-enabled code analysis illustrates how quickly leaders may reach for blanket closure in response to uncertainty.

Basically, non-technical managers need to stop over-reacting.

Private repositories can create a false sense of security.

I think that's the crux of the argument. Closing code doesn't solve the underlying problems.

Making code private is not an appropriate mitigation for lack of ownership, patching capability, or operational assurance, so systems that cannot be safely maintained should be remediated or retired.

If you are so concerned about the poor security of your systems, you should shut them down completely to mitigate the threat.

Closure can become a one-way door.

As I said to the BMJ, "nothing lasts longer than a temporary fix".

Where code has been developed in the open, making a repository private later may not remove access for a capable adversary as popular repositories are often mirrored or forked

Indeed. A friend of mine has already archived all of the NHS's repositories. You can see the ones they've tried to hide.

But the killer blow, I think, is this:

Moving code from public to private as a substitute for investment in secure-by-design delivery, ownership and remediation is a warning sign because it reduces sharing and scrutiny, can slow coordinated improvement across government and suppliers, and does not remove the underlying weaknesses in a running service.

Exactly! Coding in the open has been shown time and again to produce high quality and secure work. The looming threat of AI vulnerability scanners doesn't change that - security is a shared responsibility. Technical teams need to be well enough resourced to create secure systems; hiding code is as reliable as papering over structural cracks.

GDS was created was to be a strong centre with vast technology expertise. This was to counter the frankly shoddy approach to tech in other departments. Back then, a Service Assessment was a way for a department to prove that they were actually capable of designing, launching, and managing a complex IT project.

Most departments have become significantly better at the development and running of these sorts of projects, so the raison d'etre of GDS has somewhat waned. Departments feel more confident in running off on their own. Usually I'd celebrate that - it's important that GDS doesn't become a bottleneck and that the talent is distributed throughout the whole Civil Service.

But NHS England has always been a bit of a weird one. One of the reasons NHSX was created

2

was to ensure that the health service had strong expertise in technology and its deployment. As the Head of Open Technology there, I helped craft the policies which embedded Open Source and Open Standards within it

3

.

I don't know what discussions have taken place within NHS England - although I looking forward to receiving a response to my FOI request. It looks to me like a small group within NHS England have received a report showing some potential vulnerabilities discovered by Mythos. Rather than following their own internal guidance, they've over-reacted and slapped a blanket ban on coding in the open.

I fervently hope that this new guidance will encourage DHSC to bring NHS England into line with best practice. If not, perhaps GDS ought to reassert itself as the technical authority with power to veto a department's incomprehensible decisions?

---

1. Of course, all the budget cuts mean that biscuits cannot be purchased for any meetings. Which may explain some of the morale issues within the Civil Service. Thanks Austerity. Thausterity. ↩︎

2. As of today, they've shut down nearly 200 repositories. More may be coming. ↩︎

3. I was there right before the start of NHSX and helped set it up. ↩︎

4. Which, I suppose, is why I'm bitter and angry that all our hard work is being undone. ↩︎

#AI #gds #government #nhs #nhsx #OpenSource

Alt...

Guidance. AI, open code and vulnerability risk in the public sector. Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.

GDS weighs in on the NHS's decision to retreat from Open Source

Within the UK's Civil Service you occasionally hear the expression "being invited to a meeting without biscuits". It implies a rather frosty discussion without any of the polite niceties of a normal meeting

0

. In general though, even when people have severe disagreements, it is rare for tempers to fray. It is even rarer for those internal disagreements to spill over into public.

Which is what makes GDS's latest guidance so surprising. At the start of the month, NHS England made the bizarre and irresponsible decision to close all their Open Source repositories due to unfounded fears of AI hacking

1

. Lots of people within the NHS were outraged. As were many outside - with this petition against the move gathering over 2,000 signatures.

Within other parts of government there was also alarm. Although I no longer work for Government Digital Service, I was contacted by several concerned people there who remembered all my work on Open Source. The brilliant team in Whitechapel have now published their guidance "AI, open code and vulnerability risk in the public sector".

It is brutal.

They utterly repudiate the NHS's stance and forensically eviscerate it. I'll let you read the whole thing, but here are a few choice excerpts:

Recent public reporting about organisations restricting access to public repositories due to AI-enabled code analysis illustrates how quickly leaders may reach for blanket closure in response to uncertainty.

Basically, non-technical managers need to stop over-reacting.

Private repositories can create a false sense of security.

I think that's the crux of the argument. Closing code doesn't solve the underlying problems.

Making code private is not an appropriate mitigation for lack of ownership, patching capability, or operational assurance, so systems that cannot be safely maintained should be remediated or retired.

If you are so concerned about the poor security of your systems, you should shut them down completely to mitigate the threat.

Closure can become a one-way door.

As I said to the BMJ, "nothing lasts longer than a temporary fix".

Where code has been developed in the open, making a repository private later may not remove access for a capable adversary as popular repositories are often mirrored or forked

Indeed. A friend of mine has already archived all of the NHS's repositories. You can see the ones they've tried to hide.

But the killer blow, I think, is this:

Moving code from public to private as a substitute for investment in secure-by-design delivery, ownership and remediation is a warning sign because it reduces sharing and scrutiny, can slow coordinated improvement across government and suppliers, and does not remove the underlying weaknesses in a running service.

Exactly! Coding in the open has been shown time and again to produce high quality and secure work. The looming threat of AI vulnerability scanners doesn't change that - security is a shared responsibility. Technical teams need to be well enough resourced to create secure systems; hiding code is as reliable as papering over structural cracks.

GDS was created was to be a strong centre with vast technology expertise. This was to counter the frankly shoddy approach to tech in other departments. Back then, a Service Assessment was a way for a department to prove that they were actually capable of designing, launching, and managing a complex IT project.

Most departments have become significantly better at the development and running of these sorts of projects, so the raison d'etre of GDS has somewhat waned. Departments feel more confident in running off on their own. Usually I'd celebrate that - it's important that GDS doesn't become a bottleneck and that the talent is distributed throughout the whole Civil Service.

But NHS England has always been a bit of a weird one. One of the reasons NHSX was created

2

was to ensure that the health service had strong expertise in technology and its deployment. As the Head of Open Technology there, I helped craft the policies which embedded Open Source and Open Standards within it

3

.

I don't know what discussions have taken place within NHS England - although I looking forward to receiving a response to my FOI request. It looks to me like a small group within NHS England have received a report showing some potential vulnerabilities discovered by Mythos. Rather than following their own internal guidance, they've over-reacted and slapped a blanket ban on coding in the open.

I fervently hope that this new guidance will encourage DHSC to bring NHS England into line with best practice. If not, perhaps GDS ought to reassert itself as the technical authority with power to veto a department's incomprehensible decisions?

1. Of course, all the budget cuts mean that biscuits cannot be purchased for any meetings. Which may explain some of the morale issues within the Civil Service. Thanks Austerity. Thausterity. ↩︎

2. As of today, they've shut down nearly 200 repositories. More may be coming. ↩︎

3. I was there right before the start of NHSX and helped set it up. ↩︎

4. Which, I suppose, is why I'm bitter and angry that all our hard work is being undone. ↩︎

Alt...

Guidance. AI, open code and vulnerability risk in the public sector. Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.

It's Sunday morning in Europe! #archive 8UTC Sunday as always #lispyGopherClimate #podcast since 2022.

https://toobnix.org/w/pU6zu95YDdyGKqsxxRf3Vg #peertube live

#RSS (recent times) https://toobnix.org/feeds/videos.xml?accountId=580185

@vnikolov 's Quality Without A Name toot #AI

As much as I can remember about the #lisp community #architecture and Christopher Alexander https://www.dreamsongs.com/Files/PatternsOfSoftware.pdf https://alexandria.common-lisp.dev/

My NicCLIM #IDE demo and the #DL book I am #writing - loose bibliography and sketch of chapters

#AI #softwareEngineering

Alt...

The lisp alien and gopher fighting in the unix_surrealism corpofoss war arc. LISPY GOPHER SHOW vintage banner recently unearthed.

Is literally *anyone* working on a #FLOSS option?
#android #AI #NoAI

Alt...

Screenshot of Android settings for default assistant with no assistant chosen.

#business #ai #advertising #advertisement

#mechanisation of intellectual tasks:

• slide rule—relieved the burden upon the intellectual by replacing the tedious, error-prone pen-and-paper manipulation of numbers and logarithm tables with a slide-and-cursor mechanism
• calculator—relieved the burden upon the intellectual by replacing the tedious, error-prone manual manipulation of the slide and the cursor of the slide rule with the fully automatic calculator
• computer—relieved the burden upon the human computer by replacing the slide rule and the calculator with the fully automatic digital computer
• web search engine—relieved the burden upon the intellectual by replacing the tedious, error-prone manual library search of print journals and books with the fully automatic web search engine
• automated theorem provers—relieved the burden upon the mathematician by replacing the tedious, error-prone manual re-proofs of previously proven low-level steps with the fully automatic proof checker
• #AI code generator—relieved the programmer of his brain, by replacing once-intellectual tasks with thoughtless, menial button pushes

As tech companies cut back on their employees’ free use of AI code generators, in the face of surging #energy costs, there may well emerge a secondary market in which the so-called “#AI expert” script kiddies trade “tokens” amongst themselves, much like electric power companies trade amongst themselves their federally regulated polluting rights.

There is no AI, just other people's data.

#robot #comic #ai #data #people #noai

Alt...

A comic robot and write around: There is no AI just other people's data.

The Intercept: Philly Cops Admit That They’re Tracking “First Amendment Activity” Critical of AI

A law enforcement document obtained by The Intercept shows police scan social media looking for posts opposing AI data centers.

"...Americans speaking out against artificial intelligence data centers on social media are falling under police surveillance, a confidential law enforcement bulletin obtained by The Intercept reveals.... “Domestic violent extremists (DVEs) are likely interested in targeting artificial intelligence (AI) data centers, posing a physical and cyber threat to infrastructure in the Philadelphia regional area,” the Delaware Valley Intelligence Center wrote in a December alert...."

https://theintercept.com/2026/06/01/ai-data-center-protest-police-surveillance/

#1stamendment #ai #surveillance #bigbrother

lol, has a product launch ever gone as badly?
Everybody hates this shit, fuck off with it!

#AI #GenAI #LLMs #Technology #TechBros #AIHustle #AIBubble

Alt...

Just 10 percent of Americans say they're thrilled about the future of AI, a Pew poll found in March; that same month, some 80 percent of registered U.S. voters in an NBC poll said neither Democrats nor Republicans are doing a good job on the Al front. That number also appears in an April survey of white-collar workers: 80 percent are straight-up refusing to use Al even when it's mandated. In the last 30 days, 54 percent of workers reported bypassing company Al tools and completing jobs themselves.

Pleased to share a page and explainer for the AI tarpit project Science is Poetry, with legal statement, rationale(s), and a few deployment notes:

https://julianoliver.com/projects/science-is-poetry/

The page may grow a bit. Just wanted to get it out the door.

#AI #bigtech

Alt...

Title image for the Science is Poetry project page, featuring the word Counteroffensive followed by auto-generated babble on a purple background.

RE: https://mastodon.green/@gerrymcgovern/116697233926805705

It now occurs to me that the enormous diversion of resources to the construction of AI #datacenters reflects not triumphalism but desperation. If the #LLMs and generative #AI of today worked half as well as their proponents claim they do, would it be necessary to go to these lengths to make them work a little bit better yet?

These people and companies have bet the farm, not on #AI as such, but on a particular resource-heavy approach to #AI. And they're acting like out-of-control "steamers" in a casino — compulsive gamblers betting more and yet more every turn, in a frenzied attempt to win enough to cover their losses.

They're past worrying about whether they can afford it. And most of them (Peter #Thiel, who recently fled to Argentina, may be an exception) are past worrying about how it looks to the rest of us.

But we're still free to observe, and draw our own conclusions. And I suggest that we conclude, not only that these massive AI #datacenters must not be allowed to exist, but also that the kind of massive concentrations of private wealth that built them must not be allowed to exist — not if we value our lives and our freedom. Liquidation of all large accumulations of private capital is not primarily a matter of implementing some philosophical principle of equality. It's a matter of basic self-preservation.

#Luddite

Karl Voit boosted

Gerry McGovern » 🌐 2026-06-05
@gerrymcgovern@mastodon.green

Imagine something that in 2020 didn't really exist but has so exploded onto our environment that in 2030 it will demand the water of 1.3 billion people and the electricity of 2 billion.

In a time when we have a global historic severe drought and when our civilization is about to collapse due to over-consumption of energy.

This is AI.

This is Big Tech

These are the tech bros. Here to burn it all down for greed and ambition.

https://news.un.org/en/story/2026/06/1167658

FreeBSD / src / 56e5998 / loader.efi: Fix when staging moves late - FreshBSD

https://freshbsd.org/freebsd/src/commit/56e59980b673affb82c8c5da9d4338e10d946acd

– an instant cherry-pick from the main branch, before builds began for 15.1-RC3 (the third release candidate).

From the commit log message:

"… This bug hunt was greatly assisted by Claude who looked at the crash from the EFI boot loader and surmised that we weren't jumping to the code we thought we were jumping to. After inspecting the code, I asked claude how corruption could happen (I thought overwriting the page table), but claude notice the possibility that staging might change after we computed the page table, and this fix is the result. Claude didn't suggest a diff, but did provide many helpful clues that lead me to this fix."

Additional context (RC3):

<https://www.reddit.com/r/freebsd/comments/1ty1z0n/comment/oq21krm/>

#AI #Anthropic #Claude #FreeBSD

We present: AI in Schools Bingo.
Next time there's an announcement, play along at home!
#noai #ai #education #edtech #school #bcpoli #canada

Alt...

Five-by-five bingo card. Squares from top-left to bottom-right, row by row are: - "Learn to fact-check" - "Don't want kids to fall behind" - Guest speaker works for AI - Conflates research AI and chatbots - "Thought partner" - "We all use AI" - "But the calculator!" - Mentions safety, guardrails - "Critical thinking skills" - "But {country} is doing it!" - "Training for the workplace" - Doesnt mention mental health - "AI is inevitable" - "Excited to see what students do with it" - "Efficiency" - "AI is the future" - "Coding" - "Keeps students engaged" - "Democratizing creativity" - "Kids use it at home anyway" - "Cognitive offloading" but recommends AI anyway - "Helps with ideas" - "Teach them to use it ethically" - Calls tech from 10 years ago "AI" - Doesn't mention environmental impact

UK media websites given power to block Google using their articles in AI search | Competition and Markets Authority | The Guardian

<https://www.theguardian.com/business/2026/jun/03/uk-media-groups-power-opt-out-google-ai-search-summaries>

New opportunities, control and insights for website owners

https://blog.google/products-and-platforms/products/search/new-controls-website-owners/ | <https://news.ycombinator.com/item?id=48382659> and <https://redd.it/1tvfmjt> (no comment)

#AI #Google #Alphabet

@leftylabourtech

If employers were fooled by the AI™marketing hype, when it's their own money they're losing, imagine how badly our politicians are being filled when it's our money they're rising.

And our lives, jobs and well-being they're risking, on the word of charlatans and snake-oil peddlars.

#AI

RE: https://mastodon.social/@amalia22/116698249960857463

Hustle Alert

"Our wonderful and terrible new product that works so well it could take over the planet like in those movies, (please buy our stock)"

#AI #AIHustle #Anthropic #IPO #AIBubble #TechBros #Technology #LLMs #GenAI