An interesting piece of news crossed my desk (well, actually appeared in my browser) this week: The (presumably) final resolution of the entire SCO saga. If you missed it, that’s not entirely surprising. The long, sordid saga was effectively put to bed a long time ago when SCO lost some key court decisions and went bankrupt. However, there remained a complicated set of claims and counterclaims that were theoretically just dormant and could have been reanimated given a sufficiently bizarre set of circumstances. 

However, on February 26:

Plaintiff/Counterclaim-Defendant, The SCO Group, Inc. (“SCO”), and Defendant/CounterclaimPlaintiff,International Business Machines Corporation (“IBM”), jointly move for certification ofthe entry of final judgment on the Court’s orders concerning all of SCO’s claims, including the(a) Order filed on Feb. 5, 2016, granting IBM’s Motion for Partial Summary Judgment (DocketNo. 782), (b) Order filed on Feb. 8, 2016, granting IBM’s Motion for Partial Summary Judgment(Docket No. 783), (c) Partial Judgment Dismissing SCO Claims filed on July 10, 2013, and (d)Order filed on July 1, 2005, denying SCO’s Motion for Leave to File a Third AmendedComplaint (Docket No. 466). 

There’s more legalese but this would seem to be as much of a wrap as there ever is in the legal world.

I started covering this drama back in 2003 when SCO and their lawyers did their roadshow to industry analysts to show off the code that had been purportedly copied into Linux. (I was working at Illuminata at the time.) We wouldn’t sign their NDA but they showed us some code anyway and I ended up writing a research note “SCO’s Derived Case Against Linux.” I’m sure it got some of the details wrong but this was before it was particularly clear what was even being claimed. (Of course, that would remain a pattern thought much of the case.)

I then ended up helping my colleague Jonathon Eunice write an expert witness report for IBM once those cases got rolling. I haven’t been able to discuss that fact or anything else about the case while the claims and counterclaims remained open. It was a busy number of months working on that report. In all, it was a fascinating experience although one I’m not sure I would want to make a practice of. It also gave me an appreciation for why lawsuits like these are so incredibly expensive. 

Unfortunately, the expert witness reports remain under court seal and that’s unlikely to change. That’s a bit frustrating both because I think we did some good work that ended up not really being used and because there’s a lot of historical information about the claims SCO made that will probably never see the light of day. But, in any case, I still can’t say too much about the details that I know.

The whole set of cases was such a weird trip down the rabbit hole. Probably the confusion over who owned the UNIX copyrights is Exhibit A. Wouldn’t you have thought the executives involved with the supposed sale would have remembered and that the contract would have been crystal clear on this basic point? One would but this is the SCO saga we’re talking about. 

It’s hard to argue that the SCO cases hurt open source and Linux. Perhaps they slowed down adoption in some circles. But the fact that Linux made it through what, at one time, looked to be a serious threat perhaps even strengthened it in the long run. 

1. An Adaptive Learning Interface that Adjusts Task Difficulty based on Brain State (PDF) -- using blood flow to measure cognitive load, this tool releases new lessons to you when you're ready for them. The system measures blood flow using functional near-infrared spectroscopy (fNIRS). Increased activation in an area of the brain results in increased levels of oxyhemoglobin. These changes can be measured by emitting frequencies of near-infrared light around 3 cm deep into the brain tissue and measuring the light attenuation caused by levels of oxyhemoglobin. I think we all want a widget on our computer that says "your brain is full, go offline to recover," recover", if only to validate naptime.
2. Deploying Software -- Your deploys should be as boring, straightforward, and stress-free as possible. cf Maciej Ceglowski's "if you find it interesting, it doesn't belong in production."
3. Replicating SQLite Using Raft -- rqlite is written in Go and uses Raft to achieve consensus across all the instances of the SQLite databases. rqlite ensures that every change made to the database is made to a quorum of SQLite files, or none at all.
4. An Introduction to Autonomous Robots -- An open textbook focusing on computational principles of autonomous robots. CC-NC-ND and for sale via Amazon.

In this episode, we discuss the latest epidemic in hip-hop–rappers going broke! From lawsuits, to spending a million dollars on Uber, to selling wack products to the hip-hop fanbase, we go deep into the behavior that led them there. The result is an in-depth (but funny) conversation that nobody in hip-hop is having right now. As usual, no punches are pulled and nobody is safe!

Thanks for listening!

Follow and subscribe to Super Duty Tough Work:
iTunes | Soundcloud | Stitcher | Twitter

[Image: Flooding in Brooklyn during Hurricane Sandy; Instagram by BLDGBLOG].

Before heading out the other night to see a panel on pandemic diseases moderated by Sonia Shah—author of the interesting new book Pandemic: Tracking Contagions, from Cholera to Ebola and Beyond—I read an otherwise unrelated article about the current rate of sea level rise.

According to a new study, the New York Times explains, sea levels are “rising faster than at any point in 28 centuries, with the rate of increase growing sharply over the past century.” Needless to say, this is having—and will continue to have—extraordinary landscape effects.

Rising sea levels are already “straining life in many towns,” the New York Times continues, “by killing lawns and trees, blocking neighborhood streets and clogging storm drains, polluting supplies of freshwater and sometimes stranding entire island communities for hours by overtopping the roads that tie them to the mainland.”

And true sea level rise has barely started.

Flooded L-train tunnel following Hurricane Sandy; photo courtesy MTA].

Recall, for example, the Guardian’s recent depiction of Miami as a city at war with the sea, as ocean water now surges into the streets from below, assaulting the surface through backed-up storm sewers.

