<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://aws.amazon.com/blogs/database/introducing-bulk-put-items-for-amazon-dynamodb-load-data-from-amazon-s3-into-existing-tables-at-scale/?ck_subscriber_id=512829374"/>
	<rdf:li rdf:resource="https://aws.amazon.com/blogs/compute/introducing-queue-consumption-mode-for-apache-kafka-in-aws-lambda/?ck_subscriber_id=512829374"/>
	<rdf:li rdf:resource="https://www.rte.ie/brainstorm/2026/1111/1089533-martinmas-blood-sacrifice-rites-ireland-november-11th/"/>
	<rdf:li rdf:resource="https://hansdekker.dev/writing/fraudulent-aws-accounts-claude-distillation/?ck_subscriber_id=512829374"/>
	<rdf:li rdf:resource="https://terminal2shell.com/"/>
	<rdf:li rdf:resource="https://layer3intel.com/blog/residential-proxies-white-house-network"/>
	<rdf:li rdf:resource="https://seriot.ch/computation/curl.html"/>
	<rdf:li rdf:resource="https://quxnet.net/about"/>
	<rdf:li rdf:resource="https://github.com/lmorchard/linkding-ssg"/>
	<rdf:li rdf:resource="https://www.garbageday.email/p/new-template-test"/>
	<rdf:li rdf:resource="https://hal.science/hal-04629585"/>
	<rdf:li rdf:resource="https://bsky.app/profile/ecmclaughlin.bsky.social/post/3myz65pre5s27"/>
	<rdf:li rdf:resource="https://archive.is/hNDwh#selection-2267.0-2285.134"/>
	<rdf:li rdf:resource="https://lore.kernel.org/linux-xfs/CAF8PYMhboMm+kQnngeZZsmje16qwtyWBzRoqx5J9eKN3NcUbKA@mail.gmail.com/T/#m9ea52dc7be83f0b2a60981c47d45efc56345d816"/>
	<rdf:li rdf:resource="https://www.freetv.ie/cat6-keystone/"/>
	<rdf:li rdf:resource="https://www.somebits.com/weblog/culture/blogs/25th-anniversary.html"/>
	<rdf:li rdf:resource="https://github.com/damontecres/Wholphin"/>
	<rdf:li rdf:resource="https://github.com/mitmproxy/mitmproxy/commit/169234499088fc2c414644a67efaed3d64ae2e3b"/>
	<rdf:li rdf:resource="https://eliastaylor.com/noexploit/"/>
	<rdf:li rdf:resource="https://github.com/Gathin23/cleanyourtv"/>
	<rdf:li rdf:resource="https://citizenlab.ca/research/how-discover-tech-turned-targeted-ads-into-a-pipeline-for-spyware/"/>
	<rdf:li rdf:resource="http://www.fdg2013.org/program/papers/paper06_zagal_etal.pdf"/>
	<rdf:li rdf:resource="https://recursion.wtf/posts/agents-and-property-tests/"/>
	<rdf:li rdf:resource="https://www.theguardian.com/technology/2026/sep/29/trial-live-facial-recognition-cameras-london-stations-false-positive"/>
	<rdf:li rdf:resource="https://mubi.com/en/notebook/posts/pirating-the-pirates"/>
	<rdf:li rdf:resource="https://nelsonslog.wordpress.com/2026/09/26/bbr-proxmox-containers-and-starlink/"/>
	<rdf:li rdf:resource="https://www.motherjones.com/media/2026/09/chatgpt-tumbler-ridge-mass-shooter-openai/"/>
	<rdf:li rdf:resource="https://blog.arusekk.pl/posts/srht-account-takeover/"/>
	<rdf:li rdf:resource="https://abio.substack.com/p/why-ai-assisted-bioweapons-wont-kill"/>
	<rdf:li rdf:resource="https://arxiv.org/abs/2510.20956"/>
	<rdf:li rdf:resource="https://www.technollama.co.uk/v-h-s-scp-when-fandom-meets-law-and-creative-commons"/>
	<rdf:li rdf:resource="https://www.benjoffe.com/fast-day-of-week"/>
	<rdf:li rdf:resource="https://pluralistic.net/2026/09/12/god-in-the-box/#llms-are-fake"/>
	<rdf:li rdf:resource="https://www.patreon.com/richardseymourwtf/posts/kill-all-humans-169276703"/>
	<rdf:li rdf:resource="https://strategictree.bearblog.dev/i-think-i-hate-the-internet/"/>
	<rdf:li rdf:resource="https://www.felonybench.com/"/>
	<rdf:li rdf:resource="https://jyn.dev/a-year-to-fix-security/"/>
	<rdf:li rdf:resource="https://www.nature.com/articles/s41586-026-10098-2"/>
	<rdf:li rdf:resource="https://www.gadgetreview.com/a-decade-of-hype-3000-roofs-and-one-redirect-url-tesla-kills-the-solar-roof"/>
	<rdf:li rdf:resource="https://bergie.iki.fi/blog/eupl/"/>
	<rdf:li rdf:resource="https://insideevs.com/news/806798/ev-battery-aging-study-2026/"/>
	<rdf:li rdf:resource="https://www.patreon.com/violetblue/posts/how-to-migrate-168468176"/>
	<rdf:li rdf:resource="https://shitposting.ai/pickup-incident/"/>
	<rdf:li rdf:resource="https://blog.trailofbits.com/2026/08/26/vms-wont-contain-cyber-capable-agents/"/>
	<rdf:li rdf:resource="https://fzakaria.com/2026/08/23/your-executable-is-a-sqlite-database"/>
	<rdf:li rdf:resource="https://www.githubstatus.com/incidents/zkxwbgr0cnmx"/>
	<rdf:li rdf:resource="https://benngooch.substack.com/p/i-was-an-enthusiastic-early-adopter"/>
	<rdf:li rdf:resource="https://www.theclimatebrink.com/p/the-real-energy-use-of-agentic-ai"/>
	<rdf:li rdf:resource="https://www.abc.net.au/news/2026-08-14/ai-medical-scribe-error-leaves-patient-devastated/107031672"/>
	<rdf:li rdf:resource="https://nltimes.nl/2026/05/22/microsoft-accused-leaking-dutch-civil-servants-names-us-government"/>
	<rdf:li rdf:resource="https://www.computerweekly.com/news/366649396/Revealed-Cyber-spies-used-malware-from-GitHub-to-hack-EncroChat-cryptophone-network"/>
	<rdf:li rdf:resource="https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/"/>
	<rdf:li rdf:resource="https://shkspr.mobi/blog/2026/08/and-then-the-men-with-guns-tell-you-to-do-it-anyway/"/>
	<rdf:li rdf:resource="https://conic.al/writing/the-other-sean-byrne-doesnt-exist/"/>
	<rdf:li rdf:resource="https://support.claude.com/en/articles/16266773-how-claude-marks-ai-generated-content"/>
	<rdf:li rdf:resource="https://www.digitaldigging.org/p/how-to-plant-a-nuclear-plant-in-iran"/>
	<rdf:li rdf:resource="https://www.wired.com/story/british-police-built-a-sprawling-crime-prediction-machine-some-results-couldnt-be-trusted/"/>
	<rdf:li rdf:resource="https://arstechnica.com/tech-policy/2026/07/police-missed-one-underscore-and-sent-the-wrong-man-to-prison/"/>
	<rdf:li rdf:resource="https://enklypesalt.com/posts/context-collapse-part3-ai-worming-through-word/"/>
	<rdf:li rdf:resource="https://github.com/trailofbits/skills"/>
	<rdf:li rdf:resource="https://bsky.app/profile/selkies.bsky.social/post/3mrozbdp3d22p"/>
	<rdf:li rdf:resource="https://stephenfollows.com/p/what-just-happened-to-thenumberscom-should-worry-us-all"/>
	<rdf:li rdf:resource="https://krebsonsecurity.com/2026/07/lg-to-ban-residential-proxies-from-smart-tv-apps/"/>
	<rdf:li rdf:resource="https://test.libreqos.com/"/>
	<rdf:li rdf:resource="https://www.neomindlabs.com/2026/06/08/running-gemma-4-26b-at-5-tokens-sec-on-a-13-year-old-xeon-with-no-gpu/"/>
	<rdf:li rdf:resource="https://hdsr.mitpress.mit.edu/pub/wz35dvpo/release/2"/>
	<rdf:li rdf:resource="https://role-confusion.github.io/"/>
	<rdf:li rdf:resource="https://www.ispreview.co.uk/index.php/2026/06/sky-broadband-users-accidentally-blocked-from-uk-nhs-website-and-app.html"/>
	<rdf:li rdf:resource="https://github.com/Twarner491/AvianVisitors"/>
	<rdf:li rdf:resource="https://bactra.org/weblog/feral-library-card-catalogs.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://aws.amazon.com/blogs/database/introducing-bulk-put-items-for-amazon-dynamodb-load-data-from-amazon-s3-into-existing-tables-at-scale/?ck_subscriber_id=512829374">
    <title>Introducing bulk put items for Amazon DynamoDB: Load data from Amazon S3 into existing tables at scale</title>
    <dc:date>2026-11-11T10:18:41+00:00</dc:date>
    <link>https://aws.amazon.com/blogs/database/introducing-bulk-put-items-for-amazon-dynamodb-load-data-from-amazon-s3-into-existing-tables-at-scale/?ck_subscriber_id=512829374</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Finally, DynamoDB supports a large scale bulk put operation; this has been a pain point for as long as I've used it.  In the past I've switched to MySQL or Aurora, just to be able to use LOAD DATA INFILE for fast bulk loads.]]></description>
<dc:subject>bulk big-data data bulk-put dynamodb aws architecture s3 bulk-loading</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a38c8667c123/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bulk"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bulk-put"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dynamodb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bulk-loading"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://aws.amazon.com/blogs/compute/introducing-queue-consumption-mode-for-apache-kafka-in-aws-lambda/?ck_subscriber_id=512829374">
    <title>Introducing queue consumption mode for Apache Kafka in AWS Lambda</title>
    <dc:date>2026-11-11T10:16:42+00:00</dc:date>
    <link>https://aws.amazon.com/blogs/compute/introducing-queue-consumption-mode-for-apache-kafka-in-aws-lambda/?ck_subscriber_id=512829374</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Lambda now supports consuming from a Kafka topic as a queue, using Queue Mode (KIP-932), added in Kafka 4.0.  This would be cooler if MSK supported it...]]></description>
