Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 191 Comments
Joined 1 year ago
cake
Cake day: August 13th, 2024

help-circle

  • I don’t happen across Medium very often so I wondered what this sentiment was about.

    Apparently Medium is basically YouTube for bloggers and essayists (with apologies to those who surely think that’s an insulting comparison) and the new CEO messed with the algorithm so much that now writers’ content isn’t being promoted as well as it used to be, and the people who subscribed (or followed, or whatever) aren’t even seeing that content as much any more.

    ~… and it seems there’s no option to get a notification about new content from favourite writer, but maybe I’ve missed it. No “ring that bell” here.~ Edit: When I turned on JavaScript I got a pop-up implying that exists, at least for people who aren’t logged in.

    But as far as I can tell, that doesn’t necessarily mean we should hate the content that’s on there.












  • The SI prefix thing stems from a joke anyway. Allow me to trot out the etymology again:

    Once upon a time in the 1980s, there was created a program for reading ELectronic Mail called Elm.

    Someone created a rival mail reader called Pine, which followed both the tree pun as well as the fact it was a recursive acronym: “Pine is not Elm”.

    Pine had an editor called the Pine Composer or Pico for short. Pico is both a typographical term as well as an SI unit. They may have been going for both. Too perfect a pun to pass up, perhaps.

    Due to licensing uncertainty, someone else created a from-scratch clone of Pico called Nano, cementing the continuation of puns, but in the SI direction.

    And then apparently someone else has decided to get on the bandwagon with Micro.





  • TIL that, at least according to the linked page, YYYY-MM-DD hh:mm:ss (or %Y-%M-%D %h:%m:%s in strftime format) isn’t valid in either system.

    ISO8601 apparently disallows spaces altogether, so that space should be a T for it to qualify there; RFC3399 allows the space, but insists there should be a UTC offset of some kind at the end.

    Unrelatedly, the page’s use of %Z and %z doesn’t match with strftime formatting at all, so there’s at least one other standards problem lurking here.