home.social
  1. Report of investigation into the November 2025 Economic and fiscal outlook publication error
    obr.uk/docs/dlm_uploads/011220

  2. Interesting panel discussion.

    The Nerve roundtable: How can culture fight back in a turbulent world?
    thenerve.news/p/roundtable-cul

  3. After subscribing to The Guardian for several years I'm now two-timing with a month's i subscription before I decide which to continue with.

    So far, the i articles seem just as well-written/researched, less verbose, and without The Guardian's obvious "chip on the shoulder" that becomes tedious after a while.

    Shame about the paywall though, especially as "gift links" don't seem to be supported.

  4. I'm trying out the i app and at least it greys out articles I've read.

  5. Updated my /uses page to reflect the recent switch to i3 on arch and migration from WriteFreely to eleventy.

    underlap.org/uses/

  6. Have you ever paused to consider the lineage of a piece of sofware? How long has it been around and where does it derive from?

    New blog post: Software lineage: Mach ports vs BSD

    underlap.org/software-lineage-

  7. New blog post: Taking the blades SSG for a spin

    underlap.org/blades-ssg

    Thanks to @asynchronaut for bringing blades to my attention.

  8. Wrote a summary of web linking (AKA link relations; think rel="xxx" in a <a/> or <link/> HTML element).

    The piece of the puzzle that's still unclear to me is whether WebFinger has been superseded, or maybe just generally ignored. There doesn't seem to be much adoption (except by Mastodon) or follow-on activity AFAICT.

    wiki.underlap.org/en/link-rela

    /cc @meissa @jsmarr

  9. @henrikjernevad Looks like I'd need to add IndieAuth support to my (WriteFreely) web site before I could use webmention.io. Probably not worth the effort.

  10. @marick Yes, have advantages, but are not without downsides:

    * tags apply to the whole repo, which is awkward for versioning and releasing independent artefacts
    * carbon/money costs can be relatively high when "safe" changes, e.g. to docs or website, trigger expensive CI checks
    * all or nothing in terms of private/public,
    access control (e.g. limiting write access to certain subcomponents), issue management, fork maintenance, and continuous deployment

  11. @iainH gives his perspective on the CICS restructure project: iainhouston.com/restructure_an

    CICS is an IBM transaction processing product which was radically and successfully restructured to reduce the cost of maintenance and enable functional enhancements. I worked on the tail end of the initial restructure project and later helped to factor out several more key components. This was one of the most exciting parts of my career and I'm so grateful I had the opportunity to be involved.

  12. Another nice blog from Matt Stine (via ) on