Linkdump for August 1st through September 1st

Sometime between August 1st and September 1st, I thought this stuff was interesting. You might think so too!

  • The P-I error that changed Seattle history: "Occasionally, newspapers report factual errors. A well-intentioned interview subject gives bad information, a name is spelled wrong, a breaking news story is inadvertently peppered with grammatical errors. But no incorrect newspaper story has had a bigger impact on Seattle history than one published June 7, 1889."
  • 98.6 degrees is a normal body temperature, right? Not quite: “Forget everything you know about normal body temperature and fever, starting with 98.6. That’s an antiquated number based on a flawed study from 1868 (yes, 150 years ago). The facts about fever are a lot more complicated.”
  • The “I Am Steve Rogers” Joke in ‘Avengers: Infinity War’ Is the Definitive Captain America Moment: That’s who Captain America is, a man who listens to and believes in people when they tell him who they are. That’s a lesson we all should take away from that moment.
  • The Bullshit Web: “An honest web is one in which the overwhelming majority of the code and assets downloaded to a user’s computer are used in a page’s visual presentation, with nearly all the remainder used to define the semantic structure and associated metadata on the page. Bullshit — in the form of CPU-sucking surveillance, unnecessarily-interruptive elements, and behaviours that nobody responsible for a website would themselves find appealing as a visitor — is unwelcome and intolerable.”
  • Ignorant Hysteria Over 3D Printed Guns Leads To Courts Ignoring The First Amendment: "…in the last few days the hysteria [over 3D-printed guns] has returned… and much of it is misleading and wrong, and while most people probably want to talk about the 2nd Amendment implications of all of this, it's the 1st Amendment implications that are a bigger deal." Interesting. I'm not at all comfortable with wide availability of 3D-printed guns, but this analysis of the issues is worth reading.

Linkdump for April 27th through May 17th

Sometime between April 27th and May 17th, I thought this stuff was interesting. You might think so too!

  • The Case of the Stolen Source Code: Last week, for about three days, the macOS video transcoding app HandBrake was compromised. One of the two download servers for HandBrake was serving up a special malware-infested version of the app, that, when launched, would essentially give hackers remote control of your computer. // In a case of extraordinarily bad luck, even for a guy that has a lot of bad computer luck, I happened to download HandBrake in that three day window, and my work Mac got pwned. // Long story short, somebody, somewhere, now has quite a bit of source code to several of our apps.
  • JSON Feed: Announcing JSON Feed: We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs. So we developed JSON Feed, a format similar to RSS and Atom but in JSON. It reflects the lessons learned from our years of work reading and publishing feeds.
  • Let’s discuss the Linguistic & Pragmatic use of the [“N-word”]: No matter what your intentions, the word WILL mean something different depending on your relative status. Language is circumstancial.
  • The neural network writes the episode list for next season’s Dr. Who: I’ve trained this open-source neural network framework on a variety of datasets, including recipes, Pokemon, knock-knock jokes, pick up lines, and D&D spells. Now I give you: training a neural network on the complete list of Dr. Who episodes.
  • What we really need is an adaptation of the original 1740 The Beauty and the Beast: So were you aware that the The Beauty and the Beast story we all know is a heavily abridged and rewritten version of a much longer novella by Gabrielle-Suzanne Barbot de Villeneuve?  And that a lot of the plot holes existing in the current versions exist because the 1756 rewrite cut out the second half of the novella, which consisted entirely of the elaborate backstory that explains all the weird shit that happened before?  And that the elaborate backstory is presented in a way that’s kind of boring because the novel had only just been invented in 1740 and no one knew how they worked yet, but contains a bazillion awesome ideas that beg for a modern retelling?  And that you are probably not aware that the modern world needs this story like air but the modern world absolutely needs this story like air?

Post-Thanksgiving Status

This year’s Thanksgiving break was just what was needed: four days of virtually nothing of import whatsoever. We spent the weekend relaxing at home, reading books (I finished four over the four days (all of which were old Star Trek novels…yes, it’s escapist fluff, but that’s the point, especially as the Star Trek universe is based on optimistic ideals, which is just what I need these days), and in doing so completed this year’s Goodreads challenge, which I’d had set at 52 books), watching Netflix shows and upbeat movies from our personal collection, and eating lots of good food. We didn’t even leave the house for three of the four days, only venturing out on Sunday to do our grocery shopping for the week and a little Christmas book shopping at Goodwill.