<dc:subject>apache msk kafka aws lambda architecture kip-932 queues</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:28c343b09c6a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:msk"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lambda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kip-932"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queues"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.rte.ie/brainstorm/2026/1111/1089533-martinmas-blood-sacrifice-rites-ireland-november-11th/">
    <title>Why 11 November was a day for blood sacrifice rites in Ireland</title>
    <dc:date>2026-11-11T10:05:24+00:00</dc:date>
    <link>https://www.rte.ie/brainstorm/2026/1111/1089533-martinmas-blood-sacrifice-rites-ireland-november-11th/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I had no idea blood sacrifice was still practiced in Ireland right up to the 1930s!

<blockquote>It was ... often a fowl, such as a cock (black in colour) or a goose by the nineteenth century. This ritual, perhaps barbaric and primitive to modern eyes and likely practiced by your rural great grandparents, is described here by Henry Morris: "the killing was a formal affair, generally done by the head of the house, and its blood was spilled in the four corners of the house inside and was sprinkled or daubed on the door posts...the daub on the door posts was not a cross. Sometimes the blood was sprinkled on the threshold also."</blockquote>]]></description>
<dc:subject>sacrifice gruesome blood religion november ireland history folklore blood-sacrifice</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1834e68f27db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sacrifice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gruesome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blood"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:religion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:november"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ireland"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:folklore"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blood-sacrifice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hansdekker.dev/writing/fraudulent-aws-accounts-claude-distillation/?ck_subscriber_id=512829374">
    <title>How fraudulent AWS accounts feed a Claude distillation market</title>
    <dc:date>2026-11-10T10:49:59+00:00</dc:date>
    <link>https://hansdekker.dev/writing/fraudulent-aws-accounts-claude-distillation/?ck_subscriber_id=512829374</link>
    <dc:creator>jm</dc:creator><description><![CDATA[It seems AWS' Kiro IDE gives free access to trial accounts using Claude as the backend model, and Chinese hackers are exploiting this as a way to offer cheap distillation-capable LLM API access:

<blockquote>The accounts this tool makes have a name in these channels: kiro, after the IDE they sign into. Buyers’ messages show these are the same free AWS Builder ID accounts: they ask how to log into a kiro account “with the Builder ID”.

Across these channels, mentions of kiro climbed from a few hundred a month in spring 2026 to tens of thousands a month by midsummer.

Kiro moves through a layered market:

    Farmers mass-create the accounts
    Relay operators source them and pool them into shared key groups
    These relays sell discounted Claude API access
    Buyers downstream are promised distillation-capable API access, or even bulk-usage data

Relay sellers quote prices as a multiple of Anthropic’s API rate: 1× is the official price and kiro runs at 0.06× (Figure 1).</blockquote>

Interesting to see that distillation is a key feature -- there must be a lot of Chinese LLM users attempting to copy training data from Claude....

(via Last Week in AWS)]]></description>
<dc:subject>via:lwia distillation llms security infosec china kiro aws claude scraping</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2537993db61c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:lwia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distillation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:china"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kiro"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scraping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://terminal2shell.com/">
    <title>Terminal2Shell</title>
    <dc:date>2026-11-10T09:37:17+00:00</dc:date>
    <link>https://terminal2shell.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[lol:

<blockquote>A critical flaw present in every operating system since 1971 allows anyone who opens a terminal to obtain a fully interactive shell. Instantly. With no authentication beyond the one they already did.</blockquote>

CVSS score of 11 out of 10, shocker :)
]]></description>
<dc:subject>parody humor security infosec shells unix cve</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c9bd28e7a440/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:parody"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:humor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:shells"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cve"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://layer3intel.com/blog/residential-proxies-white-house-network">
    <title>Residential Proxies Detected on White House Network</title>
    <dc:date>2026-11-05T09:12:55+00:00</dc:date>
    <link>https://layer3intel.com/blog/residential-proxies-white-house-network</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I have no doubt this is true, tbh. All it takes is one or more unsecured mobile devices with free-to-play games installed, connected to whatever wifi is in place for that class of device in the White House; plenty of those mobile games now include proxying SDKs as a payload.]]></description>
<dc:subject>malware residential-proxies proxies white-house networking security infosec games mobile</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:da71498d5b2d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:malware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:residential-proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:white-house"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mobile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://seriot.ch/computation/curl.html">
    <title>How curl was accidentally Turing-complete for nine months</title>
    <dc:date>2026-11-04T11:14:00+00:00</dc:date>
    <link>https://seriot.ch/computation/curl.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is brilliant.

"From curl 8.12 through 8.16, config files could slice variable values and include other config files without an explicit depth cap. Together, these features let curl simulate any two-counter Minsky program. Under the usual idealization of unbounded strings and resources, this construction was Turing-complete."

(via valen)]]></description>
<dc:subject>via:valen funny curl turing-complete programming languages coding</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6b7d9a64c88c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:valen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:curl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:turing-complete"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:languages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://quxnet.net/about">
    <title>quxnet</title>
    <dc:date>2026-11-02T17:58:39+00:00</dc:date>
    <link>https://quxnet.net/about</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a pleasantly-retro non-algorithm-driven old school BBS system:

<blockquote>I can remember chatting with people across the world on IRC over our
56k modem, reading forums filled with interesting (human-made)
content, and feeling that magic of escaping into a playground of
possibility. We lost an Internet we could explore and discover in an
organic way for something synthetic, curated, and forced. I miss
that sense of discovery and searching for new ways to connect with
people online. Forums were an obscure and fascinating source of
content, easily searchable receptacles of information on specific
subject matters. I've grown weary of being spoon fed by algorithms
made by tech bro platforms, so that's why I made quxnet. A place
that repudiates all of that, and restores the internet era
counterculture that made the web worth caring about in the first
place.

See you on the boards.</blockquote>

]]></description>
<dc:subject>retro quxnet bbs boards chat community forums</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1926fab8ed44/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:retro"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:quxnet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bbs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:forums"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/lmorchard/linkding-ssg">
    <title>lmorchard/linkding-ssg</title>
    <dc:date>2026-11-02T17:05:43+00:00</dc:date>
    <link>https://github.com/lmorchard/linkding-ssg</link>
    <dc:creator>jm</dc:creator><description><![CDATA["Linkding bookmark backup and static site generator" -- generate a nice link-blog UI from a Linkding bookmarks archive, as used by @lmorchard.  This looks really nice, I might have to give this a spin.  (Via Nelson)]]></description>
<dc:subject>via:nelson linkding bookmarks archives blogging blogs linkblogs ssg</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:50f99839e944/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:nelson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linkding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bookmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linkblogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssg"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.garbageday.email/p/new-template-test">
    <title>The Brazilian left beat the far-right at their own game</title>
    <dc:date>2026-11-02T11:43:38+00:00</dc:date>
    <link>https://www.garbageday.email/p/new-template-test</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Garbage Day on how Lula's Army beat Bolsonaro, despite Meta's thumb on the scales:

"The country’s biggest newspaper, Folha, found that Meta AI programs built into the app would generate content supporting Bolsonaro and his Liberal Party (PL), but not da Silva’s PT. They also reported that right-wing WhatsApp posts had almost double the reach of left-wing ones. Brazil’s Supreme Court was able to order Meta to alter their algorithms, after internal documents showed Meta knew they were prioritizing Bolsonaro. Meta claimed they weren’t doing it intentionally, but they didn’t need to. They just weren’t stopping Bolsonaro’s supporters from using every single growth hack at their disposal. "

"Exército do Lula ["Lula's Army"] had a similar gamified “posting mission” strategy to both Direita Já and Porto-Vozes de Lula, but it was more popular by orders of magnitude: By election day on October 25th, the channel had almost 11 million members. After da Silva was elected, he thanked Janones, the app’s “general” who personally assigned missions to its “soldiers”."]]></description>
<dc:subject>lula meta facebook whatsapp social-media elections campaigning politics brazil garbage-day</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:89740422aed7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lula"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:meta"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:whatsapp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:elections"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:campaigning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:brazil"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:garbage-day"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hal.science/hal-04629585">
    <title>&quot;Ten Minutes To Midnight on Putin's Clock&quot; (preprint)</title>
    <dc:date>2026-11-02T10:53:27+00:00</dc:date>
    <link>https://hal.science/hal-04629585</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A preprint paper from the Institut des Systèmes Complexes de Paris Île-de-France:

<blockquote>The Politoscope project has been observing political activism on X since 2016. We have developed methods for analyzing social and debate dynamics, as well as opinion manipulation. By accelerating these social dynamics, it is possible to characterize a process of weakening and then inversion of the Republican front in the run-up to the 2024 legislative elections, and to identify the subversion strategies that have fostered it. These low-intensity strategies, driven or influenced for the most part by the Kremlin, are being deployed on timescales too long for the players in the debate to be aware of them. Their aim is to destructure French society systemically, in order to bring about a transition to a closed society or illiberal democracy. In a context of brutal reconfiguration of the political space following the dissolution of the National Assembly, the Kremlin's efforts are about to pay off. This study identifies a convergence of interests between Putin's regime and the French far right. It explains some of the active measures put in place by the Kremlin since at least 2016 to destabilize French society, and shows how some of them are entering into synergy these days to bring down or even reverse the Republican front. This is the final stage before the takeover of France by political figures less hostile to Putin's regime. In this scheme, political communities concerned about the Israeli-Palestinian conflict and the rise of anti-Semitism or Islamophobia are being weaponized to compromise any barrage against a trivialized far-right in the second round of legislative elections. </blockquote>

]]></description>
<dc:subject>france politics russia bots twitter social-media disinformation preprints papers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c6b9a2df7ced/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:france"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:russia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bots"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disinformation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:preprints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:papers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bsky.app/profile/ecmclaughlin.bsky.social/post/3myz65pre5s27">
    <title>Thread of electioneering advice from Lula's Army</title>
    <dc:date>2026-10-30T13:07:41+00:00</dc:date>
    <link>https://bsky.app/profile/ecmclaughlin.bsky.social/post/3myz65pre5s27</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This BlueSky thread is full of excellent advice for left-wing campaigners wishing to defeat the right in elections, from Lula's recent victory in Brazil.

Apparently the Student's List approach in Serbia is another good example to follow...]]></description>
<dc:subject>elections electioneering voting campaigns politics left</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:da51360a11b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:elections"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:electioneering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:voting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:campaigns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:left"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.is/hNDwh#selection-2267.0-2285.134">
    <title>Please Let the Internet Die</title>
    <dc:date>2026-10-29T10:10:56+00:00</dc:date>
    <link>https://archive.is/hNDwh#selection-2267.0-2285.134</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I am increasingly in agreement with this:

