I caught some kind of head cold, or maybe the flu that's going around, and stayed home from work today.
Reports indicate that this year's flu vaccine may only have a 10% efficacy. But if you haven't been vaccinated, do it; 10% efficacy's better than nothing. I got mine -- and if I hadn't, I might be feeling even worse right now.
In my last couple of posts, I've talked a bit about the drawbacks of iOS and Android, but acknowledged I've found the alternatives lacking. Ultimately, I went back to Android -- but not stock Android.
Android -- at least, the base OS -- is free/open-source software. As such, there are many different variations of Android available.
Replicant is the only Android variation endorsed by the GNU Project; it seeks to provide an Android experience with only free/open software. Unfortunately, it has drawbacks: it has a very limited number of supported devices, the most recent of which is the Samsung Galaxy Tab 3, which was released in 2013. Replicant itself isn't quite that outdated; the latest version is 6.0, based on Android 6.0 Marshmallow (2015). And even though Replicant itself is free, it still requires proprietary firmware in most cases.
I've ultimately settled on LineageOS, an Android distribution descended from the previous CyanogenMod project.
You can install Google Services and Apps (Gapps) on top of LineageOS, but on my latest installation, I opted not to do that. I get most of my Android software from F-Droid, a free software repository.
I do run a few proprietary apps; the Amazon App Store is one source, and there's a program called Yalp Store (you can get it from F-Droid) that lets you download apps from the Google Play Store without installing Gapps -- though keep in mind that does violate Google's terms of service.
Someone also recently recommended microG to me; it's a free re-implementation of Google Services. I haven't tried it out yet, but it looks promising.
All in all, I was surprised by just how easy it ended up being running an Android-based OS without Google's proprietary apps and services. That's easy for values of "easy" that include being comfortable flashing your phone, of course, but so far it's worked out pretty well for me.
I'd sure like to see one of those alternatives get a better foothold, though. More competition is good for everybody, especially if that competition comes from free software.
Yesterday I talked a little bit about Ubuntu Touch, a would-be alternative smartphone OS based on GNU/Linux (that is to say, the Linux kernel and GNU userland, as opposed to Android, which is based on the Linux kernel and Google's own userland).
There are other phone OS's out there, too.
Jolla's Sailfish is another GNU/Linux-based OS, based on Nokia's abandoned MeeGo platform. It's the most mature of the lot, but supports a limited number of devices. I haven't tried it because the port for my phone, the Nexus 5, hasn't been updated since 2015. But it appears to have pretty good support for Sony Xperia phones, and it runs Android apps through a compatibility layer, though my understanding is that that compatibility layer is proprietary, drains the battery significantly, and doesn't have full compatibility.
Other than iOS, Android, and, to a lesser extent, Windows Phone, Ubuntu Touch, and Sailfish, there aren't a lot of mobile OS's that are ready for prime-time. KDE's Plasma Mobile is still in early stages; the steps for setting it up on a Nexus 5 indicate that it's strictly for developers right now.
GNOME doesn't have much of a mobile presence at this time, either, though Purism has announced that its upcoming Librem 5 phone will feature a GNOME desktop (with Plasma as an alternative option).
There's also LuneOS, a fork of Palm/HP's webOS (which, like Android, is based on the Linux kernel but not the GNU userland). It's still early days too.
I also just ran across postmarketOS, whose homepage says "The project is at very early stages of development and is not usable for most users yet." (Boldface in original.)
One of the biggest problems facing all these projects is the proliferation of different Android devices, most of which rely on proprietary firmware for hardware support. There is a project in the works that should help with the hardware support issues (though not with the inherent problems of proprietary firmware); it's called Halium, and it should make development much easier for all these projects.
In the meantime, though? You're probably stuck with iOS or Android -- Apple's walled garden or Google's spyware.
There are ways to run Android without Google services or proprietary software. I'll get to that tomorrow.
It's disappointing that the smartphone market has turned into a choice between two OS's: iOS's walled-garden approach where Apple decides what software you're allowed to run on the phone that you ostensibly own, and Android's spyware panopticon security nightmare.
There are a few alternatives, none of them very good.
A few months ago, I tried switching from Android to Ubuntu Touch. Canonical abandoned Ubuntu Touch a few months back, but it's still under development by a small community-based group called UBports.
Here's what I wrote at the time (originally posted on Brontoforumus, 2017-07-03):
It's a pretty different idiom from Android (no ubiquitous three buttons at the bottom of the screen, though their functionality is there; swipe from the left edge of the screen to get a dock, from the right edge to get a Windows 7-style list of open programs, and the Back button is handled at the app level), but I could get used to it, and the list of available apps seemed sufficient for my day-to-day use.
The only real problem was that the phone didn't work.
I fucked around with the settings for awhile but all I managed to accomplish was to change what it said under "carrier" from "Sprint" to "none".
So I decided to give LineageOS another shot. (Well, technically my first time using it as LineageOS, but I used it plenty when it was Cyanogenmod.) It appears that I've mostly fixed the Sprint issues I had with it before.
But I thought Ubuntu was pretty impressive, and I intend to give it another shot someday. Maybe once they finish updating it to a 16.04 base.
I should probably update my post about getting Sprint to work on LineageOS (then CyanogenMod); I need to update the title and the links, and add the last step that finally got it (mostly) working.
I've managed to do okay without Gapps, too -- but maybe I'll get to that another time.
Papago Plaza -- the entire complex where the tap room was located -- is being demolished to put up condos. They've expressed hope for finding a new home, but no news yet.
My good friend Brad -- himself a brewery owner these days -- came in from Riverside to pay his respects, and so we got a Lyft van-full of the old gang together and headed up there for the last day.
There are pictures. I don't have them yet. Hopefully I'll get them later and be able to post them.
It was bittersweet. The fridge was mostly empty; most of the items on the menu, food or drink, were sold out. The life-size monk statue had already gone, as had one of the two dartboards.
The writing was literally on the wall; people had been saying their goodbyes in silver Sharpie for months (if one message, dated March, is anything to go on).
We had a few rounds, and then we walked a block south to McFate -- that's my regular watering hole these days. My friends hadn't been there yet, but they were interested in checking it out. There was a nice bit of symmetry: saying goodbye to the old spot, and hello to the new one.
The details of the day are a little hazy. I remember we told old stories, and I laughed some belly laughs.
I'm pretty sure I only drank five beers, and I paced myself, with a glass of water after each. But I do have a tendency to make a beeline for the highest-alcohol beer on the menu when I don't have to drive. (I can recommend the beers I drank at McFate, but can't remember their names. There was an IPA called Hazy something, and a Scotch-aged something or other.)
I'll miss Papago. I hope it reopens someplace. At any rate, it was good to get the band back together for a day, and talk about the good old days.
Yesterday I discussed Ajit Pai's plan to dismantle the FCC's net neutrality regulations, his disingenuous justifications for doing so, and the inevitability of lawsuits challenging the change in court. We left off on Tim Wu's observation that Pai is doing this in opposition to the vast majority of public opinion.
The FCC comment period concerning the net neutrality repeal saw 22 million comments; it received a greater response than any other FCC proposal in history.
Pai [...] released a "Myth vs. Fact" sheet that claims public comments to the FCC don't show significant support for net neutrality. Pai's office called it a "myth" that commenters "overwhelmingly want the FCC to preserve and protect net neutrality," arguing that fraudulent comments far outnumber legitimate ones.
That's true largely because the FCC imposed no real restrictions on comment uploads and took no steps to remove fraudulent comments from the record. But analyses of comments show that about 98 or 99 percent of "unique" comments oppose the net neutrality repeal.
That last link goes to an article by Jeff Kao at Hackernoon titled More than a Million Pro-Repeal Net Neutrality Comments were Likely Faked. Here are a couple lines from the abstract:
My research found at least 1.3 million fake pro-repeal comments, with suspicions about many more. In fact, the sum of fake pro-repeal comments in the proceeding may number in the millions. In this post, I will point out one particularly egregious spambot submission, make the case that there are likely many more pro-repeal spambots yet to be confirmed, and estimate the public position on net neutrality in the “organic” public submissions.
Kao goes on to chart the duplicate versus unique comments:
Keep-Net Neutrality comments were much more likely to deviate from the form letter, and dominated in the long tail.
From this chart we can see that the pro-repeal comments (there are approximately 8.6 million of them) are much more likely to be exact duplicates (dark red bars) and are submitted in much larger blocks. If even 25% of these pro-repeal comments are found to have been spam, that would still result in more than 2 million faked pro-repeal comments, each with an email address attached. Further verification should be done on the email addresses used to submit these likely spam comments.
On the other hand, comments in favor of net neutrality were more likely to deviate from a form letter (light green, as opposed to dark green bars) and were much more numerous in the long tail. If the type, means of submission, and ‘spamminess’ of comments from both sides were equal, we would expect a roughly even distribution of light and dark, red and green, throughout the bars. This is evidently not the case here.
Kao has gone to more trouble than Pai to try and tell spam comments from legitimate ones. Indeed, New York AG Eric Schneiderman has accused the FCC of stonewalling his investigation into FCC comments using fraudulent names and addresses. And he's not the only one investigating:
Schneiderman is not the first to accuse the FCC of stonewalling investigations into the net neutrality comment system. The FCC's claim that the comment system was temporarily disrupted by DDoS attacks has received lots of attention, but the FCC hasn't provided all the records requested in several Freedom of Information Act (FoIA) requests.
The FCC also told members of Congress that it won't reveal exactly how it plans to prevent future attacks on the public comment system.
A FoIA request from Ars was denied by the FCC due to "an ongoing investigation."
US Senator Ron Wyden (D-Ore.) criticized the FCC for failing to turn over its internal analysis of the DDoS attacks that hit the FCC's public comment system. Senator Brian Schatz (D-Hawaii) and Rep. Frank Pallone (D-N.J.) requested an independent investigation into the DDoS attacks, and the US Government Accountability Office (GAO) has agreed to investigate.
The FCC is also facing a lawsuit alleging that it ignored a FoIA request for data related to bulk comment uploads, which may contain comments falsely attributed to people without their knowledge.
So are there any other ways the FCC's terrible plan is vulnerable to litigation?
And there's legal precedent stating that the FCC can't preempt state laws -- ironically, decided in a case where Tom Wheeler's FCC attempted to prevent states from passing laws against municipal broadband.
These are just some of the avenues of attack Pai has opened himself up to. The question isn't whether there will be lawsuits after the net neutrality repeal; it's how many and how soon.
Ajit Pai has announced, expectedly, that he intends to vote to kill the FCC's Title II net neutrality regulations on December 14.
As I've discussed previously, this was a foregone conclusion, but the point was never to change Pai's mind; there are, after all, two whole branches of government besides the one he serves in.
The problem for Mr. Pai is that government agencies are not free to abruptly reverse longstanding rules on which many have relied without a good reason, such as a change in factual circumstances. A mere change in F.C.C. ideology isn’t enough. As the Supreme Court has said, a federal agency must “examine the relevant data and articulate a satisfactory explanation for its action.” Given that net neutrality rules have been a huge success by most measures, the justification for killing them would have to be very strong.
It isn’t. In fact, it’s very weak. From what we know so far, Mr. Pai’s rationale for eliminating the rules is that cable and phone companies, despite years of healthy profit, need to earn even more money than they already do — that is, that the current rates of return do not yield adequate investment incentives. More specifically, Mr. Pai claims that industry investments have gone down since 2015, the year the Obama administration last strengthened the net neutrality rules.
Setting aside whether industry investments should be the dominant measure of success in internet policy (what about improved access for students? or the emergence of innovations like streaming TV?), Mr. Pai is not examining the facts: Securities and Exchange Commission filings reveal an increase in internet investments since 2015, as the internet advocacy group Free Press has demonstrated.
A popular argument I've seen from anti-Title II trolls on sites like Ars Technica and Techdirt is "Well if we need these rules, how did the Internet do so well before 2015?" (This rhetorical question is usually coupled with sarcastic remarks about former president Barack Obama.)
That question is disingenuous, for a couple of reasons. First, as Wu notes, that's the opposite of how FCC rules get passed and repealed. We already asked and answered the question of why we needed Title II regulations during the public comment period in 2014. The question isn't "Why did we need these rules in 2015?" It's "Why do we no longer need them in 2018?" It's the oldest forum troll trick in the book: "I'm not going to provide supporting evidence for my argument, I'm going to demand that you provide supporting evidence for yours, even though the burden of proof is on me."
The other reason the "How did the Internet ever survive before 2015?" question is disingenuous horseshit is that Pai's not merely rolling back FCC rules to pre-2015 levels, he's rolling them back to pre-2005 levels. Wu's article continues:
But Mr. Pai faces a more serious legal problem. Because he is killing net neutrality outright, not merely weakening it, he will have to explain to a court not just the shift from 2015 but also his reasoning for destroying the basic bans on blocking and throttling, which have been in effect since 2005 and have been relied on extensively by the entire internet ecosystem.
This will be a difficult task. What has changed since 2004 that now makes the blocking or throttling of competitors not a problem? The evidence points strongly in the opposite direction: There is a long history of anticompetitive throttling and blocking — often concealed — that the F.C.C. has had to stop to preserve the health of the internet economy. Examples include AT&T’s efforts to keep Skype off iPhones and the blocking of Google Wallet by Verizon. Services like Skype and Netflix would have met an early death without basic net neutrality protections. Mr. Pai needs to explain why we no longer have to worry about this sort of threat — and “You can trust your cable company” will not suffice.
So let's, just for a moment, play the trolls' game and explain why we need Title II regulations to protect net neutrality.
There's a convenient list of net neutrality violations making the rounds; I don't know where it originated, but I've seen variations on it in a couple of different places: by a poster named JoeDetroit on Techdirt and a poster named Happysin on Ars Technica. Here are both those versions of the list combined and lightly edited:
2005 - Madison River Communications was blocking VOIP services. The FCC put a stop to it.
2005 - Comcast was denying access to P2P services without notifying customers.
2007-2009 - AT&T was having Skype and other VOIPs blocked because they didn't like that there was competition for their cellphones.
2011 - MetroPCS tried to block all streaming except YouTube. They actually sued the FCC over this.
2011-2013 - AT&T, Sprint, and Verizon were blocking access to Google Wallet because it competed with their own wallet apps. This one happened literally months after the trio were busted collaborating with Google to block apps from the Android marketplace.
2012 - Verizon was demanding Google block tethering apps on Android because it let owners avoid their $20 tethering fee. This was despite guaranteeing they wouldn't do that as part of a winning bid on an airwaves auction.
2012 - AT&T tried to block access to FaceTime unless customers paid more money.
2013 - Verizon literally stated that the only thing stopping them from favoring some content providers over other providers were the net neutrality rules in place.
2014 - Netflix & Comcast sign a deal where Netflix will pay Comcast to stop throttling the service. The very next day, streaming problems vanish.
That is, needless to say, not an exhaustive list.
Meanwhile, there's another kind of forum troll, making the rounds like clockwork on every article I've ever seen on this subject: the "What does it matter? Pai's just going to do it anyway; he doesn't care what we think!" troll.
I've already responded to that argument at length (and up at the top of this post -- "two whole branches of government"). Wu reinforces my point:
Moreover, the F.C.C. is acting contrary to public sentiment, which may embolden the judiciary to oppose Mr. Pai. Telecommunications policy does not always attract public attention, but net neutrality does, and polls indicate that 76 percent of Americans support it. The F.C.C., in short, is on the wrong side of the democratic majority.
That's why people left comments on the FCC website. It's why people are writing articles protesting it now, and planning in-person protests for December 7. Lawsuits are inevitable, and clear and constant reminders that Pai threw out the Title II classification against public opinion makes his weak case weaker.
And that's not the only thing. Come back tomorrow for more.
Yesterday I talked about IDW's Transformers comics (which are on sale on Comixology through tomorrow, November 30). I mentioned a few favorites from their first few years (Phase One), but also noted that the series didn't really get good until Phase Two.
Phase Two kicks off with two series: More than Meets the Eye, by James Roberts and Alex Milne, and Robots in Disguise, by John Barber and Andrew Griffith (with various other artists involved in both series over the course of their runs).
There was also a trilogy of prequel miniseries, called Autocracy, Monstrosity, and Primacy, available as the Autocracy Trilogy (written by Chris Metzen and Flint Dille, with gorgeous painted art by Livio Ramondelli). I've only read Autocracy, which concerns the beginning of the war and Orion Pax's ascension as Optimus Prime. I really liked the art, but the story felt a little disjointed; it was released digital-first, with 8-page issues, and those short chapters really affect the pacing.
But back to the two main series: As our story begins, the five-million-year war between the Autobots and Decepticons has been finally, decisively won, by the Autobots. More than Meets the Eye tells the story of a group of Cybertronians led by Rodimus who set off in a ship called the Lost Light, nominally in search of the legendary Knights of Cybertron, but mostly they just get into trouble along the way. Robots in Disguise is a political drama, about Bumblebee's attempts to serve as leader on a resurgent but factionalized Cybertron, where an uneasy peace exists among Autobots, Decepticons, and so-called NAILs, Cybertronians who did not join either faction but are returning to their home planet now that the war is over.
Chris Sims wrote a great series of reviews at Comics Alliance, called The Transformed Man, where he followed both series for most of their run. It's worth a read, whether you want to read it as a companion piece as you read the series yourself, or want some reviews from a Transformers skeptic to see if these are the kind of books you'd be into. Sims is funny and insightful, and, for all his talk about being a Transformers neophyte, his tastes align pretty closely with mine as a longtime fan.
I plan on talking about these comics in more detail later on, but my take is this: read More than Meets the Eye all the way through, and then keep reading as it continues under the title Lost Light (with new artist Jack Lawrence). It's seriously one of my favorite comics of the last few years, and my favorite Transformers series ever, in any medium.
Robots in Disguise, meanwhile? My recommendation is to read up through the City on Fire arc (vol 4) and stop there. After that, volume 5 is mostly table-setting, and then both series cross over in an arc called Dark Cybertron. I haven't read Dark Cybertron, because it wasn't in the Humble Bundle I got most of these comics in, and because I hate crossovers (though I just bought it in the current Comixology sale, so I guess I'll be reading it shortly). Some important stuff happens that leads into "season 2" of More than Meets the Eye (beginning in MtMtE vol 6), but even if you don't read it, it doesn't take long to pick up what you missed. (I plan on getting into spoilers in a future post, but for now I'll leave it at that. Even though one of those spoilers is right there on the cover of MtMtE vol 6.)
After that, Robots in Disguise moves off Cybertron and on to Earth, and it loses my interest fast. There is some great stuff in there -- a highlight is Thundercracker enthusiastically writing screenplays and not realizing that they are terrible, and issue #48 is narrated by a dog and is amazing -- but in a lot of ways it's a continuation of the earlier, more boring Phase One comics that I didn't like that much. Your mileage may vary.
The Cybertron storyline, however, continues in two Windblade miniseries, and then the Till All Are One series, by Mairghread Scott, Sara Pitre-Durocher, and a few other artists. These series ably continue the story of political intrigue that Barber and Griffith started, and expand the scope by introducing other planets where Cybertronians have settled, including religious Caminus, militaristic Carcer, and Eukaris, the planet where all the Beast Wars characters live.
Lost Light is still ongoing. Till All Are One, sadly, has been cancelled, and its story will wrap up in Till All Are One Annual 2017, which is due out on December 20.
So there's my brief run-through of what IDW Transformers comics I like. In future posts, I hope to spend more time delving into why I like them, how Roberts and Milne have turned Megatron into my favorite character, and why it's a damn shame to see Till All Are One go and I hope that it's not the last we see of Cybertronian political intrigue.
I'm a longtime Transformers fan. And over the past year or so, IDW's Transformers comics -- most specifically, the More than Meets the Eye and Lost Light series -- have surpassed Beast Wars as my all-time favorite Transformers series.
But it wasn't always thus. The first few years of Transformers at IDW -- now referred to retroactively as "Phase One" -- mostly just aren't that good.
The main series, spread across miniseries called Infiltration, Escalation, and Devastation (written by Simon Furman and drawn by EJ Su), was too slow-paced and human-centric. Another miniseries, Stormbringer (by Furman and Don Figueroa), was an attempt to course-correct and focus the action on giant robots and the planet Cybertron, but made the baffling choice of turning Cybertron into an uninhabitable wasteland; the book was pretty to look at but ultimately forgettable. All Hail Megatron (by Shane McCarthy, Guido Guidi, and various other artists) started out strong, and had some great moments with Megatron and Starscream, but ultimately suffered Third Act Problems and fizzled out near the end.
So don't start with any of those.
No, if there's a Phase One book you should start with, it's Megatron Origin, by Eric Holmes and Alex Milne. Megatron Origin is probably the single most important book in IDW's entire Transformers line, which is perhaps ironic since it was actually conceived as part of the previous Transformers line at Dreamwave.
That may be why the effects of Megatron Origin aren't really apparent through most of Phase One; it plants seeds that pay off later (mixaphorically speaking). But it introduces an element that's key to what I love so much about the IDW comics, and why I think Megatron is the most interesting character in them: it gives him an arc. Megatron starts out as the good guy.
That thread picks up later, in issues #22 and #23 of the 2010-2011 Transformers series (which are also collected in the Chaos Theory trade, along with some other stuff). Milne revisits Megatron's origin story with writer James Roberts, going back even farther than the Megatron Origin miniseries to tell of his first meeting with Orion Pax (later Optimus Prime). Roberts and Milne come back to this story again and again in More than Meets the Eye and Lost Light; it's a crucial moment in Megatron's development, signaling his turn from philosopher to violent revolutionary.
Those are the most important books in Phase One.
I also quite like the first ten issues (collected in the first two volumes) of Transformers: Spotlight, a series of done-in-one stories, each focused on an individual character, written by Simon Furman and drawn by various artists. They're not as crucial to Phase Two continuity as the Megatron stories I've mentioned, but they're well worth reading.
Lastly (for Phase One), there's Last Stand of the Wreckers by Roberts and Nick Roche, which is mainly important for two things: it introduces Overlord, who becomes important later, and it begins to establish Prowl as a scheming, calculating bastard, which becomes his primary depiction from here on in. It's not essential, but it does make for a nice "oh shit" moment if you know who Overlord is when he shows up later.
And oh, hey, all these comics are on sale on Comixology through November 30. (And if you miss this sale, keep an eye out for another one later; IDW has pretty frequent Transformers sales. They show up in Humble Bundles once in awhile, too.)
Last night I finally got around to changing my site intro. I removed the bit that said "I'm a thirtysometing computer scientist who's spent the last few years bouncing from one temp IT job to another."
I got a full-time job on April 1, 2016. It's been good. Good company, good pay, good benefits, good coworkers.
Back in 2013, shortly after starting a new temp job, I introduced myself to one of the other guys and cracked a joke about "jumping from temp job to temp job, hoping each time that my next leap would be the leap home." After eight temp jobs in seven years, it looks like I've finally made that leap.
I'm getting used to it. That constant fear that you learn as a temp, that the axe could fall at any time? I'm working on unlearning it. It's not as bad as it used to be.
I wrote a post once called Tempin' Ain't Easy. I'd still like to expand it to book length, one of these days. Years of unemployment and underemployment certainly affect your outlook. I'm not about to forget those years. I feel lucky that that's not what I'm dealing with anymore.
Now I need to think of a new tagline. "Now Works on Phones" is a two-year-old joke; it's a reference to a then-recent responsive redesign of the website and a brief (about three days) contract I took installing phones in an office. Now Works on Phones.
