<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Personal Blog of 256</title>
    <link>https://256-32.com/blog</link>
    <description>Relentless verbiage.</description>
    <language>en-GB</language>
    <item>
      <title>Reasoning Realm V1.0.0</title>
      <link>https://256-32.com/blog/7</link>
      <pubDate>Fri, 04 Sep 2026 16:30:56 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-09-04&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;My &lt;a href=&quot;/blog/0&quot;&gt;first blog post&lt;/a&gt; was about revisiting the code of Reasoning Realm, after an 8 year hiatus. That was just 1 small change, though, and over the last few weeks I&apos;ve been revisiting it properly. It&apos;s now polished enough for me to declare V1.0.0 done.&lt;/p&gt;
&lt;p&gt;There were a lot of problems with the code. One that stands out to me is the way the selection tool worked; it had plenty of bugs, and its state was represented with 2 booleans (effectively 3 since the active tool was also checked). I tried to fix the mess by adding another boolean before realising this&apos;d make more sense as an enum, representing the current state of the selection. JavaScript doesn&apos;t have enums so I just used a string (selState in the V1.0.0 source), which was close enough.&lt;/p&gt;
&lt;p&gt;Replacing the booleans with an &quot;enum&quot; suddenly made everything far easier to handle, and less buggy. There&apos;s probably some deep, insightful message here about experience giving you knowledge of different approaches and the intuition to know which one to use.&lt;/p&gt;
&lt;p&gt;Anyway, I remember working on Reasoning Realm back in 2016-2018, and encountering one particular bug, which seemed almost intractable to me, until, after a great amount of investigation and confusion, I figured out it was because a function had a for loop with a variable called &quot;i&quot;, and within that loop it called another function that also had a variable with the same name, and they collided. Instead of realising that I should&apos;ve used the &quot;var&quot; keyword to make them local, I blamed JS, thinking it poorly designed, and just gave the variables different names. Pretty much every variable in the entire codebase was global, even when they definitely shouldn&apos;t&apos;ve been.&lt;/p&gt;
&lt;p&gt;In retrospect, was JS in the wrong here? Maybe; Lua doesn&apos;t have this particular problem, although even in Lua, non-iterator variables are global by default, like JS. I still think I should&apos;ve been more careful about criticising JS for things I didn&apos;t understand.&lt;/p&gt;
&lt;p&gt;I also remember being confused by the fact that assigning one array to another didn&apos;t copy it, which of course does not confuse me anymore. I &quot;solved&quot; that &quot;problem&quot; by using .slice() for 1D arrays, sometimes pointlessly, and for 2D arrays:&lt;/p&gt;
&lt;pre&gt;clipboard = JSON.parse(JSON.stringify(rectCellList));&lt;/pre&gt;&lt;p&gt;I don&apos;t use that anymore.&lt;/p&gt;
&lt;p&gt;It feels nice to now be able to say I&apos;ve been working on a project for 10 years. It makes me feel like a real hacker.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Slop Star</title>
      <link>https://256-32.com/blog/6</link>
      <pubDate>Thu, 20 Aug 2026 17:11:21 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-08-20&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;For reasons that are beyond me, corporations have decided to use a four-pointed star as the symbol of machine learning. Every time I see it, it triggers a Pavlovian fight-or-flight response in me.&lt;/p&gt;
&lt;p&gt;They didn&apos;t invent the symbol, which makes it worse, because four-pointed stars occur all over the place, so I keep fucking seeing them unexpectedly, in perfectly innocent contexts, and it spikes my cortisol. This is exactly what Hitler did to the swastika.&lt;/p&gt;
&lt;p&gt;They&apos;ve done it with words, too. Critical keystones of my lexicon have been tainted. Agent. Summary. Token. Grok. Training. Datacentre. Assistant.&lt;/p&gt;
&lt;p&gt;Decades from now, after civilisation collapses, I&apos;ll still see a slop star in the wreckage every so often and have war flashbacks to the enshittocene.&lt;/p&gt;</description>
    </item>
    <item>
      <title>First Time Petting a Dog</title>
      <link>https://256-32.com/blog/5</link>
      <pubDate>Fri, 31 Jul 2026 21:22:14 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-07-31&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;I&apos;ve managed to make it to my mid-20s without ever petting a dog, or interacting with one in basically any way. I never grew up with dogs, and as a child I had a fear of them. As I got older I became unafraid, but still tried to avoid them.&lt;/p&gt;
&lt;p&gt;This morning, though, I was walking a footpath beside a brook when I encountered an old lady walking 2 dogs, without leashes, who approached me, barking. I tried to walk around in the hope that they&apos;d avoid me, but they persisted. The lady then had me pet them and feed them, and I was pleasantly surprised by how friendly they were. They stopped barking when I started petting them. This is the final nail in the coffin of my fear of dogs.&lt;/p&gt;
&lt;p&gt;I still prefer cats though. Maybe I&apos;m a Derse dreamer.&lt;/p&gt;
&lt;p&gt;:3&lt;/p&gt;</description>
    </item>
    <item>
      <title>1 Year of Age Verification</title>
      <link>https://256-32.com/blog/4</link>
      <pubDate>Sat, 25 Jul 2026 15:44:08 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-07-25&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;It&apos;s been 1 year today since the generously-named Online Safety Act&apos;s age verification duties went into effect in the UK. The widespread outrage about it seems to have died down, and the country is continuing on the normal trajectory of slow, painful degradation of privacy and free speech.&lt;/p&gt;