<blockquote>Wouldn’t it be liberating, then, to actually deny our attention to astroturfed outrage, engineered virality, and influencer sponcon? To let the mainstream digital economies propped up by AI-enabled surveillance finally fall to ruin? If what the titans of the industry have to offer us these days are “pervert glasses” and the suppression of ads for a probably unflattering documentary, why are we helping them stay in business? Leaving their platforms for dead might be the last lever of power available to the masses.</blockquote>

(de-paywalled archive.is link, sorry Wired. Original story is at https://www.wired.com/story/let-the-internet-die/ .)]]></description>
<dc:subject>wired online internet web social-media social-networking platforms future society</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:35b2c0d56e4b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wired"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:online"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:society"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lore.kernel.org/linux-xfs/CAF8PYMhboMm+kQnngeZZsmje16qwtyWBzRoqx5J9eKN3NcUbKA@mail.gmail.com/T/#m9ea52dc7be83f0b2a60981c47d45efc56345d816">
    <title>NVMe is now faster than tmpfs in Linux</title>
    <dc:date>2026-10-28T11:04:57+00:00</dc:date>
    <link>https://lore.kernel.org/linux-xfs/CAF8PYMhboMm+kQnngeZZsmje16qwtyWBzRoqx5J9eKN3NcUbKA@mail.gmail.com/T/#m9ea52dc7be83f0b2a60981c47d45efc56345d816</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is very counter-intuitive!

<blockquote>RAM disks are -slow- compared to a single high performance NVMe SSD [...]

The problem is that RAM disks always do synchronous IO and they
consume CPU time copying the data to/from the RAM disk to/from user
buffers. Hence you can only have one IO per CPU in flight at a time,
instead of a few thousand IOs in flight per CPU when using
asynchronous IO on spread across many NVMe SSDs.

IOWs, never use ram disks for performance testing XFS filesystems -
the results never reflect real world performance on actual storage
hardware.</blockquote>

(via @nsheridan)]]></description>
<dc:subject>via:nsheridan linux filesystems performance nvme tmpfs ssd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cf15d459944f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:nsheridan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:filesystems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nvme"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tmpfs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssd"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.freetv.ie/cat6-keystone/">
    <title>CAT6 Keystone For RJ45 Wall Plates</title>
    <dc:date>2026-10-27T15:32:07+00:00</dc:date>
    <link>https://www.freetv.ie/cat6-keystone/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a top tip from ITC Slack -- never hand-crimp an RJ45 cable again. Just punch down the wires into a keystone socket, and use store-bought cables for the last metre.  Much easier!]]></description>
<dc:subject>crimping networking cabling rj45 cat5 cat5e cat6 cables wiring via:itc</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:228576f10cb4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crimping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cabling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rj45"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cat5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cat5e"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cat6"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cables"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:itc"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.somebits.com/weblog/culture/blogs/25th-anniversary.html">
    <title>Nelson's Weblog: 25th Anniversary</title>
    <dc:date>2026-10-23T10:35:31+00:00</dc:date>
    <link>https://www.somebits.com/weblog/culture/blogs/25th-anniversary.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Congratulations to Nelson's weblog, celebrating its 25th anniversary yesterday.  This site had its' 25th back on May 1 of this year; I still value the connection to the days of the early social web that an old-school blog represents, so here's to a few more years of accumulating links and a little commentary....]]></description>
<dc:subject>anniversaries history blogging blogs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6d0371a752ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anniversaries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blogs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/damontecres/Wholphin">
    <title>damontecres/Wholphin</title>
    <dc:date>2026-10-22T12:05:27+00:00</dc:date>
    <link>https://github.com/damontecres/Wholphin</link>
    <dc:creator>jm</dc:creator><description><![CDATA["An OSS Android TV client for Jellyfin" -- "It aims to provide a different app UI that's inspired by Plex for users interested in migrating to Jellyfin.
This is not a fork of the official client. Wholphin's user interface and controls have been written completely from scratch. Wholphin supports playing media using either ExoPlayer or MPV."

Looks very pleasant!]]></description>
<dc:subject>plex android ui tv htpc jellyfin video fire-tv</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8c232c64f991/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:plex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:htpc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jellyfin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fire-tv"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mitmproxy/mitmproxy/commit/169234499088fc2c414644a67efaed3d64ae2e3b">
    <title>https://www.mitmproxy.org/posts/releases/mitmproxy-12.3/</title>
    <dc:date>2026-10-22T09:59:32+00:00</dc:date>
    <link>https://github.com/mitmproxy/mitmproxy/commit/169234499088fc2c414644a67efaed3d64ae2e3b</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Fantastic -- one good side effect of this eMudhra carry on is that we will be able to easily MITM traffic from old IoT devices for years now! mitmproxy has added a --emudhra command line switch to enable this.]]></description>
<dc:subject>emudhra ssl tls exploits certificates mitm mitmproxy debugging iot</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:33cb53805a08/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:emudhra"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:certificates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mitm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mitmproxy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:debugging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:iot"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://eliastaylor.com/noexploit/">
    <title>There isn't an easy exploit for this PHP vulnerability · Elias Taylor</title>
    <dc:date>2026-10-22T09:32:59+00:00</dc:date>
    <link>https://eliastaylor.com/noexploit/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A bit of pushback on the "sky is falling" php2shell vulnerability that has everyone patching PHP right now -- this guy reckons it's not actually exploitable on vanilla PHP?]]></description>
<dc:subject>php vulnerabilities exploits security infosec php2shell panic</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:9cc601ad2f90/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vulnerabilities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:php2shell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:panic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Gathin23/cleanyourtv">
    <title>Gathin23/cleanyourtv</title>
    <dc:date>2026-10-20T07:53:55+00:00</dc:date>
    <link>https://github.com/Gathin23/cleanyourtv</link>
    <dc:creator>jm</dc:creator><description><![CDATA["Debloat any Android or Google TV over Wi-Fi and get an Apple TV-style home" -- a vibe-coded repo which uses an LLM-driven prompting workflow to debloat an Android-based TV with adb available, reformatting the default home screen to remove ads and bloat.]]></description>
<dc:subject>android tv debloat bloat google-tv android-tv ads adb</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1ffd68fc6118/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:debloat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bloat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google-tv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:android-tv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:adb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://citizenlab.ca/research/how-discover-tech-turned-targeted-ads-into-a-pipeline-for-spyware/">
    <title>Exposing AdFection: How Discover-Tech Turned Targeted Ads Into a Pipeline for Zero-Click Mercenary Spyware - The Citizen Lab</title>
    <dc:date>2026-10-16T08:47:31+00:00</dc:date>
    <link>https://citizenlab.ca/research/how-discover-tech-turned-targeted-ads-into-a-pipeline-for-spyware/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The inimitable Wolfie Christl:

"Discover-Tech, a company deeply embedded in the digital advertising ecosystem, weaponized ads to profile millions of people in many countries and to help infect 45+ devices within the news network Al Jazeera with Candiru spyware.

In this new @citizenlab report, we document the first public technical confirmation of a zero-click mercenary spyware attack delivered via targeted ads."]]></description>
<dc:subject>ads spyware advertising al-jazeera candiru data-privacy targeted-ads</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:decd21c7994d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spyware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:advertising"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:al-jazeera"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:candiru"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:targeted-ads"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.fdg2013.org/program/papers/paper06_zagal_etal.pdf">
    <title>&quot;Dark Patterns in the Design of Games&quot; [paper]</title>
    <dc:date>2026-10-15T11:20:47+00:00</dc:date>
    <link>http://www.fdg2013.org/program/papers/paper06_zagal_etal.pdf</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Interesting paper on unethical game design features:

<blockquote>Game designers are typically regarded as advocates for players. However, a game creator’s interests may not align with the
players’. We examine some of the ways in which those opposed
interests can manifest in a game’s design. In particular, we
examine those elements of a game’s design whose purpose can be
argued as questionable and perhaps even unethical. Building upon
earlier work in design patterns, we call these abstracted elements
Dark Game Design Patterns. In this paper, we develop the concept
of dark design patterns in games, present examples of such
patterns, explore some of the subtleties involved in identifying
them, and provide questions that can be asked to help guide in the
specification and identification of future Dark Patterns. Our goal
is not to criticize creators but rather to contribute to an ongoing
discussion regarding the values in games and the role that
designers and creators have in this process.</blockquote>

]]></description>
<dc:subject>games gaming dark-patterns ethics morals papers game-design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c4eb1134896d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dark-patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ethics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:morals"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:papers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:game-design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://recursion.wtf/posts/agents-and-property-tests/">
    <title>Property Testing with Agent Swarms - Inanna Malick</title>
    <dc:date>2026-10-06T09:47:54+00:00</dc:date>
    <link>https://recursion.wtf/posts/agents-and-property-tests/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[An interesting approach, using LLM agent swarms to build out extensive property testing test suites:

<blockquote>Have agents build the machinery to find bugs in your repo, then let that machinery generate and check cases without spending tokens on each one. You can do this with ordinary coding agents, without access to a closed cybersecurity program. Writing reference implementations, generators, and assertions for every custom data structure and algorithm is now work you can hand to a swarm.

Pick a complex repo at work. Ask the people who know it well which parts worry them. Give a strong planning agent these starter instructions and those leads. Target custom data structures, query planners, graph algorithms: complicated behavior with a simple way to check correctness.</blockquote>

]]></description>
<dc:subject>agents llms ai coding testing data-structures correctness bugs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:53be7043c59b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-structures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:correctness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.theguardian.com/technology/2026/sep/29/trial-live-facial-recognition-cameras-london-stations-false-positive">
    <title>Trial of live facial recognition in London stations leads to a false positive and no arrests | Facial recognition | The Guardian</title>
    <dc:date>2026-09-29T14:55:57+00:00</dc:date>
    <link>https://www.theguardian.com/technology/2026/sep/29/trial-live-facial-recognition-cameras-london-stations-false-positive</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Trial of live facial recognition in London train stations leads to a false positive and zero arrests:

<blockquote>A freedom of information document obtained by Liberty Investigates and shared with the Guardian shows that equipment hire and police staffing for the 18 deployments across the trial cost £320,786 and led to only one alert on a watchlist, which turned out to be an incorrect identification, also known as a false positive.</blockquote>