I did spend some time tweaking Eclecticism, now that I’m paying attention to it again. I removed somewhere over 1,600 posts from a period where I was mirroring every tweet I posted to my blog…it seemed like a good idea at the time, but just ended up dumping a lot of noise into the archives here. I’ve also re-enabled Google Adwords advertising. I’m keeping it minimal, as I don’t want to unduly annoy any visitors, but it’d be nice to get back to making a little bit of money off of my years of babbling (at one point a few years back, I was pulling in about $100 every three months…nothing major by any means, but enough to cover my hosting costs, which was all I was really concerned with).

And that’s it for now.

Eclecticism is Now Secure (HTTPS)

Thanks to Dreamhost’s Let’s Encrypt initiative, plus a little nudging while setting up the iOS version of Ulysses, the (simple but very powerful) editor I’m using for writing posts here, my site is now HTTPS enabled.

For those who don’t know the terminology, all that means is that all traffic between my blog and your web browser is encrypted, and cannot be read by anyone who might intercept the data stream in transmission. You don’t have to do anything, it just happens automagically in the background.

While there’s nothing here that really requires the transmission to be encrypted — I don’t sell anything or have any reason to ask for sensitive information, which is the primary use case (and why HTTPS is used by financial institutions, shopping site, and so on) — I’m increasingly of the opinion that it’s just good practice to encrypt whenever possible.

Think of it like sending a physical letter to a friend via traditional snail mail; there might not be anything in the letter that needs to be kept private, but I’d still be pretty disturbed if I got a letter from someone and saw that the envelope had been opened so that someone else could read the contents.

Of course, with electronic communication, there’s no ripped envelope to let you know that someone’s taken a peek at what you’re saying or reading. Unsecure websites (or emails) are more like sending postcards: while for most people it’s pretty unlikely that anyone between the sender and receiver would be reading the postcard, it’s entirely possible that it could happen. Adding encryption means that not only is there an “envelope”, but it’s an envelope that can’t be opened by anyone but the receiver.

Good security isn’t paranoia. Just a good idea.

(Incidentally, I’m also set up with PGP encryption for my email, and would use it more often if I knew my contacts were similarly set up. Just contact me for my PGP public key if you’d like to securely email me (I’ll get it posted here eventually, I’m just finding bits and pieces of my site that need to be recreated after letting it lie fallow for so long, and that’s one).)

So. Very. S…l…o…w….

WordPress has gotten, really, really slow for me on this site, both on the outward-facing public side, and on the backend. I’m wondering if it might be a side effect of years and years of blogging (building up a total of almost 6,500 posts and almost 13,000 comments), plus trying various plugins here and there that probably often added extra fields to the database. I’m very tempted to do a full nuke-and-pave, exporting all the entries, building a brand-new WordPress install from the ground up, and then re-importing everything, but I worry about breaking all sorts of links (incoming, internal, and images) that I’d likely never have time to go back through and fix. At what point does the hassle of rebuilding stop outweighing the annoyance of a slow website?

Input-Only iPad

The iPad has lots of good creation tools, but it really does excel at providing a convenient way to veg out, and as much as I like having it, I think it has been more than a little responsible for my lack of blogging. Why take the time and effort to write anything when it’s so easy to kick back and let page after page of text and images flow past my eyes?

Meanwhile, I’ve neglected posting to Eclecticism; I have probably a few gigabytes of audio ripped from old vinyl waiting to be processed, imported to iTunes, and perhaps posted to Vinylicious; when I bother to pick up my camera, shots sit on the memory card for weeks or months, and then sit in Aperture for months before I finally get around to processing them and posting to my Flickr account; and who knows how many other projects have been left half-finished here and there.

All in all, while it’s been a busy year, on this level it feels like I don’t really have much to show for it.

So: As the iPad does have the capability to be far more than just a portable idiot box, it’s time to start taking advantage of that. I’ve got the iPad, a text editor, a nice little wireless keyboard (the onscreen keyboard works great and all, but it’s best for short bursts of text–tweets, status updates, comments, short emails, etc.–a real keyboard is much nicer for anything longer than one or two paragraphs), and a whole mess of lately underused grey matter rattling around in my skull. In theory, I should be able to put those together and, perhaps, get back in the habit of babbling on a semi-regular basis.

New Design

During my between-homework breaks today, I snagged bits of time here and there to see if I could slap together a new design for my site. Initially I was just hoping to find a decent temporary placeholder theme until I had time to really dive into a full redesign, but as it turned out, I think I’m happy enough with this to simply declare it my new look (until I get bored again).

I’ve wanted to simplify things and remove some of the clutter for a while, so I went looking for a nice, clean, single-column theme. After experimenting with two or three, I’ve settled on Satorii, by Felipe Lavin, slightly modified to fit my taste (adding the graphic in the background, switching to a serif font, and using my handwriting font for the site and post titles). I may do other tweaks here and there — I’m not thrilled with the footer at the moment — but that will come as I have time and inspiration strikes.