&lt;p&gt;I have still never verified my age and never will. If I turn off my VPN, plenty of websites become unusable (if they weren&apos;t already unusable to me due to requiring JS), either because they require me to doxx myself or because they outright block the UK (like Imgur and SpaceHey). There&apos;s an old list of sites that died or blocked the UK &lt;a href=&quot;https://onlinesafetyact.co.uk/in_memoriam/&quot;&gt;here&lt;/a&gt;, although it&apos;s presumably outdated and certainly incomplete.&lt;/p&gt;
&lt;p&gt;I&apos;ve barely ever gotten any age verification prompts, though, not because they aren&apos;t common, but because I don&apos;t use websites that require them (other than through alternative front-ends). There are still plenty of small sites that exist outside the surveillance capitalist panopticon, like the one I&apos;m posting this on, and I&apos;m sure they&apos;ll continue to exist in the future.&lt;/p&gt;
&lt;p&gt;Retreating into the &quot;nerd&quot; corners of the internet seems to be the best survival strategy for the modern web. It&apos;s like Eternal September has been reversed, not because of computer-illiterate people leaving the internet, but because of them sticking to a small number of mainstream sites, leaving the rest of the internet for computer people.&lt;/p&gt;
&lt;p&gt;As for my own site, I have made no attempt to even care about the OSA. I don&apos;t care whether my site complies with it. I&apos;m not digging through a mountain of deliberately impenetrable, dense legalese written by authoritarians simply so I can run a blog. Besides, when a law is sufficiently unjust, you have a moral obligation to disobey it.&lt;/p&gt;
&lt;p&gt;Anyway, I predict that everything will keep getting worse. The general public will become more and more supportive of mass surveillance, laws will get stricter and we&apos;ll have to start hosting hidden services on the TOR network or I2P. Then they&apos;ll make those illegal, and my 1337 hacksaw cyberpunk fantasy world will begin.&lt;/p&gt;
&lt;p&gt;It&apos;ll be like The Matrix. Or V for Vendetta. Or maybe Tron?</description>
    </item>
    <item>
      <title>De-Americanisation</title>
      <link>https://256-32.com/blog/3</link>
      <pubDate>Fri, 03 Jul 2026 17:33:46 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-07-03&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;I grew up on the English-speaking internet, where everyone is American, and as such have unthinkingly absorbed a bunch of Americanisms. More recently I&apos;ve been trying to un-learn them, but they seem to be endless.&lt;/p&gt;
&lt;p&gt;Some are obvious. I once found a preserved chat-log from years ago where I spelt colour without a U, which I definitely don&apos;t do anymore. Some are more subtle, like the spelling of defence and cancelled, or grammatical constructions such as &quot;how it looks like&quot;. The worst ones are probably the cultural and political Americanisms, like implicitly assuming that Parliament works like the US congress or something.&lt;/p&gt;
&lt;p&gt;I think the most dramatic de-Americanisation effort I&apos;ve done, though, is my realisation earlier this year that the British spelling of programme can be used even when talking about software, and subsequent replacement of every instance of &quot;program&quot; with &quot;programme&quot; throughout this site. I did this shortly before the site went live. I even changed the comments and variable names in source code.&lt;/p&gt;
&lt;p&gt;That said, I think the best way to de-Americanise oneself is not to try and consciously enumerate every Americanism (although this is nonetheless a worthwhile effort), but to expose oneself to more British (or wherever you&apos;re from) media, which is what I&apos;ve been trying to do.&lt;/p&gt;
&lt;p&gt;It&apos;s interesting that the great promise of the internet, that it would eradicate borders and bring humanity together, is now the one thing I want to avoid. It&apos;s also interesting that I&apos;m writing this on the eve of the semiquincentennial of the rogue colonies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>This is not the Old Web</title>
      <link>https://256-32.com/blog/2</link>
      <pubDate>Sat, 06 Jun 2026 14:06:53 +0100</pubDate>
      <description>&lt;p&gt;&lt;b&gt;2026-06-06&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;I frequently see people use the term &quot;new web&quot; or &quot;modern web&quot; to refer to mainstream sites, with phone-centric web design and mountains of JS you have to run for basic functionality, all funded by surveillance capitalism. You know, 5 websites all filled with screenshots of the other 4. They&apos;re very similar to each other because they have the same advertising-based incentive structure.&lt;/p&gt;
&lt;p&gt;People also use the term &quot;old web&quot; to refer to small independent sites, with a different funding model or more often no funding at all, implying that they&apos;re some sort of ancient relic still ambling along, even if they were created recently and reflect a fundamentally novel culture.&lt;/p&gt;
&lt;p&gt;I think this old/new distinction is a hold-over from back when social media were new. Like all those towns and cities with &quot;new&quot; in the name that are hundreds of years old. Or New Super Mario Bros., which is probably considered a retro game by now.&lt;/p&gt;
&lt;p&gt;Mainstream social media &lt;b&gt;are&lt;/b&gt; the old web. They&apos;re the massive, traditional, old-fashioned incumbents who are currently falling apart under their own weight, too large and too slow to adapt to problems of their own making, being overtaken, at least in useability and value provided, by smaller sites.&lt;/p&gt;
&lt;p&gt;If this were &lt;i&gt;really&lt;/i&gt; the old old web, we wouldn&apos;t be using HTTPS, for starters. The technical and social elements of modern small sites are massively different from the web of the 2000s when I was a child.&lt;/p&gt;
&lt;p&gt;Whatever you call it, this is not the old web.</description>
    </item>
  </channel>
</rss>