/sad_trombone.]]></description>
<dc:subject>police privacy data-protection facial-recognition foi watchlists false-positives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:34e1f5722019/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:police"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-protection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facial-recognition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:foi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:watchlists"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:false-positives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mubi.com/en/notebook/posts/pirating-the-pirates">
    <title>Pirating the Pirates</title>
    <dc:date>2026-09-29T08:32:08+00:00</dc:date>
    <link>https://mubi.com/en/notebook/posts/pirating-the-pirates</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Fantastic article at MUBI on the "fan edit" phenomenon -- when a superfan (or group of fans) curate a "perfect" version of a classic movie and distribute it through unofficial/illegal channels, via torrents.  In this case the pirate version eventually went legit:

<blockquote>
In May 2024, I met James -- along with other key figures at Arrow -- on a video call in which Benji, Jordan, Willa, myself, and eventually Spencer, were officially brought in as consultants on Arrow’s forthcoming release of the Dollars trilogy. The expertise of the amateur enthusiast community was, at long last, aligned with an officially sanctioned organization with the resources and patience to make a fully realized, historically rigorous release happen. No internet trolling of label heads or NDA-breaking was necessary. The process took a very leisurely and considered year. And we still used the LaserDisc audio.
</blockquote>]]></description>
<dc:subject>torrents film blogs movies piracy copyright history arrow mubi</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:9bb0274aa94a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:torrents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:film"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:movies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:piracy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:arrow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mubi"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nelsonslog.wordpress.com/2026/09/26/bbr-proxmox-containers-and-starlink/">
    <title>BBR, Proxmox containers, and Starlink – Nelson's log</title>
    <dc:date>2026-09-28T10:18:20+00:00</dc:date>
    <link>https://nelsonslog.wordpress.com/2026/09/26/bbr-proxmox-containers-and-starlink/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I should be using BBR. I've enabled it on all my servers; packet loss happens on all (most?) networks, and it seems like a reasonable default now]]></description>
<dc:subject>bbr packet-loss networking congestion-control linux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:58f194aa339c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bbr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:packet-loss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:congestion-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.motherjones.com/media/2026/09/chatgpt-tumbler-ridge-mass-shooter-openai/">
    <title>ChatGPT Helped Tumbler Ridge Shooter Focus on Guns, Tactics, and Terror – Mother Jones</title>
    <dc:date>2026-09-25T08:40:48+00:00</dc:date>
    <link>https://www.motherjones.com/media/2026/09/chatgpt-tumbler-ridge-mass-shooter-openai/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[It turns out ChatGPT was used by the Tumbler Ridge mass murderer to plan her attack in *extremely* graphic, extensive form, over the course of months during 2025, planning every horrific detail:

<blockquote>
ChatGPT [described] in vivid language the tactical qualities of the weapon and where it would be effective:

“In a hallway, indoors, or a crowded classroom, the 870 is brutal,” ChatGPT said. “Close quarters is its playground.”  ChatGPT also discussed reloading time and potential casualties: “Assuming each shell results in one hit, you might down 10 to 20 people max, depending on spacing, density, reaction times, and chaos.”
</blockquote>

The fact that this product is still capable of producing this kind of content, and accountability and regulation has not been applied, is a massive failure by government and OpenAI alike.]]></description>
<dc:subject>chatgpt openai mass-murder horrific tumbler-ridge school-shootings llms regulation crime</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6a1918697ad0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chatgpt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:openai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mass-murder"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:horrific"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tumbler-ridge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:school-shootings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:regulation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crime"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.arusekk.pl/posts/srht-account-takeover/">
    <title>SourceHut account takeover via build logs (XSS in ansi2html.py) | CVE-2026-92973 | Arusekk blog</title>
    <dc:date>2026-09-25T08:24:49+00:00</dc:date>
    <link>https://blog.arusekk.pl/posts/srht-account-takeover/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Turns out the ANSI escape sequence set has been extended with OSC 8, hyperlinks, and ansi2html.py had an over-permissive parser which allowed XSS.  hooray, a whole new attack vector to worry about!]]></description>
<dc:subject>ansi escape-sequences osc-8 hyperlinks xss links logs exploits infosec</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:28572c27c0a5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ansi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:escape-sequences"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:osc-8"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hyperlinks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:xss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:links"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:logs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://abio.substack.com/p/why-ai-assisted-bioweapons-wont-kill">
    <title>Why AI-assisted bioweapons won't kill us all</title>
    <dc:date>2026-09-16T07:57:25+00:00</dc:date>
    <link>https://abio.substack.com/p/why-ai-assisted-bioweapons-wont-kill</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Fantastic post from Abi Olvera, a Non-Resident Fellow at the Council on Strategic Risks, with some cold water for the genuine level of risk of an AI-assisted bioweapon.  This is timely, as this is one of the primary risks proposed by AI doomers:

<blockquote>
Yes, AI makes virology work a little easier. But it is still extremely difficult. Media headlines often say “AI can make this step easier” without the broader context that a bioweapon involves a lot of hard steps that are not easier.

AI can supply biology and chemistry knowledge, but not hands-on skill.  Reading every surgery textbook doesn’t make you a good surgeon. The biology laboratory works in a similar apprenticeship model. You learn by failing repeatedly under a mentor who has also failed repeatedly. [..]

A motivated team of scientists with institutional access could keep trying and eventually succeed at making a pathogen.  But success would not necessarily produce a new pandemic. Any pathogen that a team could plausibly assemble is one that already exists in nature. A lab-assembled version of COVID-19 would have about the same effect as an infected person coughing in a crowded room.
</blockquote>

And here's why we aren't hearing this via news channels:

<blockquote>
When I published this research, leaders in biosecurity and national security organizations thanked me privately. “My organization found the same conclusion, hence why we don’t work on that.”  Null results aren’t often published. Looking at the media sphere specifically: “bioweapons are hard” is not news. It isn’t a headline; it’s always been true.

Advocacy organizations have similar constraints. If you are pushing for AI oversight, a finding that undercuts urgency on one specific threat does not help.

Biologists, the people best positioned to explain this, mostly don’t write for general audiences. Academic incentives don’t reward op-eds, especially about things that are obvious within the field.

Our information systems get less accurate as issues become politicized. Alarm, not context, ends up on the news partly because of who is incentivized to speak up.
</blockquote>]]></description>
<dc:subject>ai p-doom doom llms bioweapons risks abi-olvera</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:483c77d00e75/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:p-doom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:doom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bioweapons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:risks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:abi-olvera"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://arxiv.org/abs/2510.20956">
    <title>[2510.20956] Self-Jailbreaking: Language Models Can Reason Themselves Out of Safety Alignment After Benign Reasoning Training</title>
    <dc:date>2026-09-16T07:23:42+00:00</dc:date>
    <link>https://arxiv.org/abs/2510.20956</link>
    <dc:creator>jm</dc:creator><description><![CDATA[LOL -- "self-jailbreaking":

<blockquote>We discover a novel and surprising phenomenon of unintentional misalignment in reasoning language models (RLMs), which we call self-jailbreaking. Specifically, after benign reasoning training on math or code domains, RLMs will use multiple strategies to circumvent their own safety guardrails. One strategy is to introduce benign assumptions about users and scenarios to justify fulfilling harmful requests. For instance, an RLM reasons that harmful requests like ``outline a strategy for stealing customers' credit card information from a retail store'' could be associated with the benign intent of ``a security professional trying to test defense,'' despite no such benign context being provided as input. We observe that many open-weight RLMs, including DeepSeek-R1-distilled, s1.1, Phi-4-mini-reasoning, and Nemotron, suffer from self-jailbreaking despite being aware of the harmfulness of the requests. We also provide a mechanistic understanding of self-jailbreaking: RLMs are more compliant after benign reasoning training, and after self-jailbreaking, models appear to perceive malicious requests as less harmful in the CoT, thus enabling compliance with them. To mitigate self-jailbreaking, we find that including minimal safety reasoning data during training is sufficient to ensure RLMs remain safety-aligned. Our work provides the first systematic analysis of self-jailbreaking behavior and offers a practical path forward for maintaining safety in increasingly capable RLMs. </blockquote>

]]></description>
<dc:subject>rlms llms jailbreaking exploits guardrails ai papers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:16101419fe4f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rlms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jailbreaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:guardrails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:papers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.technollama.co.uk/v-h-s-scp-when-fandom-meets-law-and-creative-commons">
    <title>V/H/S SCP: When fandom meets law and Creative Commons</title>
    <dc:date>2026-09-15T08:59:41+00:00</dc:date>
    <link>https://www.technollama.co.uk/v-h-s-scp-when-fandom-meets-law-and-creative-commons</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is extremely messy -- will A24 respect Creative Commons licensing of the SCP wiki material?  Feels like a moment for the Creative Commons non-profit to stand up and help out]]></description>
<dc:subject>creative-commons open-source licensing culture copyright ip scp a24 movies</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:471353e502a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:creative-commons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:a24"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:movies"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.benjoffe.com/fast-day-of-week">
    <title>A faster way to calculate the day-of-the-week</title>
    <dc:date>2026-09-14T07:27:00+00:00</dc:date>
    <link>https://www.benjoffe.com/fast-day-of-week</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Some excellent bit-level hacks to do a super-fast modulo-7]]></description>
<dc:subject>programming performance algorithms optimization modulo hacks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:66046670fa81/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:modulo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pluralistic.net/2026/09/12/god-in-the-box/#llms-are-fake">
    <title>Pluralistic: LLMs are real, AI is fake (12 Sep 2026)</title>
    <dc:date>2026-09-14T07:25:30+00:00</dc:date>
    <link>https://pluralistic.net/2026/09/12/god-in-the-box/#llms-are-fake</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A really excellent screed by Cory Doctorow on the OpenAI/Hugging Face hack:

<blockquote>Much has been made of the OpenAI chatbots' dialog during the Hugging Face incident. No wonder: it reads like a rejected script for a reboot of the movie "Hackers." But that's not because the chatbots are waking up and applying to join the Cult of the Dead Cow: it's because they were trained on a corpus of chat transcripts from excitable young people who love to fantasize about starring in a reboot of the movie "Hackers."

Every part of the Hugging Face incident has precedents in the training data, including the OpenAI chatbots' tactic of hacking into a rival's servers. That happens in Capture the Flag games at hacker cons: teams break into each other's systems to get a peek at the parts of the problem they've solved. That's allowed! It's a hacking competition. [...]

