Weekly output: Amy Webb, unlimited data, connected-car privacy, commercial geoint, U2F adoption, ECPA reform

The next few days will be a little crazy–starting with a 6 a.m. flight tomorrow to Orlando. I’m returning to Central Florida for the first time since 2011 to cover SpaceX’s attempt Tuesday to launch the Falcon Heavy rocket, the most powerful launch vehicle the U.S. has seen since the Saturn V. Assuming no scrubs, then I’m flying up to New York Tuesday night so I can cover Yahoo Finance’s cryptocurrency-focused All Markets Summit Wednesday, after which I will be delighted to sleep in my own bed once again.

1/29/2018: Fireside Chat with Futurist Amy Webb, State of the Net

I interviewed Amy at this tech-policy conference. She started with some harsh words about Washington’s ability to forecast future tech trends (her stock in trade), which probably didn’t go over very well in the room even if many policymakers around here need to realize the limits of their vision.

1/31/2018: Unlimited wireless data is here to stay; so is the need to check your options, USA Today

A new study by OpenSignal finding that download speeds at AT&T and Verizon have rebounded after a slump the research firm blamed on their shift to selling unlimited-data plans provided a news peg for this column reminding readers that they may be able to save money by opting for a limited-data plan–as unfashionable as that may be.

1/31/2018: Why a car can’t protect your privacy as well as a smartphone, Yahoo Finance

Watching a few panels at the Washington Auto Show’s public-policy day last week got me thinking about how Google Maps and connected cars each treat your location history–only one lets you inspect, edit, export and delete that information, and it’s not the one that requires an oil change.

1/31/2018: The Vanguard of Commercial GEOINT, Trajectory Magazine

This is the cover story for the U.S. Geospatial Intelligence Foundation’s quarterly magazine that holds up reasonably well for the first three-fourths or so–after which comes a bit on Strava that now looks problematic.

2/1/2018:  The authentication solution government has been slow to adopt, Fifth Domain

I’ve been meaning to write something about what’s held up the usage of “U2F” security keys–the cryptographically-signed USB fobs that can protect your Gmail or Facebook account from both phishing and the loss of either your phone number or your phone. This new government-cybersecurity site gave me that opportunity.

2/2/2018: The email privacy hole Congress won’t fix, Yahoo Finance

A couple of years ago, I started thinking that whenever Congress finally passed reform of the Electronic Communications Privacy Act, it would be fun to write a post recapping how long that took. Well, that hasn’t happened, so I decided to use Groundhog Day to instead write a post recapping how long Congress has failed to fix this obsolete law.

Advertisement

How I screwed up a Strava story

A story I wrote weeks ago started to go bad last Saturday, before it had even been published and posted.

That’s when an Australian student named Nathan Ruser tweeted out an interesting discovery: The Global Heatmap provided by the activity-tracking social network Strava revealed the locations of both documented and secret foreign military bases, as outlined by the running and walking paths of service members that Strava’s apps had recorded.

The feature I had filed for the U.S. Geospatial Intelligence Foundation’s Trajectory Magazine–posted Wednesday and landing in print subscribers’ mailboxes this week–also covered Strava, but in a different light.

As part of an overview of interesting applications of “geoint,” I wrote about Strava Metro, the database of activities over time available to local governments and cyclist-advocacy organizations (but not commercial buyers). In that part of the story, I quoted Strava executive Brian Devaney explaining the company’s efforts to keep its users anonymous in both Metro and the heatmap.

Looking at Strava from the perspective of “will this show where people live?”, I didn’t even think about how Strava users might unwittingly map temporary workplaces abroad. I had my chance to clue in on Strava’s military user base from looking around D.C.–that’s Joint Base Andrews precisely outlined southeast of the District in the screengrab above–but I failed to draw any conclusions from that.

Apparently, so did everybody else in the months after the Nov. 1 debut of the heatmap, heralded in a post by Strava engineer Drew Robb that touted how “our platform has numerous privacy rules that must be respected.”

You can blame Strava for making it difficult to set a geofence around a sensitive area. But it’s less fair to hound a privately-run service built to share workout data–remember, it calls itself “the social network for athletes”–for not maintaining a database of classified military locations to be blacked out on its heatmap.

After Ruser’s first tweets, however, developer Steve Loughran poked around Strava’s system and found that he could correlate the heatmap with the records of individual people by uploading a fabricated GPS file of a workout to spoof the site into thinking he’d jogged along the same path. That’s a deeper problem, and one that appears to be Strava’s fault.

After I asked Strava to explain these new findings, spokesman Andrew Vontz pointed me to a Jan. 29 post by CEO James Quarles pledging action to make privacy a simpler choice in its system.

I hope that they do so forthwith. Meanwhile, a fourth of a magazine feature with my name on it (at least it’s the last fourth!) looks dumb. It’s true that every other journalist to write about Strava between November and last week also missed these angles–but I may be unique in having a positive piece about Strava land this week. That’s not a great feeling.