Tidal surges are turned into walls of seawater that batter Miami Beach’s west coast and sweep into the resort’s storm drains, reversing the flow of water that normally comes down from the streets above. Instead seawater floods up into the gutters of Alton Road, the first main thoroughfare on the western side of Miami Beach, and pours into the street. Then the water surges across the rest of the island.
The effect is calamitous. Shops and houses are inundated; city life is paralysed; cars are ruined by the corrosive seawater that immerses them. During one recent high spring tide, laundromat owner Eliseo Toussaint watched as slimy green saltwater bubbled up from the gutters. It rapidly filled the street and then blocked his front door. “This never used to happen,” Toussaint told the New York Times. “I’ve owned this place eight years and now it’s all the time.”

It’s worth pointing out, of course, that Michael Grunwald, author of the excellent book The Swamp: The Everglades, Florida, and the Politics of Paradise—a Cadillac Desert for South Florida—rebutted most of that article’s more salacious points.

“I’m sorry to spoil the climate porn,” Grunwald wrote for Time, “but while the periodic puddles in my Whole Foods parking lot are harbingers of a potentially catastrophic future, they are not currently catastrophic. They are annoying. And so is this kind of yellow climate journalism.”

However, Elizabeth Kolbert recently picked up the baton in a great and convincing piece for The New Yorker. Kolbert rode around the city, speaking with geologists and water managers, visiting neighborhoods already experiencing the landscape-futures of climate change. “We’d come to a neighborhood,” she writes, “of multimillion-dollar homes where the water was creeping under the security gates and up the driveways. Porsches and Mercedeses sat flooded up to their chassis.”

Tomorrow’s coastal landscape, today.

[Image: Flooding in New York State; photo by Jonathan LaRocca/Creative Commons].

In any case, continue this trend for a century, two centuries, three centuries, and coastal cities such as Miami—and New York and Shanghai and Sydney and Lagos and Rio—are threatened not with Grunwald’s annoyance but with extinction. “Experts say the situation would then grow far worse in the 22nd century and beyond,” the New York Times points out, “likely requiring the abandonment of many coastal cities.”

None of this is news—even here on BLDGBLOG, we’ve been looking at the flooded cities of a climate-changed future since nearly day one—but it was interesting to consider this vision of a drowned world while listening to Sonia Shah and her panelists discuss known reservoirs of microbes and pathogens.

Take the Sundarbans, for example.

[Image: The Sundarbans, courtesy NASA].

In Shah’s book, Pandemic, she explains that the Sundarbans—which she describes as “a netherworld of land and sea long hostile to human penetration” in the Bay of Bengal—are the natural reservoir of Vibrio cholerae bacteria. These, of course, cause cholera.

The environmental and spatial conditions there are perfect for their survival, and it was only human intervention—and, later, global trade—that allowed cholera to make its great escape.

During the event the other night, Shah also pointed out that our mountains of impermeable plastic waste are inadvertently forming a nearly ideal, artificial ecosystem for mosquitoes, giving those insects a water-logged environment—a different kind of “plastisphere”—in which to breed. The conditions, again, are perfect for mosquitos’ survival, an accidental augmentation of their habitat by way of the consumer packaging industry.

I mention all this because it’s hard not to wonder what future disease reservoirs might form in an era of rising sea levels and flooded cities. Down in the drowned road tunnels of New York, for example, or in the geyser-like storm drains of an uninhabitable Miami—in the basements, parking lots, and silt-filled shopping malls of a submerged world—what future infections will find a route for spilling over into the human world, what disease-ridden insects find ideal conditions for replication?

These sorts of “neglected environments contaminated with human filth,” as Shah describes them, are great shapers of pandemics.

While this is not only interesting from the perspective of a potential novel plot—a Michael Crichton-like thriller set in a flood-ravaged world, where strange diseases emerge from forgotten suburbs engulfed by the sea—it also has clear epidemiological relevance, in terms of scanning ahead for potential outbreaks.

In other words, we know—as Shah’s panel the other night made abundantly clear—that human settlement in previously wild landscapes, such as deep rain forests and coastal mangrove swamps, poses predictable, if statistically complex, dangers in terms of exposing people to new diseases. But we should thus also be able to predict that certain forthcoming landscape-scale events—the permanent flooding of the New York City subway system, say, or Floridian landfills fatally overcome by rising tides—will also come with more or less known epidemiological side-effects.

Consider Bill McKibben’s recent piece in the Guardian, for example, where he writes that the Zika virus “foreshadows our dystopian climate future .” Zika, McKibben writes, is unsettling evidence ,” offering us a signal that a changing climate has forced us to take “one more step in the division of the world into relative safe and dangerous zones,” suggesting for McKibben “an emerging epidemiological apartheid.”

[Image: Mapping the potential future spread of malaria; UNEP/GRID].

So what are the microbes, bacteria, or pathogens—what are the insects, rodents, and invasive species—that might thrive in these as-yet unrealized landscapes? What future disease reservoirs will form, as coastal cities and towns are erased by the sea, and what are the specific thresholds that tomorrow’s epidemiologists should be looking for?

Put another way, what pandemics might emerge from these cities we know will drown?

After my previous blog post about the FBI, Apple, and the San Bernadino iPhone, I’ve been reading many other bloggers and news articles on the topic. What seems to be missing is a decent analogy to explain the unusual nature of the FBI’s demand and the importance of Apple’s stance in opposition to it. Before I dive […]