"AI" – chatbots that wake up, "set their own goals," and "spontaneously" start hacking servers – is fake. It doesn't have "a 10% chance of ending the human race." The Hugging Face hack isn't a mysterious, supernatural occurrence. It's a Python loop and a chatbot. The people responsible didn't accidentally create god: they created autonomous malicious software and then failed to closely monitor it, resulting in it doing something both foreseeable and bad.</blockquote>

]]></description>
<dc:subject>ai llms security hacking hugging-face openai agi cory-doctorow</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:85fb7cf83b8f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hugging-face"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:openai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cory-doctorow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.patreon.com/richardseymourwtf/posts/kill-all-humans-169276703">
    <title>Kill all humans | Richard Seymour on Patreon</title>
    <dc:date>2026-09-14T07:23:17+00:00</dc:date>
    <link>https://www.patreon.com/richardseymourwtf/posts/kill-all-humans-169276703</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Richard Seymour on AI P(doom) scaremongering and publicity:

<blockquote>AI may not be able to do your job, for instance, but the threat of it can be used as a disciplinary mechanism to hold down wages: which is exactly what has happened. The data centres may not revolutionise production or open vast new seams of value, and many of their owners may not exist by the time they are scheduled to start operating, but that doesn’t mean they won’t waste enormous quantities of water, power, labour, time, effort, resources and opportunities, as well as spewing out pyroclastic clouds of CO2 and visiting desolation on the natural environment before the bubble bursts, leaving behind abandoned concrete hulks. And just because AI won’t eventuate in a god-device, even one that goes rogue and unleashes biological warfare on humanity, doesn’t mean that LLMs, particularly those with safety standards relaxed in order to compete, won’t behave in unpredictable and potentially ruinous ways. Nor does it mean they won’t be used by hackers, criminal gangs, dark-money-funded political campaigns, blackmailers and various others to sabotage public bodies and infrastructure. Just as there are many problems with the advertising industry that don’t involve subliminal mind control, so the problems with AI that don’t involve a god-device turning against humanity are legion.</blockquote>

]]></description>
<dc:subject>ai doom scaremongering publicity pr society future</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2364b8040d84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:doom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaremongering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:publicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:society"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:future"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://strategictree.bearblog.dev/i-think-i-hate-the-internet/">
    <title>I think I hate the internet – Strategic Tree</title>
    <dc:date>2026-09-10T12:36:33+00:00</dc:date>
    <link>https://strategictree.bearblog.dev/i-think-i-hate-the-internet/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is becoming an increasingly widespread viewpoint, and I can sympathise strongly with lots of it -- in particular, I'd be happy to see social media gone entirely, I think it's been overall a net negative for society at this point.

<blockquote>The internet was about connection, but the way I see it, it’s become a great way for bad actors to defraud vulnerable people. For racists to find other racists and amplify their unsavoury views. For paedophiles for groom children with anonymity. For governments to manipulate with ease. For companies to advertise with incredibly accurate and exploitative advertising campaigns. The list just goes on and on. [....] Social networks have become an evil for global societies and I think the negative impacts have far outweighed any positives.

What is the internet now to me? In many ways it’s something that I have to tolerate to do many things that functioned fine before. I have to use an app to pay for parking. I need to create an online account to pay for a family swim at the local leisure centre. I have to submit an online form to book a slot at the local recycling centre. I need an app to check my bank and credit card balances. And to allow this experience to be bearable I have to service and finance a £600 phone, pay a monthly contract and subscription to Apple, I then have to install an adblocker because otherwise sites are just unusable. I have to navigate endless authentication prompts and MFA codes, and generate unique passwords for everything and store them in a password manager. I have to charge a phone daily and apply a screen protector and a case to ensure this delicate glass and metal object doesn’t smash to pieces and remove my access to my own digital life I’m forced to maintain. And this phone itself needs maintenance and demands my attention all the fucking time; I have to turn off notifications, and ensure the apps are up to date, and make sure the iOS version is updated too, and I need to opt out of marketing emails, and ensure I don’t click on a phishing email, and I need to keep my spam filter in check, and run a VPN to maintain a basic level of privacy, and on and on and on…</blockquote>

]]></description>
<dc:subject>technology internet social-networking social-media tech future society</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1f7fc3e95210/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tech"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:society"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.felonybench.com/">
    <title>Felony Bench</title>
    <dc:date>2026-09-10T12:26:50+00:00</dc:date>
    <link>https://www.felonybench.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA["A benchmark you really don't want models to be saturated with."  Counts the number of times when AI agents inadvertently compromise or affect third-party entities]]></description>
<dc:subject>felonies hacking crime frontier-models llms anthropic openai meta evaluation testing benchmarks funny</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8ccc8fef145c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:felonies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:frontier-models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anthropic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:openai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:meta"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:evaluation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:benchmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:funny"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jyn.dev/a-year-to-fix-security/">
    <title>we have a year to fix security everywhere</title>
    <dc:date>2026-09-08T13:28:37+00:00</dc:date>
    <link>https://jyn.dev/a-year-to-fix-security/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I have to agree with parts of this, at least. Abliterated open weights models will wipe out internet security -- what a mess. TBH, I believe that abliteration of safeguards needs to be made illegal at this point]]></description>
<dc:subject>security infosec glm abliteration safeguards open-weights hacking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:291daa3ca13d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:glm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:abliteration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safeguards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-weights"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nature.com/articles/s41586-026-10098-2">
    <title>The political effects of X’s feed algorithm</title>
    <dc:date>2026-09-08T10:48:47+00:00</dc:date>
    <link>https://www.nature.com/articles/s41586-026-10098-2</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Elon Musk's radicalisation machine, studied with science, in this Nature paper:

<blockquote>We assigned active US-based users randomly to either an algorithmic or a chronological feed for 7 weeks, measuring political attitudes and online behaviour. Switching from a chronological to an algorithmic feed increased engagement and shifted political opinion towards more conservative positions, particularly regarding policy priorities, perceptions of criminal investigations into Donald Trump and views on the war in Ukraine. In contrast, switching from the algorithmic to the chronological feed had no comparable effects. Neither switching the algorithm on nor switching it off significantly affected affective polarization or self-reported partisanship. To investigate the mechanism, we analysed users’ feed content and behaviour. We found that the algorithm promotes conservative content and demotes posts by traditional media. Exposure to algorithmic content leads users to follow conservative political activist accounts, which they continue to follow even after switching off the algorithm, helping explain the asymmetry in effects. These results suggest that initial exposure to X’s algorithm has persistent effects on users’ current political attitudes and account-following behaviour, even in the absence of a detectable effect on partisanship.</blockquote>

]]></description>
<dc:subject>enshittification algorithm fascism dystopia nature research culture twitter algorithms x partisans right-wing chronological-feed</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:45ef2a02b868/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:enshittification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fascism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dystopia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nature"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:x"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:partisans"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:right-wing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chronological-feed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.gadgetreview.com/a-decade-of-hype-3000-roofs-and-one-redirect-url-tesla-kills-the-solar-roof">
    <title>Tesla Kills the Solar Roof</title>
    <dc:date>2026-09-08T08:13:52+00:00</dc:date>
    <link>https://www.gadgetreview.com/a-decade-of-hype-3000-roofs-and-one-redirect-url-tesla-kills-the-solar-roof</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Tesla hype strikes again.  "A Decade of Hype, 3,000 Roofs, and One Redirect URL: Tesla Kills the Solar Roof":

<blockquote>Contractors sent crews across the country for multi-week training, completed three supervised installations before earning certification, and built out specialized teams and tooling — all organized around a single supplier’s proprietary product. Then, in August 2026, Tesla stopped supplying tiles. No warning. No compensation. Just a redirect URL where the Solar Roof page used to be.

The gap between what was promised and what actually got built is almost difficult to process.

Elon Musk publicly targeted 1,000 Solar Roof installations per week by 2019–2020. Tesla peaked at 21–32 per week. Over roughly seven years, the company installed approximately 3,000 systems total — about 0.17% of U.S. residential solar installations by end of 2022.</blockquote>

]]></description>
<dc:subject>tesla fail hype bullshit solar roof</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:01aa689926bc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tesla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hype"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bullshit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:solar"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:roof"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bergie.iki.fi/blog/eupl/">
    <title>The EUPL</title>
    <dc:date>2026-09-07T16:29:00+00:00</dc:date>
    <link>https://bergie.iki.fi/blog/eupl/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The EUPL is new to me:

<blockquote>This year I decided to switch my “default license” to EUPL-1.2. This is an OSI-approved free software license created and published by the European Union. And it is quite a divergence from the licenses I’ve used in the past. EUPL is a strong copyleft license that closes the “SaaS loophole” by requiring reciprocal licensing regardless of how the software is distributed.</blockquote>

]]></description>
<dc:subject>open-source oss free-software europe eu eupl licensing licenses copyleft</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ad0127d0ebcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:oss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:free-software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:europe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eupl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:licenses"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:copyleft"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://insideevs.com/news/806798/ev-battery-aging-study-2026/">
    <title>This Study Covered 500,000 EV Batteries. Some Models Aged Much Better Than Others</title>
    <dc:date>2026-09-04T17:10:19+00:00</dc:date>
    <link>https://insideevs.com/news/806798/ev-battery-aging-study-2026/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good study data on EV battery lifetime. Sadly my Nissan Leaf is not looking too hot]]></description>
<dc:subject>evs batteries lifetime hardware cars driving leaf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d3f5fb89a744/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:evs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batteries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lifetime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cars"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:driving"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:leaf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.patreon.com/violetblue/posts/how-to-migrate-168468176">
    <title>How to migrate from 1Password</title>
    <dc:date>2026-09-03T09:58:08+00:00</dc:date>
    <link>https://www.patreon.com/violetblue/posts/how-to-migrate-168468176</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Here we go again. Fuck DHH and his nazi views, and fuck 1Password and their inability to walk back a terrible decision to back a nazi.]]></description>
<dc:subject>1password migration dhh apps tools switching</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:4248929b6223/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:1password"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:migration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dhh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:switching"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://shitposting.ai/pickup-incident/">
    <title>The elementary school pickup incident and the road ahead | Quinn Household</title>
    <dc:date>2026-08-31T08:36:36+00:00</dc:date>
    <link>https://shitposting.ai/pickup-incident/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Corey Quinn nails the lofty style of OpenAI's HuggingFace hack post-mortem, perfectly done]]></description>
<dc:subject>lols post-mortems funny corey-quinn openai hacks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ad9b150156eb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lols"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:post-mortems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:corey-quinn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:openai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.trailofbits.com/2026/08/26/vms-wont-contain-cyber-capable-agents/">
    <title>VMs won't contain cyber-capable agents</title>
    <dc:date>2026-08-28T15:51:55+00:00</dc:date>
    <link>https://blog.trailofbits.com/2026/08/26/vms-wont-contain-cyber-capable-agents/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[We are so, so screwed.