For the most part, though, this is what I’m going with from here forward. Nice, simple, clean, and easy to read.

Back (Sorta)

While I don’t really think that very many people noticed, something went all pear-shaped over the weekend and this blog disappeared for a few days. Thanks to some assistance from Dreamhost support, I’m back up and running…mostly. Some of the plugins I used broke, and I’ve lost the customizing of the theme (including all the egolicious representations of me), so I’ll have (yet another) PROJECT to keep me busy once the quarter ends.

So, some minor frustrations. However, the content is here, and that’s the most important part. I was thinking that it was about time for a redesign anyway.

Lazyweb: Automated Crowdsourcing of Website Uptime/Downtime Tracking

Last night, Prairie and I were watching Bones on Netflix’s streaming service when Netflix suddenly stopped responding. In order to find out if there were service-wide problems, my first step was to turn to Twitter to see if there were any other people reporting problems — and as it turns out, there were. Reassured that it was a Netflix issue, and not something going wrong with my setup, we popped in a DVD until people on Twitter started reporting that things were working again.

It seems that using Twitter is becoming a more and more common way to get a quick handle on whether a particular website is having issues. This started me thinking about a website that could act as a simple, centralized tracker of uptime/downtime reports, gathered from real-time scanning of the Tweetstream. I don’t have the coding chops to do this, so I’m tossing the idea out to the Lazyweb in case anyone else wants to run with it.

The basic idea seems simple enough: scan the tweetstream for variations on the types of posts people make when a service is showing signs of problems. Basic search strings would be something along the lines of “* is [down|broken]” and “is * [down|broken]“. Anytime a hit is made on the search string, an entry is made in the database with the reported problem site and whatever might be considered relevant data from the source tweet (the tweet text, time/datestamp, perhaps even geolocation data for those tweets that are carrying it). Tracking reports of websites coming back online could be integrated as well, by watching strings such as “* is [back|up|back up|working]“.

The website would display a regularly updating display of downtime/uptime reports, one line per target website, with a series of stats indicating things like how recently the last problem or resolution tweet was recorded, the number of problem or resolution tweets found within the last 10, 30, or 60 minutes, perhaps a map showing geolocation markers that could indicate if downtime is widespread (indicating downtime at the website itself) or geographically targeted (indicating problems with a particular network, carrier, or ISP between the website and the Twitter users reporting problems), and whatever other data might be useful. It might be possible to use CSS to color-code lines depending upon variable such as the rate of problem tweets being found, too.

Anyway, that’s about as formed as the idea is in my head. If this sounds interesting to anyone else, feel free to grab the idea and run. If someone does build this based on this post, though, some mention or credit would be nice. ;)

Dreamhost Does Good

Since I’ve occasionally groused about the hosting service I get with Dreamhost, I wanted to be sure to mention when things go right, instead of only when things go wrong.

For a few months, the server that my account was set up on, and which hosts all three domains under my control, was being tweaky, resulting in sporadic downtime. I’d been building up a small library of downtime reports in my support page with Dreamhost, when last month, things took a turn for the worse…and then, soon afterward, for the better. Of course, I didn’t really know about the “for the worse” part until I got the news of the “for the better” side of things.

The last time my site went down, when I submitted the support request notifying Dreamhost of the downtime, they replied relatively quickly, letting me know that the server I was on had become “unresponsive,” and they were working on getting this back up and running. About half an hour later, my sites came back up, and I didn’t think much more of it. Until the next day, when I got the following…

This is just a note to let you know that we’ve moved your account to a new server! We apologize for the lack of notice, but this was an emergency move as a perfomance and stability measure.

Apparently the server I’d been on had gone seriously downhill, and had to be replaced, necessitating moving my account to new hardware (and hopefully all the other occasional downtime I’d had was due to the developing hardware issues, and I won’t get those again). Most of the rest of the message was covering anything I might need to do to ensure that everything worked as it should, and as it turns out, I didn’t really need to do much of anything, as the transition was seamless. Then, at the end of the note…

…again, we really apologize for the abrupt nature of this move! To try and make up for it a bit, we’ve also set your account to now have unlimited disk and bandwidth, forever!

Ooooh. See those last few words? That’s nice to see. “Unlimited disk and bandwidth, forever!” No worries about storing large files (not that I tend to do that), no worries about surcharges on the (very) off chance that I get Slashdotted or Dugg. Just keep paying my yearly bill, and I’m set.

Dreamhost, I’ve had issues with you from time to time, but this? This is good. Thanks!