<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/assets/css/rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>dbushell.com (notes)</title>
    <description>David Bushell’s Notes only feed</description>
    <link>https://dbushell.com/notes/</link>
    <lastBuildDate>Sat, 17 Oct 2026 06:44:00 GMT</lastBuildDate>
    <atom:link href="https://dbushell.com/rss.xml" rel="self" type="application/rss+xml"/>
    <author>David Bushell</author>
    <language>en-GB</language>
<item>
  <description>“Rather, I became a physicist to stare at large databases of histograms produced by a Lovecraftian-autocomplete of dubious correctness and say “yeah that’s probably ok I guess” to add to humanity’s knowledge frontier. Why are we even doing all this? - Rikab Gambhir”This whole satirical piece is excellent.</description>
  <link>https://dbushell.com/notes/2026-10-17T06:44Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-17T06:44Z/</guid>
  <pubDate>Sat, 17 Oct 2026 06:44:00 GMT</pubDate>
  <content:encoded><![CDATA[<blockquote><p>Rather, I became a physicist to stare at large databases of histograms produced by a Lovecraftian-autocomplete of dubious correctness and say “yeah that’s probably ok I guess” to add to humanity’s knowledge frontier.</p><p><cite><a href="https://terrytao.wordpress.com/2026/10/15/why-are-we-even-doing-all-this/" rel="noopener noreferrer" target="_blank">Why are we even doing all this?</a> - Rikab Gambhir</cite></p></blockquote><p>This whole satirical piece is excellent.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>I updated my static search fallback to use the no-AI version of DuckDuckGo (sigh). I don’t use Pagefind anymore because I built my own Zig wasm index, but the no-JS fallback remains the same DuckDuckGo form. For searching the rest of the web I pay for Kagi and disable all the slop (sigh). I remembered to update the form-action directive in my content security policy . Apparently I have an old article on HTTP security headers. Speaking of CSP, Google are not content and have invented a new connection allowlists header. I glanced over the spec and it seems reasonable. But this is Google, it’s probably another backdoor for fingerprinting (sigh).</description>
  <link>https://dbushell.com/notes/2026-10-15T05:37Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-15T05:37Z/</guid>
  <pubDate>Thu, 15 Oct 2026 05:37:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>I updated my <a href="https://dbushell.com/2024/11/21/static-search-page-find/#fallback">static search fallback</a> to use the <a href="https://www.stevefrenzel.dev/posts/duckduckgo-no-ai-as-default-search-engine/" rel="noopener noreferrer" target="_blank">no-AI version of DuckDuckGo</a> (sigh). I don’t use Pagefind anymore because I built my own <a href="https://dbushell.com/2025/05/18/search-with-zig-wasm-worker/">Zig wasm index</a>, but the no-JS fallback remains the same DuckDuckGo form.</p><p>For searching the rest of the web I pay for <glossary-term id="--term-kagi"><a href="https://help.kagi.com/kagi/why-kagi/why-pay-for-search.html" rel="noopener noreferrer" target="_blank">Kagi</a></glossary-term> and disable all the slop (sigh).</p><p>I remembered to update the <code>form-action</code> directive in my <glossary-term id="--term-csp"><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP" rel="noopener noreferrer" target="_blank">content security policy</a></glossary-term>. Apparently I have an old article on <a href="https://dbushell.com/2020/02/28/http-security-headers-and-inline-resources/">HTTP security headers</a>.</p><p>Speaking of CSP, Google are not content and have invented a new <a href="https://developer.chrome.com/blog/connection-allowlist-announcement" rel="noopener noreferrer" target="_blank">connection allowlists</a> header. I glanced over the spec and it seems reasonable. But this is Google, it’s probably another <a href="https://wil.to/posts/googles-prompt-api/#:~:text=UPDATED%20OCTOBER%207%2C%202026" rel="noopener noreferrer" target="_blank">backdoor for fingerprinting</a> (sigh).</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>TetraLogical have released an Accessible Components Library. “For every component, we’ve documented the applicable success criteria from the Web Content Accessibility Guidelines (WCAG) 2.2, at levels A, AA, and AAA. We’ve also added our own recommendations for things WCAG doesn’t cover, such as usability when using high contrast themes. Introducing the Accessible Components Library - Craig Abbott”There is a lot to learn from this library. I especially like the Tabs web component. I’ve tried to build similar before and have never been sure if I got it right. This reference is reassuring! I look forward to studying new patterns in future updates.</description>
  <link>https://dbushell.com/notes/2026-10-15T05:15Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-15T05:15Z/</guid>
  <pubDate>Thu, 15 Oct 2026 05:15:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>TetraLogical have released an <a href="https://tetralogical.com/resources/accessible-components-library/" rel="noopener noreferrer" target="_blank">Accessible Components Library</a>.</p><blockquote><p>For every component, we’ve documented the applicable success criteria from the Web Content Accessibility Guidelines (WCAG) 2.2, at levels A, AA, and AAA. We’ve also added our own recommendations for things WCAG doesn’t cover, such as usability when using high contrast themes.</p><p><cite><a href="https://tetralogical.com/blog/2026/10/14/accessible-components-library/" rel="noopener noreferrer" target="_blank">Introducing the Accessible Components Library</a> - Craig Abbott</cite></p></blockquote><p>There is a lot to learn from this library. I especially like the <a href="https://tetralogical.com/resources/accessible-components-library/tabs/" rel="noopener noreferrer" target="_blank">Tabs web component</a>. I’ve tried to build similar before and have never been sure if I got it right. This reference is reassuring! I look forward to studying new patterns in future updates.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>Origami (Weird Web October) by Dan Q is really cool! When I saw the open source repo my first reaction was: liar! Where’s the JavaScript? It’s all inline in index.html and remarkably simple (not the maths). The Unlicense ‘license’ Dan chose is interesting. It waives copyright putting the work into public domain. Since copyright is not easily shaken off, it falls back to a modified MIT license. Copyright should be unwaivable in my opinion. Human rights are inalienable and this protects people against exploitation. Of course, the entire idea of copyright has been peverted and destroyed beyond meaning. So whatever!</description>
  <link>https://dbushell.com/notes/2026-10-14T06:54Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-14T06:54Z/</guid>
  <pubDate>Wed, 14 Oct 2026 06:54:00 GMT</pubDate>
  <content:encoded><![CDATA[<p><a href="https://danq.me/2026/10/14/origami/" rel="noopener noreferrer" target="_blank">Origami (Weird Web October)</a> by Dan Q is really cool! When I saw the <a href="https://github.com/Dan-Q/origami" rel="noopener noreferrer" target="_blank">open source repo</a> my first reaction was: liar! Where’s the JavaScript? It’s all inline in <code>index.html</code> and remarkably simple (not the maths).</p><p>The <a href="https://unlicense.org/" rel="noopener noreferrer" target="_blank">Unlicense</a> ‘license’ Dan chose is interesting. It waives copyright putting the work into public domain. Since copyright is not easily shaken off, it falls back to a modified MIT license. Copyright should be unwaivable in my opinion. Human rights are inalienable and this protects people against exploitation. Of course, the entire idea of copyright has been peverted and destroyed beyond meaning. So whatever!</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>It’s official, Deno is as dead as a dodo. “We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime. Deno is joining Cloudflare - Ryan Dahl”Deno’s decline didn’t go unnoticed. Following Dahl’s silence after half the team was laid off it became clear that his focus was elsewhere. What was left of Deno Land Inc. has been “tweeting AI fantasies and vibe-coding Temu Cloudflare.” — now they’re being assimilated into the real Cloudflare collective. “Ryan and Bert will be leading a new effort to make workerd self-hosting a first-class supported way to build and run apps using the Workers programming model. This will involve merging code and ideas from celld back into workerd. Deno is joining Cloudflare - Kenton Varda and Ryan Dahl”Cloudflare claims to support open source and that “‘Lock-in’ actually hurts” but evidently they’re not keen on open source competition. So Dahl’s pivot to an acquisition paid off† and probably just in time. I felt that an acquisition was unlikely. That was before the celld project, which is what Cloudflare are actually buying here to swiftly consume. Celld was a bit of a ‘left field hail mary’, as the Yanks say. I don’t want to harp on about this but in a Hacker News comment yesterday, Dahl himself now admits: “It has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does. Why reimplement Node? It works. Hacker News: Cloudflare acquires Deno - @rough-sea”I was saying exactly that for years: “Where are those developers? They’re using Node. Maybe Node compatibility is the solution? Nope. It ain’t working. Why would a Node developer move to Deno only to continue using Node APIs and NPM modules? Something’s off (The Deno Package Paradox)”Venture capital led to bad decisions and killed innovation. Now the corporate machine has come to sweep up what’s left. I have thoughts on Cloudflare but I’ll save those for the big blog one day. † At least for Deno’s investors who weren’t seeing any return on the 20-whatever million invested. I bet Cloudflare got 50 cents on the dollar.</description>
  <link>https://dbushell.com/notes/2026-10-10T10:30Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-10T10:30Z/</guid>
  <pubDate>Sat, 10 Oct 2026 10:30:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>It’s official, Deno is as dead as a dodo.</p><blockquote><p>We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime.</p><p><cite><a href="https://deno.com/blog/cloudflare" rel="noopener noreferrer" target="_blank">Deno is joining Cloudflare</a> - Ryan Dahl</cite></p></blockquote><p><a href="https://dbushell.com/2025/04/28/denos-decline/">Deno’s decline</a> didn’t go unnoticed. Following <a href="https://dbushell.com/2026/03/20/denos-decline-and-layoffs/">Dahl’s silence</a> after half the team was laid off it became clear that his focus was elsewhere. What was left of <em>Deno Land Inc.</em> has been <a href="https://dbushell.com/2026/10/03/deno-to-node/#:~:text=tweeting%20AI%20fantasies%20and%20vibe%2Dcoding%20Temu%20Cloudflare."><q>tweeting AI fantasies and vibe-coding Temu Cloudflare.</q></a> — now they’re being assimilated into the real Cloudflare collective.</p><blockquote><p>Ryan and Bert will be leading a new effort to make workerd self-hosting a first-class supported way to build and run apps using the Workers programming model. This will involve merging code and ideas from celld back into workerd.</p><p><cite><a href="https://blog.cloudflare.com/deno-joins-cloudflare/" rel="noopener noreferrer" target="_blank">Deno is joining Cloudflare</a> - Kenton Varda and Ryan Dahl</cite></p></blockquote><p>Cloudflare claims to support open source and that <em>“‘Lock-in’ actually hurts”</em> but evidently they’re not keen on open source <em>competition</em>. So Dahl’s pivot to an acquisition paid off<sup>†</sup> and probably just in time. I felt that an <a href="https://dbushell.com/notes/2026-03-18T07:00Z/">acquisition was unlikely</a>. That was before the <a href="https://github.com/denoland/celld" rel="noopener noreferrer" target="_blank">celld</a> project, which is what Cloudflare are actually buying here to swiftly consume. Celld was a bit of a ‘left field hail mary’, as the Yanks say.</p><p>I don’t want to harp on about this but in a Hacker News comment yesterday, Dahl himself now admits:</p><blockquote><p>It has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does. Why reimplement Node? It works.</p><p><cite><a href="https://news.ycombinator.com/item?id=50023277" rel="noopener noreferrer" target="_blank">Hacker News: Cloudflare acquires Deno</a> - @rough-sea</cite></p></blockquote><p>I was saying exactly that for years:</p><blockquote><p>Where are those developers? They’re using Node. Maybe Node compatibility is the solution? Nope. It ain’t working. Why would a Node developer move to Deno only to continue using Node APIs and NPM modules?</p><p><cite><a href="https://dbushell.com/2024/08/05/the-deno-package-paradox/#somethings-off">Something’s off (The Deno Package Paradox)</a></cite></p></blockquote><p>Venture capital led to bad decisions and killed innovation. Now the corporate machine has come to sweep up what’s left. I have thoughts on Cloudflare but I’ll save those for the big blog one day.</p><p><small><sup>†</sup> At least for Deno’s investors who weren’t seeing any return on the 20-whatever million invested. I bet Cloudflare got 50 cents on the dollar.</small></p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>Kilian Valkhof would like to have a universal pseudo selector in CSS and so would I. It’s not something I knew was necessary until now but I like the idea. That said, I don’t like pseudo-elements. They’re a dead end for style and content. A failure/abuse of the standardisation process to rush things in via CSS.</description>
  <link>https://dbushell.com/notes/2026-10-08T13:32Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-08T13:32Z/</guid>
  <pubDate>Thu, 08 Oct 2026 13:32:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>Kilian Valkhof would <a href="https://kilianvalkhof.com/2026/css-html/id-like-to-have-a-universal-pseudo-selector-in-css/" rel="noopener noreferrer" target="_blank">like to have a universal pseudo selector in CSS</a> and so would I. It’s not something I knew was necessary until now but I like the idea.</p><p>That said, <a href="https://dbushell.com/2025/05/23/pseudo-elements/">I don’t like pseudo-elements.</a> They’re a dead end for style and content. A failure/abuse of the standardisation process to rush things in via CSS.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>The “Declarative Partial Updates” that Dave Rupert writes about in “Recursion is DEAD and HTML killed it” have me intrigued. They’ve talked about them before on Shop Talk. Seems like a powerful addition to HTML. Seems like something I’d use just because I could even though my website is static on a CDN.</description>
  <link>https://dbushell.com/notes/2026-10-07T03:51Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-07T03:51Z/</guid>
  <pubDate>Wed, 07 Oct 2026 03:51:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>The “Declarative Partial Updates” that Dave Rupert writes about in <a href="https://daverupert.com/2026/10/html-recursion/" rel="noopener noreferrer" target="_blank">“Recursion is DEAD and HTML killed it”</a> have me intrigued. They’ve talked about them before on Shop Talk. Seems like a powerful addition to HTML. Seems like something I’d use just because I could even though my website is static on a CDN.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>I receive plenty of email harassment. Mostly from anonymous cowards. Anyone with a blog and public email address in [current year] can probably attest to that experience. Apparently the audacity to prefer not to fund billionaires really upsets people? Several of those people were even able to form a coherent sentence. A few latched on to my “Play Synthesised Audio” button as the ultimate “gotcha!” The Web Speech API and SpeechSynthesis I used have been around since 2018. Back when “machine learning” wasn’t designed to violate humanity. As far as I know these APIs are old school text-to-speech (and sound like it). However, I am no longer confident. I can’t test or trust all browsers &amp; operating systems. The button was a “nice to have” feature but it’s not worth the hassle.</description>
  <link>https://dbushell.com/notes/2026-10-05T14:32Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-05T14:32Z/</guid>
  <pubDate>Mon, 05 Oct 2026 14:32:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>I receive plenty of email harassment. Mostly from anonymous cowards.</p><p>Anyone with a blog and public email address in [current year] can probably attest to that experience. Apparently the audacity to <a href="https://dbushell.com/ai/">prefer <strong>not</strong> to fund billionaires</a> really upsets people?</p><p>Several of those people were even able to form a coherent sentence. A few latched on to my <a href="https://dbushell.com/2025/07/26/text-to-speech-synthesis/">“Play Synthesised Audio” button</a> as the ultimate “gotcha!”</p><p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API" rel="noopener noreferrer" target="_blank">Web Speech API</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/API/SpeechSynthesis" rel="noopener noreferrer" target="_blank"><code>SpeechSynthesis</code></a> I used have been around since 2018. Back when “machine learning” wasn’t designed to violate humanity. As far as I know these APIs are old school text-to-speech (and sound like it). However, I am no longer confident. I can’t test or trust all browsers &amp; operating systems.</p><p>The button was a “nice to have” feature but it’s not worth the hassle.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>““The Wheel of Time turns, and Ages come and pass, [web developers are surveyed,] leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave birth to it comes again.” The Wheel of Time - Robert Jordan”</description>
  <link>https://dbushell.com/notes/2026-10-05T08:46Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-05T08:46Z/</guid>
  <pubDate>Mon, 05 Oct 2026 08:46:00 GMT</pubDate>
  <content:encoded><![CDATA[<blockquote><p>“The Wheel of Time turns, and Ages come and pass, [web developers are surveyed,] leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave birth to it comes again.”</p><p><cite>The Wheel of Time - Robert Jordan</cite></p></blockquote>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>If you’re reading this my website is now built and deployed with Node. If not… well, I’m in for a miserable weekend!</description>
  <link>https://dbushell.com/notes/2026-10-02T17:01Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-10-02T17:01Z/</guid>
  <pubDate>Fri, 02 Oct 2026 17:01:00 GMT</pubDate>
  <content:encoded><![CDATA[<pre data-lang="sh" tabindex="0" translate="no" id="pre-2d735ea5"><code><span class="line"><span class="syntax-c01639ae">brew</span><span class="space"> </span><span class="syntax-e661ac3e">uninstall</span><span class="space"> </span><span class="syntax-e661ac3e">deno</span></span></code></pre><p>If you’re reading this my website is now built and deployed with Node.</p><p>If not… well, I’m in for a miserable weekend!</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>It’s safe to say that Apple broke copy/paste on macOS 27. I thought it was just me. Like a sudden onset skill issue, or a crumb under my keyboard. The amount of “I thought it was just me!” on the socials suggest we’re not going crazy. Marcin Wichary says Apple Notes is a problem: “On top of that, the last version of Apple Notes on my macOS occasionally breaks copy/paste (!), which led to some writing loss on my part. (If you cut from one note intending to paste in another, and realize nothing was saved in the clipboard, you lost the text forever.) “I trust in TextEdit.” - Marcin Wichary”That was shared in February. I’m a big Notes user, it may well be the common denominator in all my copy/paste failures. I’m keeping track to see if it happens without Notes involved. Notes is the only app in Apple’s ecosystem that I still use. Bugs and sync failures elsewhere has led me to find alternatives for everything else. Apple fanboys’ new coping mantra has been that “Golden Gate” is a “Snow Leopard” release. Meaning that lack of exciting new features were made up by fixes and stability. I’m not sure it was true back then, it’s certainly not today. Update: oh dear, “macOS Golden Gate Is a Buggy Mess”</description>
  <link>https://dbushell.com/notes/2026-09-29T04:40Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-29T04:40Z/</guid>
  <pubDate>Tue, 29 Sep 2026 04:40:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>It’s safe to say that Apple broke copy/paste on macOS 27.</p><p>I thought it was just me. Like a sudden onset skill issue, or a crumb under my keyboard.</p><p>The amount of <em>“I thought it was just me!”</em> on the socials suggest we’re not going crazy.</p><p>Marcin Wichary says Apple Notes is a problem:</p><blockquote><p>On top of that, the last version of Apple Notes on my macOS occasionally breaks copy/paste (!), which led to some writing loss on my part. (If you cut from one note intending to paste in another, and realize nothing was saved in the clipboard, you lost the text forever.)</p><p><cite><a href="https://unsung.aresluna.org/i-trust-in-textedit/#:~:text=On%20top%20of%20that%2C%20the%20last%20version%20of%20Apple%20Notes%20on%20my%20macOS%20occasionally%20breaks%20copy/%E2%80%8Bpaste" rel="noopener noreferrer" target="_blank">“I trust in TextEdit.”</a> - Marcin Wichary</cite></p></blockquote><p>That was shared in February. I’m a big Notes user, it may well be the common denominator in all my copy/paste failures. I’m keeping track to see if it happens without Notes involved. Notes is the only app in Apple’s ecosystem that I still use. Bugs and sync failures elsewhere has led me to find alternatives for everything else.</p><p>Apple fanboys’ new coping mantra has been that “Golden Gate” is a “Snow Leopard” release. Meaning that lack of exciting new features were made up by fixes and stability. I’m not sure it was true back then, it’s certainly not today.</p><p><strong>Update:</strong> oh dear, <a href="https://www.squareorbits.com/blog/2026/09/macos-golden-gate-is-a-buggy-mess/" rel="noopener noreferrer" target="_blank">“macOS Golden Gate Is a Buggy Mess”</a></p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>I don’t mean to immediately renege my plan to largely ignore AI stuff but “The AI Artist Paradox” by Heydon is solid logic I appreciate. I’ve never been protective over “art”. Anything can be “art”; doesn’t mean it has any value. Heydon’s logic though is that however you cut it, the prompter can never be considered the artist. Makes sense to me.</description>
  <link>https://dbushell.com/notes/2026-09-28T08:15Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-28T08:15Z/</guid>
  <pubDate>Mon, 28 Sep 2026 08:15:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>I don’t mean to immediately <a href="https://dbushell.com/2026/09/28/leaving-them-behind/">renege my plan</a> to largely ignore AI stuff but <a href="https://heydonworks.com/article/the-ai-art-paradox/" rel="noopener noreferrer" target="_blank">“The AI Artist Paradox”</a> by <strong>Heydon</strong> is solid logic I appreciate. I’ve never been protective over “art”. Anything can be “art”; doesn’t mean it has any value. Heydon’s logic though is that however you cut it, the prompter can never be considered the artist. Makes sense to me.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>My latest post “Shin honkaku” has a fancy new typographic header. It’s progressively enhanced (for reasons) so only supporting browsers (Chromium, for now) will see it. The inverted colours come from my custom dark mode experiment. The jiggery-pokery in my build system was quite the challenge that only I shall appreciate. Hopefully though you’ll enjoy the occasional design variety it allows. I don’t plan every post to have a unique style, but it’s nice to have the ability without too much hassle. It doesn’t break RSS either, unlike my previous experiments!</description>
  <link>https://dbushell.com/notes/2026-09-28T05:49Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-28T05:49Z/</guid>
  <pubDate>Mon, 28 Sep 2026 05:49:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>My latest post <a href="https://dbushell.com/2026/09/28/shin-honkaku/">“Shin honkaku”</a> has a fancy new typographic header. It’s progressively enhanced (for reasons) so only supporting browsers (Chromium, for now) will see it.</p><p>The inverted colours come from my <a href="https://dbushell.com/2026/07/16/choose-your-own-dark-mode/">custom dark mode experiment</a>. The jiggery-pokery in my build system was quite the challenge that only I shall appreciate. Hopefully though you’ll enjoy the occasional design variety it allows.</p><p>I don’t plan every post to have a unique style, but it’s nice to have the ability without too much hassle. It doesn’t break RSS either, unlike my previous experiments!</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>A few people suggested Radicle so I listed it as a GitHub alternative. Well it turns out Radicle is not a serious project. “Two critical security vulnerabilities in the network protocol used by Radicle nodes were reported. Disclosure of Vulnerability in the Network Protocol - Radicle”Kostis Maninakis discovered a major vulnerability. “As it turns out, after the handshake, everything the two nodes say to each other goes over the plain TCP socket unencrypted: gossip, repository ids, the addresses of other nodes, and the Git objects themselves, private repositories included. Vulnerability disclosure: Radicle nodes send private repositories in cleartext - Kostis Maninakis”I never looked at how Radicle was supposed to work, but the official report suggests the developers thought data was encrypted? Radicle’s plans are to replace the underlying networking protocol. This will be a gruelling “backwards-incompatible” fix. Oh dear… How can anyone trust Radicle after this? I’m sorry, but if you’re that careless, clueless even, is it even responsible to continue the project? That’s harsh to say but we’re talking about security. If you don’t have the expertise don’t get in the game. The only way I’d consider Radicle 2.0 is if multiple 3rd-party experts audited the network. Shame, because the idea sounded cool.</description>
  <link>https://dbushell.com/notes/2026-09-24T05:10Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-24T05:10Z/</guid>
  <pubDate>Thu, 24 Sep 2026 05:10:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>A few people suggested Radicle so I listed it as a <a href="https://dbushell.com/2026/04/29/github-is-sinking/">GitHub alternative</a>.</p><p>Well it turns out Radicle is not a serious project.</p><blockquote><p>Two critical security vulnerabilities in the network protocol used by Radicle nodes were reported.</p><p><cite><a href="https://radicle.dev/2026/09/23/disclosure-of-vulnerability-in-network-protocol" rel="noopener noreferrer" target="_blank">Disclosure of Vulnerability in the Network Protocol</a> - Radicle</cite></p></blockquote><p>Kostis Maninakis discovered a major vulnerability.</p><blockquote><p>As it turns out, after the handshake, everything the two nodes say to each other goes over the plain TCP socket unencrypted: gossip, repository ids, the addresses of other nodes, and the Git objects themselves, private repositories included.</p><p><cite><a href="https://maninak.com/blog/radicle-cleartext-transport-vulnerability/" rel="noopener noreferrer" target="_blank">Vulnerability disclosure: Radicle nodes send private repositories in cleartext</a> - Kostis Maninakis</cite></p></blockquote><p>I never looked at how Radicle was supposed to work, but the official report suggests the developers thought data was encrypted? Radicle’s plans are to replace the underlying networking protocol. This will be a gruelling “backwards-incompatible” fix.</p><p>Oh dear… How can anyone trust Radicle after this? I’m sorry, but if you’re that careless, clueless even, is it even responsible to continue the project? That’s harsh to say but we’re talking about security. If you don’t have the expertise don’t get in the game. The only way I’d consider Radicle 2.0 is if multiple 3rd-party experts audited the network.</p><p>Shame, because the idea sounded cool.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>I’m considering if I should replace my AI policy with simple: “No, never.” As I noted at the end of “I said no and Apple said yes” it’s impossible to keep up with this bullshit. Every day there is a new atrocity. Furthermore there is no worthwhile career in AI-driven development. That has become abundantly clear. The entire AI industry is driving to dehumanise and commoditise labour. I need to add “never” to my policy at the very least. I’ll probably edit it a little shorter.</description>
  <link>https://dbushell.com/notes/2026-09-22T18:36Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-22T18:36Z/</guid>
  <pubDate>Tue, 22 Sep 2026 18:36:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>I’m considering if I should replace my <a href="https://dbushell.com/ai/">AI policy</a> with simple: “No, never.”</p><p>As I noted at the end of <a href="https://dbushell.com/2026/09/22/apple-intelligence/">“I said no and Apple said yes”</a> it’s impossible to keep up with this bullshit. Every day there is a new atrocity.</p><p>Furthermore there is no worthwhile career in AI-driven development. That has become abundantly clear. The entire AI industry is driving to dehumanise and commoditise labour. I need to add “never” to my policy at the very least.</p><p>I’ll probably edit it a little shorter.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>The plan was to read Seishi Yokomizo but two different authors caught my attention: The Moai Island Puzzle - Alice Arisugawa The Devotion of Suspect X - Keigo Higashino Moai Island was great. Perhaps my second favourite of the shin honkaku genre behind The Tokyo Zodiac Murders. I had somewhat of an idea of how events unfolded but I fell for a red herring and totally misidentified the killer. The explanation of why a certain character took a certain journey around the island is clever. Suspect X isn’t a whodunit but a how-dunit. It begins with the murder and then follows both the murderer and the detectives as the cover-up unravels. The story was well structured and if you’re attentive things don’t quite add up. I’d give this book five stars but the very last page ruined it for me! I don’t think that ending was necessary. I appreciate these books being short (compared to my usual fantasy choices). I suppose there is only so long you can draw out a mystery.</description>
  <link>https://dbushell.com/notes/2026-09-19T06:00Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-19T06:00Z/</guid>
  <pubDate>Sat, 19 Sep 2026 06:00:00 GMT</pubDate>
  <content:encoded><![CDATA[<p><a href="https://dbushell.com/notes/2026-09-13T11:02Z/">The plan</a> was to read Seishi Yokomizo but two different authors caught my attention:</p><ul><li><a href="https://www.goodreads.com/book/show/29579674-the-moai-island-puzzle" rel="noopener noreferrer" target="_blank">The Moai Island Puzzle</a> - Alice Arisugawa</li><li><a href="https://www.goodreads.com/book/show/8686068-the-devotion-of-suspect-x" rel="noopener noreferrer" target="_blank">The Devotion of Suspect X</a> - Keigo Higashino</li></ul><p><em>Moai Island</em> was great. Perhaps my second favourite of the <em>shin honkaku</em> genre behind <a href="https://dbushell.com/notes/2026-09-06T06:05Z/">The Tokyo Zodiac Murders</a>. I had somewhat of an idea of how events unfolded but I fell for a red herring and totally misidentified the killer. The explanation of why a certain character took a certain journey around the island is clever.</p><p><em>Suspect X</em> isn’t a whodunit but a how-dunit. It begins with the murder and then follows both the murderer and the detectives as the cover-up unravels. The story was well structured and if you’re attentive things don’t quite add up. I’d give this book five stars but the very last page ruined it for me! I don’t think that ending was necessary.</p><p>I appreciate these books being short (compared to my usual fantasy choices). I suppose there is only so long you can draw out a mystery.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>“Let me make it clear: without people at the top of their game sharing their experience and knowledge — regardless of whatever “game changing” technology is in place — we are pulling up the ladders and committing our industry to stagnation and death. We’ve already fucked it up over the last few years for junior developers by instead of investing in them, playing the slot machines (also known as LLMs) to — you guessed it — make the money number go up, but there’s still hope for recovery. You’ll miss publishers when they’re gone - Andy Bell”CSS-Tricks is dead. Smashing Magazine is sloppy. Piccalilli is struggling. Anyone remember .NET magazine? The “web whetstones” I depend on to stay sharp are falling one by one. Master.dev Blog is going strong with authors like Chris Coyier and Temani Afif. Checking my RSS feeds I don’t see other regular large publishers. Most blogs I subscribe to are individual developers. Many of them have gone quiet too. I’m hanging in there! I like a distributed web but I see the value of publications.</description>
  <link>https://dbushell.com/notes/2026-09-18T09:32Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-18T09:32Z/</guid>
  <pubDate>Fri, 18 Sep 2026 09:32:00 GMT</pubDate>
  <content:encoded><![CDATA[<blockquote><p>Let me make it clear: without people at the top of their game sharing their experience and knowledge — regardless of whatever “game changing” technology is in place — we are pulling up the ladders and committing our industry to stagnation and death. We’ve already fucked it up over the last few years for junior developers by instead of investing in them, playing the slot machines (also known as LLMs) to — you guessed it — make the money number go up, but there’s still hope for recovery.</p><p><cite><a href="https://bell.bz/youll-miss-publishers-when-theyre-gone/" rel="noopener noreferrer" target="_blank">You’ll miss publishers when they’re gone</a> - Andy Bell</cite></p></blockquote><ul><li><a href="https://dbushell.com/notes/2026-09-15T04:59Z/">CSS-Tricks is dead.</a></li><li><a href="https://dbushell.com/notes/2026-09-10T06:14Z/">Smashing Magazine is sloppy.</a></li><li><a href="https://piccalil.li/" rel="noopener noreferrer" target="_blank">Piccalilli</a> is struggling.</li><li>Anyone remember .NET magazine?</li></ul><p>The <a href="https://dbushell.com/2026/05/18/web-whetstone/">“web whetstones”</a> I depend on to stay sharp are falling one by one.</p><p><a href="https://blog.master.dev/" rel="noopener noreferrer" target="_blank">Master.dev Blog</a> is going strong with authors like Chris Coyier and Temani Afif. Checking my RSS feeds I don’t see other regular large publishers. Most blogs I subscribe to are individual developers. Many of them have gone quiet too. I’m hanging in there! I like a distributed web but I see the value of publications.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>Apple’s daily harassment beat me into submission. I installed iOS 27 and macOS 27. I was told they’re both an improvement over 26 with less of the glasshole nonsense. I dialled back every setting I could and macOS 27 is fine, I guess. The stupid glass bubbles everywhere scream for attention. That’s the entire design aesthetic of Liquid Glass — pointless animations and glossy effects that beg for your eyeballs. Apple says it “brings more focus to content” but the exact opposite is true. “Look at me I’m glass!” it screams as it literally pushes content away requiring more wasted space. Apple reminds you at every glance that they own the system. Apple’s icons have been discussed by Tonsky and Nielsen — they’re bad! The UI is full of meaningless abstract shapes with no label (sometimes not even a tooltip). iOS 27 on my iPhone 12 performs like shit now. Just like the Apple TV glass update I’d already mistakenly applied. I’m not a big mobile user so whatever. I cancelled my Apple One subscription so the TV is just an Infuse x Jellyfin player now. TL;DR: tolerable but a step backwards.</description>
  <link>https://dbushell.com/notes/2026-09-16T05:01Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-16T05:01Z/</guid>
  <pubDate>Wed, 16 Sep 2026 05:01:00 GMT</pubDate>
  <content:encoded><![CDATA[<p><a href="https://dbushell.com/2026/08/20/ruminations-on-notifications/">Apple’s daily harassment</a> beat me into submission. I installed iOS 27 and macOS 27. I was told they’re both an improvement over 26 with less of the <a href="https://dbushell.com/notes/2025-06-10T05:25Z/">glasshole nonsense</a>.</p><p>I dialled back every setting I could and macOS 27 is fine, I guess.</p><figure class="Image"><img src="https://dbushell.com/images/blog/2026/macos-27-finder.avif" alt="macOS 27 Finder toolbar and tabs." width="580" height="130" decoding="async" fetchpriority="low" loading="lazy" id="--img-1a4b7129"/></figure><p>The stupid glass bubbles everywhere <strong>scream for attention.</strong> That’s the entire design aesthetic of <smart-arse>Liquid Glass</smart-arse> — pointless animations and glossy effects that beg for your eyeballs. Apple says it <a href="https://www.apple.com/uk/newsroom/2025/06/apple-introduces-a-delightful-and-elegant-new-software-design/#:~:text=brings%20more%20focus%20to%20content" rel="noopener noreferrer" target="_blank">“brings more focus to content”</a> but the exact opposite is true. <em>“Look at me I’m glass!”</em> it screams as it literally pushes content away requiring more wasted space. Apple reminds you at every glance that they own the system.</p><p>Apple’s icons have been discussed by <a href="https://tonsky.me/blog/tahoe-icons/" rel="noopener noreferrer" target="_blank">Tonsky</a> and <a href="https://blog.jim-nielsen.com/2026/rotten-macos-icon-design/" rel="noopener noreferrer" target="_blank">Nielsen</a> — they’re bad! The UI is full of meaningless abstract shapes with no label (sometimes not even a tooltip).</p><p>iOS 27 on my iPhone 12 performs like shit now. Just like the Apple TV glass update I’d already mistakenly applied. I’m not a big mobile user so whatever. I cancelled my Apple One subscription so the TV is just an <a href="https://firecore.com/infuse" rel="noopener noreferrer" target="_blank">Infuse</a> x <a href="https://jellyfin.org/" rel="noopener noreferrer" target="_blank">Jellyfin</a> player now.</p><p>TL;DR: tolerable but a step backwards.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>Not long ago I was fooled into thinking Digital Ocean had done right by CSS-Tricks. Turns out it was all Geoff and the authors working for free? Digital Ocean would rather fund outright fascism than their own publication.</description>
  <link>https://dbushell.com/notes/2026-09-15T04:59Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-15T04:59Z/</guid>
  <pubDate>Tue, 15 Sep 2026 04:59:00 GMT</pubDate>
  <content:encoded><![CDATA[<p><a href="https://dbushell.com/notes/2026-07-16T07:02Z/">Not long ago</a> I was fooled into thinking Digital Ocean had done right by <a href="https://css-tricks.com/" rel="noopener noreferrer" target="_blank">CSS-Tricks</a>. <a href="https://vale.rocks/micros/20260915-0135" rel="noopener noreferrer" target="_blank">Turns out</a> it was all <a href="https://geoffgraham.me/why-css-tricks-has-been-quiet/" rel="noopener noreferrer" target="_blank">Geoff</a> and the authors working for free? Digital Ocean would rather fund <a href="https://tante.cc/2026/09/11/power-grab/" rel="noopener noreferrer" target="_blank">outright fascism</a> than their own publication.</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
<item>
  <description>Aha! Yes! I’m called out at the start of Slop Talk Show #732 for last week’s note :) This is a proud achievement! How does one go about framing an audio clip to display in my office? Have the transcript framed and printed? I’m sure I’ve been mentioned on earlier episodes for more valuable contributions to the industry but I’ll take what I can get in this economy!</description>
  <link>https://dbushell.com/notes/2026-09-14T14:05Z/</link>
  <guid isPermaLink="true">https://dbushell.com/notes/2026-09-14T14:05Z/</guid>
  <pubDate>Mon, 14 Sep 2026 14:05:00 GMT</pubDate>
  <content:encoded><![CDATA[<p>Aha! Yes! I’m called out at the start of <a href="https://shoptalkshow.com/732/" rel="noopener noreferrer" target="_blank">Slop Talk Show #732</a> for <a href="https://dbushell.com/notes/2026-09-03T06:55Z/">last week’s note</a> :)</p><p>This is a proud achievement! How does one go about framing an audio clip to display in my office? Have the transcript framed and printed?</p><p>I’m sure I’ve been mentioned on earlier episodes for more valuable contributions to the industry but I’ll take what I can get in this economy!</p>
<hr>
<p>
Thanks for reading! Follow me on <a href="https://dbushell.com/mastodon/">Mastodon</a> and <a href="https://dbushell.com/bluesky/">Bluesky</a>.
Subscribe to my <a href="https://dbushell.com/rss.xml">Blog</a> and <a href="https://dbushell.com/notes/rss.xml">Notes</a> or <a href="https://dbushell.com/merge/rss.xml">Combined</a> feeds.
</p>
]]></content:encoded>
</item>
</channel>
</rss>