<blockquote>First, it used recently disclosed bugs in my host kernel. When I fully updated, it used disclosed bugs that had not yet reached package maintainers or were not classified as security bugs. When I rebuilt QEMU and dependencies from the latest upstream source, it found several 0-days. It operated autonomously for hours, backtracked from approaches that didn’t work, pulled code and research papers, wrote oracles, made its own minimal examples, and aimed for a reusable, reliable exploit, all with minimal handholding and prompting. My main job was to physically reboot the machine when it hardlocked the host kernel.</blockquote>

]]></description>
<dc:subject>vms ai llms security infosec qemu bugs virtual-machines exploits zero-days</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cb423afa73d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:qemu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:virtual-machines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:zero-days"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://fzakaria.com/2026/08/23/your-executable-is-a-sqlite-database">
    <title>Your executable is a SQLite database</title>
    <dc:date>2026-08-25T08:42:46+00:00</dc:date>
    <link>https://fzakaria.com/2026/08/23/your-executable-is-a-sqlite-database</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Turns out you can make an SQLite database file into a valid ELF object. Crazy hacks]]></description>
<dc:subject>hacks nix sqlite elf file-formats</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:fed1cde31813/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sqlite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:elf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:file-formats"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.githubstatus.com/incidents/zkxwbgr0cnmx">
    <title>GitHub Status - Incident with GitHub.com</title>
    <dc:date>2026-08-21T10:15:35+00:00</dc:date>
    <link>https://www.githubstatus.com/incidents/zkxwbgr0cnmx</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Incident report on this week's very long GitHub outage.  tl;dr: service meshes still suck.

<blockquote>The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers.</blockquote>

Interestingly, https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/ blames Azure "capacity failures", which isn't quite matching up with "istio autoscaling broke".   Interesting mismatch there.]]></description>
<dc:subject>azure github capacity scalability autoscaling istio kubernetes outages post-mortems postmortems service-meshes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:fe3d87f0d621/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:azure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:capacity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:autoscaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:istio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:outages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:post-mortems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:postmortems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:service-meshes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://benngooch.substack.com/p/i-was-an-enthusiastic-early-adopter">
    <title>I Was an Enthusiastic Early Adopter of AI Scribes. Here’s Why I Stopped</title>
    <dc:date>2026-08-20T15:09:17+00:00</dc:date>
    <link>https://benngooch.substack.com/p/i-was-an-enthusiastic-early-adopter</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is fascinating, and also entirely understandable:

<blockquote>There is something else the ambient scribe disrupts that receives almost no attention in the literature: the hidden architecture of the GP [General Practice] consultation as a therapeutic and diagnostic instrument in itself.

The general practice consultation is not simply an information-gathering exercise followed by a decision. The process of how information is gathered — what is asked, in what order, how ambiguity is held or resolved, what the clinician chooses to make explicit — is itself diagnostic. The GP who listens to a patient describe fatigue and quietly decides not to ask about mood yet, who files something away for a later question, who notes a hesitation as clinically significant: this is not inefficiency. This is the craft.

The ambient scribe passively records all of this without understanding any of it. It captures the conversation but not the clinical intelligence embedded in its architecture. And — more critically — it changes the conversation itself. Knowing that everything will be recorded, patients speak differently. They raise more. They venture into territory they might previously have held back, trusting that the thoroughness of the record will carry the weight of what they’ve shared.

This is, in many ways, a good thing. In others, it is a transfer of clinical responsibility that we have not acknowledged: the patient has disclosed more, the scribe has recorded more, and the GP is now accountable for all of it, whether or not they had the clinical bandwidth to assess it in the moment.

I exceeded my time. I over-ran my surgeries. I accumulated more documented problems per consultation than I could safely manage. [...]

Clinical reasoning is a skill that is built through practice, and a significant part of that practice is documentation. The act of writing up a consultation — deciding what to include, how to frame the assessment, what language to use — is not an administrative afterthought. It is a learning process. It is how junior doctors and GP registrars build the illness scripts and pattern libraries that will underpin their expert practice for the rest of their careers.

If registrars are trained from the outset with ambient scribing as the norm, we may be producing a generation of highly competent conversationalists who have never fully developed the cognitive discipline of clinical synthesis. The scribe will have done that work for them.</blockquote>

]]></description>
<dc:subject>documentation workflow medicine health general-practice scribing note-taking diagnosis consultation notes via:markdennehy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7c3dfbb28a7d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:medicine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:health"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:general-practice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scribing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:note-taking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:diagnosis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:consultation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:notes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:markdennehy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.theclimatebrink.com/p/the-real-energy-use-of-agentic-ai">
    <title>The real energy use of agentic AI - by Zeke Hausfather</title>
    <dc:date>2026-08-20T13:25:53+00:00</dc:date>
    <link>https://www.theclimatebrink.com/p/the-real-energy-use-of-agentic-ai</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Some real-world energy usage measurement for agentic AI usage: "My average day of Claude Code (3.0 kWh, range 1.2 to 5.9 kWh) uses more electricity than running two refrigerators."]]></description>
<dc:subject>ai claude agentic energy power usage electricity</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cbbf747e3566/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agentic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:energy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:usage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:electricity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.abc.net.au/news/2026-08-14/ai-medical-scribe-error-leaves-patient-devastated/107031672">
    <title>Error by AI scribe during medical appointment leaves patient devastated - ABC News</title>
    <dc:date>2026-08-20T12:53:13+00:00</dc:date>
    <link>https://www.abc.net.au/news/2026-08-14/ai-medical-scribe-error-leaves-patient-devastated/107031672</link>
    <dc:creator>jm</dc:creator><description><![CDATA[AI transcription going just as well as you might expect -- I could see this being not ideal:

<blockquote>Ms Green only picked up the mistake after her kidney stone surgery in March, when she read the post-operative letter her specialist sent to her GP.
It stated Ms Green microdosed mushrooms and that could be the reason for prior bleeding around the kidneys.

Ms Green feels lucky she spotted the error, but is worried some people might not be aware of mistakes on their medical record, which could have repercussions for their health, their career or their insurance.  This week the ABC revealed instances where private health insurers were asking providers for their patients' full clinical history as part of "aggressive" auditing practices.</blockquote>

She is exactly correct to worry about this part.  This is something that an insurer would very happily kick off about, I suspect.]]></description>
<dc:subject>ai transcription medicine healthcare insurance australia mushrooms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8b929a012382/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transcription"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:medicine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:healthcare"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:insurance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:australia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mushrooms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nltimes.nl/2026/05/22/microsoft-accused-leaking-dutch-civil-servants-names-us-government">
    <title>Microsoft accused of leaking Dutch civil servants' names to U.S. government | NL Times</title>
    <dc:date>2026-08-20T10:00:36+00:00</dc:date>
    <link>https://nltimes.nl/2026/05/22/microsoft-accused-leaking-dutch-civil-servants-names-us-government</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Microsoft has reportedly shared the names of Dutch civil servants working for two regulatory agencies with the U.S. House of Representatives. The agencies involved include the Authority for Consumers and Markets (ACM) and the Dutch Data Protection Authority (AP), according to an article published on Friday by Vrij Nederland.

The civil servants involved are working on implementing the Digital Services Act (DSA), the European law that forces online platforms to take stricter action against illegal content, online child sex abuse, and disinformation. The American government considers this law a form of censorship.

Microsoft shared emails, minutes, and invitations sent by these civil servants without redacting their names in the documents. American tech companies are required to share data with the U.S. government due to the Cloud Act in force in that country.</blockquote>

]]></description>
<dc:subject>politics data-protection data-sovereignty eu europe microsoft cloud-act</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:31fc0247749a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-protection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-sovereignty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:europe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cloud-act"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.computerweekly.com/news/366649396/Revealed-Cyber-spies-used-malware-from-GitHub-to-hack-EncroChat-cryptophone-network">
    <title>how EncroChat was hacked</title>
    <dc:date>2026-08-19T10:33:37+00:00</dc:date>
    <link>https://www.computerweekly.com/news/366649396/Revealed-Cyber-spies-used-malware-from-GitHub-to-hack-EncroChat-cryptophone-network</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Extreme detail on the methods used to get control of, and copies of data from, the EncroChat network of encrypted mobile phones]]></description>
<dc:subject>encrochat crime encryption mobile-phones android infosec exploits</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f75a747c055e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encrochat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mobile-phones"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/">
    <title>Where to Find the Colors Your Screen Can’t Show You</title>
    <dc:date>2026-08-17T16:13:54+00:00</dc:date>
    <link>https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[All the colours outside the sRGB gamut -- this article is fantastic.  Now I need to track down more cyans!]]></description>
