1. Micah N Gorrell: @BarnabyWalters Those would work as well but would limit it's use to an actual browser. What is wrong with an HTTP header for this?

    @_minego links with the rel semantic can be used both in human-visible markup for improved back-compatibility and quick error-spotting (as well as layering on top of existing solution) and also in HTTP headers for machine-only use

  2. At any given time my web archive HTTPS to HTTP domain ratio is almost exactly 1:10. Right now it’s at 410 HTTP domains and 41 HTTPS domains. Note that this is just the count of the domains I link to (and which link to me), unweighted by the number of actual physical links.

  3. Successfully got both my RPis automatically connecting to WiFi and serving HTTP and SSH over @pagekite. If you’re having trouble setting up SSH over Pagekite, using Interactive Testing is super useful. Turns out I had typed my secret in wrong — oops!

    At least I can not run them headless now and not keep lugging monitor, keyboard etc. into the kitchen (only source of WiFi strong enough for tiny antenna to pick up). Better for my own sanity as well as my housemates’.

  4. I’m rather impressed with guzzlephp.org’s HTTP Link header abstraction. Parsing Link headers and providing a simple API to check for the existence of/fetch links by rel is welcome attention to detail and cements it’s position as the only PHP HTTP client I will likely ever need.

  5. Earlier, aral wittily quipped:

    The CMS I use for my personal sites is called a file system. You might have heard of it.

    I disagree with this premise. Useful and easy as filesystems are, without a wrapper like Jekyll they don’t manage content (resources), they manage representations (typically HTML).

  6. I find it disturbing that the 6th google result for “content negotiation” is an article from 2003 about how it shouldn’t be used. This needs to be changed.