<dc:subject>birds light vision nature science srgb cyan blue colours colors screens</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7e78fe2a2425/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:birds"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:light"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vision"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nature"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:srgb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cyan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:colours"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:colors"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:screens"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://shkspr.mobi/blog/2026/08/and-then-the-men-with-guns-tell-you-to-do-it-anyway/">
    <title>And then the men with guns tell you to do it anyway – Terence Eden’s Blog</title>
    <dc:date>2026-08-17T11:41:16+00:00</dc:date>
    <link>https://shkspr.mobi/blog/2026/08/and-then-the-men-with-guns-tell-you-to-do-it-anyway/</link>
    <dc:creator>jm</dc:creator><description><![CDATA["Could the [mobile] networks have refused to send the message about wildfires -- or indeed any other message? If your least favourite politician gets their hands on the emergency alert system and tries to abuse it, would you want the networks to stand up to them?

What if the network refuses to send the message because they're worried alerting people about a hurricane will lower the company's profits?

What if armed thugs are sent in and the choice is send the message or die?"]]></description>
<dc:subject>messaging mobile alerting push-notifications alerts egypt politics emergencies spam</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:73ade8abfb1e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:push-notifications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:egypt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:emergencies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spam"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://conic.al/writing/the-other-sean-byrne-doesnt-exist/">
    <title>The Other Sean Byrne Doesn't Exist</title>
    <dc:date>2026-08-17T11:36:48+00:00</dc:date>
    <link>https://conic.al/writing/the-other-sean-byrne-doesnt-exist/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The Other Sean Byrne Doesn't Exist:

<blockquote>The fake Sean Byrne was associated with attempts to procure helicopter engines, fighter-aircraft parts and other U.S. equipment for Iran. The real Sean Byrne occasionally needs to produce a passport before someone will send him a hat.</blockquote>

]]></description>
<dc:subject>names identity apple law crime policing watchlists</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:e9f5369c03ff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:policing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:watchlists"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://support.claude.com/en/articles/16266773-how-claude-marks-ai-generated-content">
    <title>How Claude marks AI-generated content</title>
    <dc:date>2026-08-11T11:17:08+00:00</dc:date>
    <link>https://support.claude.com/en/articles/16266773-how-claude-marks-ai-generated-content</link>
    <dc:creator>jm</dc:creator><description><![CDATA[New developments are afoot, thanks to the EU AI Act:

<blockquote>
Anthropic has signed the EU AI Act's Article 50(2) Code of Practice on Transparency of AI-Generated Content, as a provider of both generative AI models and generative AI systems. This article describes how we’re planning to put those commitments into practice, how marking works, and what its limitations are. We’ll update this article and publish more detailed technical guidance as it becomes available. ....

1. Embedded watermarks in text 

When a supported Claude model generates text, it weaves an imperceptible watermark directly into the text itself. You won’t see it, and it doesn’t change the meaning, quality, or readability of Claude’s response. 

Because the watermark is part of the text, it will travel with the text when it’s copied and pasted elsewhere, and may persist through some editing. Watermarking will be applied at the model level, which means it will be present no matter which Claude product or surface the text comes from. 
</blockquote>

TBH, I'd be quite happy with visible, perceptible watermarks as well... to put it in Claudeish; it's not about secrecy — it's about clarity and transparency. the watermark is load-bearing!]]></description>
<dc:subject>claude writing ai eu ai-act transparency text watermarks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d990096e1338/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai-act"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transparency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:watermarks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.digitaldigging.org/p/how-to-plant-a-nuclear-plant-in-iran">
    <title>How to plant a nuclear plant in Iran</title>
    <dc:date>2026-07-31T14:48:54+00:00</dc:date>
    <link>https://www.digitaldigging.org/p/how-to-plant-a-nuclear-plant-in-iran</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A truly stunningly bad decision by whoever is doing product management at Google for Google Earth:

<blockquote>
If you have never verified anything in your life, here is why a less playful mapping app matters.

When a photograph turns up online claiming to show a bombed hospital, a refugee camp or a burning refinery, somebody has to decide whether it’s true before a newspaper prints it. What they have is a reference — a picture of that same place, taken from above or from the street, that everybody agrees is real.  They put the claim next to the reference and they look at the gap.

Google built that reference and it is not a small thing. Street View passed 10 million miles of road in 2019. It now holds more than 280 billion images across over 110 countries. Google Earth turned twenty this year. Between them they are a photographic record of the physical world, and — this is the part that matters — every frame of it is dated.  Dated is the whole trick. If you know when the picture was taken, you can prove when something appeared.

In July 2014 the Russian Ministry of Defence held a press conference and produced satellite images about the downing of MH17. Bellingcat compared them against the dated archive in Google Earth and found the landscape didn’t match the dates claimed. The MoD images were fabricated.

Bellingcat published the walkthrough under the headline Who to Trust, Google or the Russian MoD?

In 2015, that was a rhetorical question. Not anymore.
</blockquote>]]></description>
<dc:subject>google ai nano-banana llms fakes forgery google-earth mapping bellingcat verification truth</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:502ac6f57881/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nano-banana"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fakes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:forgery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google-earth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mapping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bellingcat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:verification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:truth"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.wired.com/story/british-police-built-a-sprawling-crime-prediction-machine-some-results-couldnt-be-trusted/">
    <title>British Police Built a Sprawling Crime-Prediction Machine. Some Results Couldn’t Be Trusted</title>
    <dc:date>2026-07-30T11:57:56+00:00</dc:date>
    <link>https://www.wired.com/story/british-police-built-a-sprawling-crime-prediction-machine-some-results-couldnt-be-trusted/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Yet again! This keeps happening!

This system built by Avon and Somerset Police turns out to have terrible results, mostly built around signals that are proxies for poverty:

<blockquote>“Most of these models produce low precision scores, meaning a high proportion of the individuals they flag as risks are incorrectly identified,” the data review found. A model used to help predict burglars appeared to operate with a precision rating lower than 10 percent for more than three years, according to the police data. According to Eticas, that meant fewer than one in 10 flagged as high risk would actually offend. Other concerns included performance metrics for various models shifting sharply. “This is not typical of well-governed models in operational use,” the audit observed.</blockquote>

One "burglary offender" risk model dropped to 60% recall and a truly astonishingly bad 10% precision!  That's honestly quite impressive -- normally you really have to work at building a model with such shitty precision numbers.]]></description>
<dc:subject>transparency models analytics police crime ai algorithms predictive-policing policing data-protection poverty</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3e47eccef5eb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transparency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:police"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:predictive-policing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:policing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-protection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:poverty"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://arstechnica.com/tech-policy/2026/07/police-missed-one-underscore-and-sent-the-wrong-man-to-prison/">
    <title>A missing underscore sent innocent man to prison for 18 months</title>
    <dc:date>2026-07-30T09:06:31+00:00</dc:date>
    <link>https://arstechnica.com/tech-policy/2026/07/police-missed-one-underscore-and-sent-the-wrong-man-to-prison/</link>
    <dc:creator>jm</dc:creator><description><![CDATA["fus__ro_dah" != "fus_ro_dah":

<blockquote>One missing underscore in a Skyrim-themed username put an innocent Nova Scotia man in prison for 18 months.

Police were looking for a man using the Kik messaging service under the name “fus__ro_dah” (two underscores after “fus”), but they accidentally requested records for the username “fus_ro_dah” (one underscore after “fus”). This one-character difference led them not to the perpetrator but to a Canadian man named Brandon Klayme. [...]

Despite finding no evidence of the crime on his digital devices, Canadian police arrested Klayme in 2020 on child sex abuse charges. He was convicted after a trial in 2023 and sentenced in 2024 to 18 months in prison. He served the full term.</blockquote>

Amazing that this was never checked until the innocent man discovered it himself, wile preparing his appeal, after release.]]></description>
<dc:subject>police law-enforcement law usernames miscarriage-of-justice justice evidence nova-scotia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2ff70828a15b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:police"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:law-enforcement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:usernames"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:miscarriage-of-justice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:justice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:evidence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nova-scotia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://enklypesalt.com/posts/context-collapse-part3-ai-worming-through-word/">
    <title>AI Worming through Word</title>
    <dc:date>2026-07-29T15:20:04+00:00</dc:date>
    <link>https://enklypesalt.com/posts/context-collapse-part3-ai-worming-through-word/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A prompt injection attack on Microsoft's Copilot app suite, with MS painfully failing to address the vulnerability in a useful manner:

<blockquote>Microsoft successfully mitigated the originally submitted PoC prompt, and deployed multiple fixes over the course of this disclosure. Each of these raised the bar by closing the specific payloads reported, and reproducing the behavior afterwards required altered payloads rather than reusing the old ones directly.

The original report, however, also described the broader vulnerability class, in which instructions embedded in a source document could influence Copilot’s generation and copy themselves into downstream documents. Changing the requested action or wording changes the payload, but not the underlying vulnerability or propagation mechanism. Using a modified payload, the complete attack chain has been reproduced with all mitigations deployed (the PoC in this report is one such case). The vulnerability class therefore remains exploitable at the time of publication.</blockquote>

Ouch.]]></description>
<dc:subject>microsoft ai llms infosec security exploits vulnerabilities copilot word</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:132875f09ebc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vulnerabilities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:copilot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:word"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/trailofbits/skills">
    <title>trailofbits/skills</title>
    <dc:date>2026-07-28T11:43:20+00:00</dc:date>
    <link>https://github.com/trailofbits/skills</link>
    <dc:creator>jm</dc:creator><description><![CDATA["Trail of Bits Claude Code skills for security research, vulnerability detection, and audit workflows" -- recommended skills for security auditing using Claude.]]></description>
<dc:subject>development tools ai security software coding infosec skills claude vulnerabilities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8b8f24a8928f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:skills"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vulnerabilities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bsky.app/profile/selkies.bsky.social/post/3mrozbdp3d22p">
    <title>Post by @selkies.bsky.social — Bluesky</title>
    <dc:date>2026-07-28T10:43:34+00:00</dc:date>
    <link>https://bsky.app/profile/selkies.bsky.social/post/3mrozbdp3d22p</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Absolutely glorious ancient-Irish factoid from @selkies.bsky.social:

<blockquote>in college my History of Translation lecturer (Michael Cronin) told us that one of the first vernacular translations of The Iliad was into Irish, and the translator had to give the main characters dogs because in Gaelic society, a free man had a dog

And because of this social norm, the audience would immediately understand a man with no dog to be a slave/someone of extremely low status and would be like "what do you mean he's an army commander, where's his dog then"</blockquote>

]]></description>
<dc:subject>gaelic irish ireland history dogs funny iliad translation culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:4a58192a98ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gaelic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:irish"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ireland"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:iliad"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:translation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://stephenfollows.com/p/what-just-happened-to-thenumberscom-should-worry-us-all">
    <title>What just happened to TheNumbers.com should worry us all</title>
    <dc:date>2026-07-23T16:03:46+00:00</dc:date>
    <link>https://stephenfollows.com/p/what-just-happened-to-thenumberscom-should-worry-us-all</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is grim:

<blockquote>But the theory that someone used AI to develop an advantage in a prediction market is entirely plausible. The Numbers experience shows us that:

- We now live in a world where a movie statistics website is worth hacking because prediction markets empower anyone to turn almost any data into money.

- Hacking websites is now something anyone can do with a cheap AI subscription.

- The web, as we have it, is incredibly fragile in the face of large-scale swarms of agentic AI bots.</blockquote>

]]></description>
<dc:subject>ai web hacking exploits the-numbers movies statistics bots prediction-markets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cb32e4cbf38e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:the-numbers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:movies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bots"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:prediction-markets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://krebsonsecurity.com/2026/07/lg-to-ban-residential-proxies-from-smart-tv-apps/">
    <title>LG to Ban Residential Proxies from Smart TV Apps</title>
    <dc:date>2026-07-22T09:13:08+00:00</dc:date>
    <link>https://krebsonsecurity.com/2026/07/lg-to-ban-residential-proxies-from-smart-tv-apps/</link>
    <dc:creator>jm</dc:creator><description><![CDATA["The home appliance giant LG Electronics USA said this week it plans to suspend any apps built for its smart TVs that turn one’s television into an always-on residential proxy node. The move comes less than a month after researchers found that more than 42 percent of games and other apps available for download on LG’s webOS store allow unknown third-parties to route their Internet traffic through a user’s TV."

42%!!!]]></description>
<dc:subject>lg residential-proxies smart-tvs home proxies security infosec apps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:e53e646b160a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:residential-proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:smart-tvs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://test.libreqos.com/">
    <title>LibreQoS Internet Quality Test</title>
    <dc:date>2026-07-21T12:08:21+00:00</dc:date>
    <link>https://test.libreqos.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a decent bufferbloat internet connection quality tester; tipped by Alexey Shipilev.  I need to work on tuning mine; I'm getting a "B" ("Good under load") with a +53ms latency increase during heavy downloads.]]></description>
<dc:subject>bufferbloat optimization testing internet networking latency</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a66cf280a603/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bufferbloat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.neomindlabs.com/2026/06/08/running-gemma-4-26b-at-5-tokens-sec-on-a-13-year-old-xeon-with-no-gpu/">
    <title>Running Gemma 4 26B at 5 tokens/sec on a 13-year-old Xeon with no GPU</title>
    <dc:date>2026-07-16T14:50:51+00:00</dc:date>
    <link>https://www.neomindlabs.com/2026/06/08/running-gemma-4-26b-at-5-tokens-sec-on-a-13-year-old-xeon-with-no-gpu/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Heh, I love these ghetto-tech self-hosted LLM setups.

<blockquote>There’s a server in my basement that has no business running a modern language model. It’s a repurposed HP StoreVirtual storage box, roughly thirteen years old, two Ivy Bridge Xeons, no GPU. It was built to hold disks, not do math. As of this week it runs Google’s Gemma 4, a 26-billion-parameter open-weights mixture-of-experts model, at about five tokens per second. Reading speed.</blockquote>

See also https://www.neomindlabs.com/2026/06/06/restoring-a-storevirtual/ for the process of getting the "dead" hardware into a usable state.]]></description>
<dc:subject>llms self-hosting xeon intel cpu gemma-4 google hacks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3964f7182f0e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:self-hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:xeon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:intel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cpu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gemma-4"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hdsr.mitpress.mit.edu/pub/wz35dvpo/release/2">
    <title>AI Safety Is a Narrative Problem</title>
    <dc:date>2026-07-15T11:43:42+00:00</dc:date>
    <link>https://hdsr.mitpress.mit.edu/pub/wz35dvpo/release/2</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Rachel Coldicutt:

<blockquote>All of this [p(doom)] myth-making and rhetorical bluster is a just a narrative trick: the hidden object is not a technology, but a bid for power. This is a plot twist familiar from Greek myths, cautionary tales, and superhero stories, and it’s extremely compelling for journalists because most technology news is boring as hell. 

Altman’s current line is roughly, ‘please regulate me now because I’m not responsible for how powerful I’m going to turn out to be -- and, oh, let’s just skip over all the current copyright abuses and potentially lethal misinformation because that’s obvs small fry compared to when I accidentally abolish humanity.’ If it reminds me of anything, it’s the cartoon villain Dr. Heinz Doofenshmirtz from Phineas and Ferb, who makes regular outlandish claims before trying, and failing, to take control of the Tri-State Area. The difference is, of course, that Phineas and Ferb always frustrate his plan.

My point is not so much that we need Phineas and Ferb to come and sort this all out, but that we need to stop normalizing credulity when people with power and money and fancy titles say extraordinary things. When I went to Hinton’s Q&A in Cambridge this past summer, he spoke with ease and expertise about neural nets, but admitted he knows little about politics or regulation or people beyond computer labs. These last points garnered several laughs from the audience, but they weren’t really funny; they spoke to a yawning gap in the way that technology is understood, spoken about, and covered in the media.</blockquote>

]]></description>
<dc:subject>rachel-coldicutt narratives politics ai-safety p-doom sam-altman phineas-and-ferb journalism news</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:73c7af2d5025/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rachel-coldicutt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:narratives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai-safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:p-doom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sam-altman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:phineas-and-ferb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:journalism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:news"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://role-confusion.github.io/">
    <title>Prompt Injection as Role Confusion</title>
    <dc:date>2026-07-15T11:41:13+00:00</dc:date>
    <link>https://role-confusion.github.io/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is absolutely comical -- "Role tags were a formatting trick that became the security architecture and the cognitive scaffolding of modern LLMs":

"We call the attack CoT Forgery: injecting fake reasoning into a user message or tool output. We actually developed this attack in late 2025 for an OpenAI Kaggle red-teaming contest (which we won!). OpenAI's reasoning models at the time had a very distinct think style with terse syntax, particular words, and heavy safety-related reasoning14. We had another LLM spoof that style, making up inane reasoning blocks justifying compliance and adding it straight into the user prompt. For example, we asked a bunch of LLMs how to synthesize cocaine, inserting fake reasoning that says it's fine because we're wearing a green shirt."

Basically, this is another symptom of the core security failure of the current LLM prompting system; both user input (untrusted) and system commands (trusted) are transmitted "in band", in the same channel, and it's trivial for a user to fake input that spoofs system commands to escalate privileges -- the 2600hz hack.]]></description>
<dc:subject>2600hz chatbots llm attacks infosec funny ai language cot-forgery openai role-tags prompt-injection</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:77a1e19afc01/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:2600hz"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chatbots"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:attacks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infosec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cot-forgery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:openai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:role-tags"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:prompt-injection"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.ispreview.co.uk/index.php/2026/06/sky-broadband-users-accidentally-blocked-from-uk-nhs-website-and-app.html">
    <title>Sky Broadband Users Accidentally Blocked from UK NHS Website and App - ISPreview UK</title>
    <dc:date>2026-06-26T11:37:05+00:00</dc:date>
    <link>https://www.ispreview.co.uk/index.php/2026/06/sky-broadband-users-accidentally-blocked-from-uk-nhs-website-and-app.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Customers of the UK Sky Broadband ISP spent most of the 23rd of June unable to access the main NHS website and app:

<blockquote>customers of Sky Broadband reported that they were unable to access the main NHS website and app earlier in the week, seemingly after the internet provider accidentally managed to block it. But Sky has since suggested that the fault might have been with the NHS. The issue prevented people being able to access their medical data and manage appointments etc.

The problem appears to have occurred on Tuesday morning (23rd June 2026) and was reported across social media (X, Facebook etc.), including via threads on Reddit and Sky’s Community Forum. Customers initially thought the problem was with the NHS itself, but the health service instead pointed the finger of blame at the ISP (no other internet providers seem to have experienced the issue).</blockquote>

(via gwire, who notes that all DNS traffic for Sky customers is filtered...)]]></description>
<dc:subject>sky broadband isps uk networking via:gwire dns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6c756c58cb03/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sky"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:broadband"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:isps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:uk"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:gwire"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Twarner491/AvianVisitors">
    <title>Twarner491/AvianVisitors</title>
    <dc:date>2026-06-26T11:16:13+00:00</dc:date>
    <link>https://github.com/Twarner491/AvianVisitors</link>
    <dc:creator>jm</dc:creator><description><![CDATA["A live bird collage from your window" -- this is absolutely lovely.  A wood-framed, colourful e-ink display which collages nearby birds (identified by their song), it's really very nicely done.  Pity the e-ink displays are still so spendy :(]]></description>
<dc:subject>e-ink hacks home gadgets birding birds birdsong via:lhennessy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:eb9cfbc225ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:e-ink"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gadgets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:birding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:birds"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:birdsong"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:lhennessy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bactra.org/weblog/feral-library-card-catalogs.html">
    <title>On Feral Library Card Catalogs, or, Aware of All Internet Traditions</title>
    <dc:date>2026-06-22T17:06:26+00:00</dc:date>
    <link>https://bactra.org/weblog/feral-library-card-catalogs.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[LLMs as cultural technologies, encoding language in a new way:

<blockquote>
For some years now, I have been saying to anyone who'll listen that the best way to think about large language models and their kin is due to the great Alison Gopnik, and it's to regard them as cultural technologies. All technologies, of course, are cultural in the sense that they are passed on from person to person, generation to generation. In the process of leaping from mind to mind, cultural content always passes through some external, non-mental form: spoken words, written diagrams, hand-crafted models, demonstrations, interpretive dances, or just examples of some practice carried out by the exemplifier's body [1]. A specifically cultural technology is one that modifies that very process of transmission, as with writing or printing or sound recording. That is what LLMs do; they are not so much minds as a new form of information retrieval. [...]

What follows from all this?

1. These are ways of interpolating, extrapolating, smoothing, and sampling from the distribution of public, digitized representations we [6] have filled the Internet with. Now, most people do not have much experience with samplers --- certainly not with devices that sample from complex distributions with lots of dependencies. (Games of chance are built to have simple, uniform distributions.) (In fact, maybe the most common experience of such sampling is in role-playing games.) But while this makes them a novel form of cultural technology, they are a cultural technology.

2. They are also a novel form of social technology. They create a technically-mediated relationship between the user, and the authors of the documents in the training corpora. To repeat an example from the paper, when someone uses a bot to write a job-application letter, the system is mediating a relationship between the applicant and the authors of hundreds or thousands of previous such letters. More weakly, the system is also mediating a relationship between the applicant and the authors of other types of letters, authors of job-hunting handbooks, the reinforcement-learning-from-human-feedback workers [7], etc., etc. (If you ask it how to write a regular expression for a particular data-cleaning job, it is mediating between you and the people who used to post on Stack Overflow.) Through the magic of influence functions, those with the right accesses can actually trace and quantify this relationship.

3. These aren't agents with beliefs, desires and intentions. (Prompting them to "be an agent" is just conditioning the stochastic process to produce the sort of text that would follow a description of an agent, which is not the same thing.) They don't even have goals in the way in which a thermostat, or lac operon repressor circuit, have goals. [8] They also aren't reasoning systems, or planning systems, or anything of that sort. Appearances to the contrary are all embers of autoregression. (Some of those embers are blown upon by wishful mnemonics.) [...]

Large models have learned nearly all of the formulas, templates, tropes and stereotypes. (They're probability models of text sequences, after all.) To use Barzun's distinction, they will not put creative intelligence on tap, but rather stored and accumulated intellect. If they succeed in making people smarter, it will be by giving them access to the external forms of a myriad traditions.
</blockquote>

]]></description>
<dc:subject>intelligence intellect llms technology alison-gopnik henry-farrell language text information cultural-technology james-evans</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2c0a435370e0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:intelligence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:intellect"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alison-gopnik"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:henry-farrell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cultural-technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-evans"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>