What do Howard Stern and Donald Trump have in common? Both are cynical showmen who care about nothing but their own bottom line.
Remember when Howard Stern ran for governor of New York? Howard didn’t want to serve, the campaign was just a publicity stunt for his radio show. Same thing is happening now with Trump, but on a much larger scale. Trump’s campaign is just a massive marketing campaign for Trump Enterprises.
Howard didn’t want to serve, and found a reason to drop out. So will Donald.
In 2016 we as a nation are facing an important decision, which will have a major impact on our lives for many years to come. Making the right choice will lead to happiness and prosperity. Making the wrong choice will lead to tyranny, and will send us back to the Dark Ages.
I am speaking, of course, about whether to install Facebook Messenger.
Facebook Messenger has never been a reliable communication tool for me. Now the Zuck Empire renders it even less so by making Messenger not work in the mobile browser. The message is clear — get on, or get off. I won’t be installing Facebook Messenger, so its utility diminishes even further for me. I am getting off.
TL;DR: It depends. Strava is Facebook for cyclists. Ride with GPS is the serious geogeek/cyclist’s companion. I keep both apps on my mobile device, but I use mostly Strava will be using exclusively Ride with GPS going forward. My decision was made easier by my friend Adena Schutzberg — a digital mapping (GIS) and endurance athlete veteran — who told me that her bike club, the Charles River Wheelmen, selected Ride with GPS as their route distribution tool.
With the demise of Google My Tracks, I needed to select an alternative — a replacement app with which to track and record my bike rides on my Android phone. (I briefly considered getting a dedicated bike computer (e.g., a Garmin), which many veteran cyclists swear by. But the thought of owning and charging and managing yet another device quickly rendered this option untenable.)
On January 30, 2016 — the day of the Google My Tracks deprecation announcement — I went back to Strava, which I had signed up for years ago and subsequently replaced with My Tracks. The reasons I ditched Strava in the first place are still there today — it has way too much stuff. Challenges, badges, game-like “social” features are to me bloatware that I don’t need. But I kept using Strava, because it did what I needed — kept track of my rides.
Then I signed up for a charity 40-mile ride, which published the routes in what the organizers called “Garmin” and “Ride with GPS” formats. Garmin not being an option I was willing to consider, I looked at the “Ride with GPS” format, which turned out to be a GPX file. Can you import a GPX file into Strava? No. So I signed up for Ride with GPS.
I paid $2 for a three-day pass, downloaded the Tour de Franklin route to my device, and set out to test the navigation capabilities of Ride with GPS — in my car. Which is where I ran into problems (almost certainly attributable to my aging device). I couldn’t get the audio or spoken alerts to work no matter how many things I tried, and towards the end of the test — after about an hour and a half of driving — my device’s battery was at less than 10%. It was now clear that I wouldn’t be able to use Ride with GPS with my current device (Google Nexus 4) to navigate along a four-hour ride.
[UPDATE May 5, 2016] My technical problems with Ride with GPS were caused by user error (me), and were swiftly and expertly addressed and resolved by RWGPS tech support represented by Tomas.
Back to The Google. After some digging I found a beta script on Strava Labs that allows users to upload a GPX file and convert it to an editable Strava route. At the time of this writing the script does not create new geometry data in Strava, only best-matches GPX data to geometry that is already in Strava. This was close enough in my use case, and my experiment ended. Strava won this round, if for the wrong reasons.
CONCLUSION: If I had to make the switch away from Google My Tracks today — knowing what I know now — I would select Ride with GPS right away. It is an excellent app with serious mapping chops and outstanding support.
The formula for Easter — “The first Sunday after the first full moon on or after the vernal equinox” — is identical for both Western and Orthodox Easters, but the churches base the dates on different calendars: Western churches use the Gregorian calendar, the standard calendar for much of the world, and Orthodox churches use the older, Julian calendar.
The two churches vary on the definition of the vernal equinox and the full moon. The Eastern Church sets the date of Easter according to the actual, astronomical full moon and the actual equinox as observed along the meridian of Jerusalem, site of the Crucifixion and Resurrection.
Snapchat began crashing my Google Nexus 4 phone about two years ago. I did a lot of research on that, found out that Snapchat and Google were pointing fingers at each other. I blogged about this, then removed Snapchat, then removed my old blog.
Two years later I reinstalled Snapchat on the same device, hoping that by now the problems would be resolved. Surprise, surprise! They’re not. Snapchat still crashes the device.
I will dig up and repost my old write-up here in a few days. But for now, bye bye Snapchat!
[UPDATE March 17, 2016] Below is a summary of my numerous posts (on my now-defunct blog ObliviousAT) on the topic since the issue first manifested itself on August 5, 2013 when my Google Nexus 4 device updated itself to Android 4.3.
An important distinction from similar reports: While others report the crashes beginning with a 4.4 upgrade, for me they began with 4.3.
August 5, 2013: Snapchat crashes and reboots the device
August 23, 2013: Three (three!!!) Snapchat updates after the release of Android 4.3, and the crashes seem to have disappeared. I applaud Snapchat, but keep wondering why Google/Android hasn’t taken any action. It seems to me that now Snapchat knows how to crash Android but chooses not to. Android watches idly and passively.
August 24, 2013: Snapchat crashed and rebooted the phone.
August 27, 2013: Android 4.3 updated itself to 4.3. Weird numbering sequence, but whatever. As long as the device stops crashing and rebooting, I’m cool. Snapchat hasn’t crashed since the 4.3 to 4.3 update, but I haven’t used it much. Unconfirmed reports from another Nexus 4 user indicate that the crashes still occur, although less frequently.
September 13, 2013: Snapchat still crashes the phone, after 3 Snapchat updates and one Android update. Phone vibrates for about ten seconds, like it’s in the throes of death. Then reboots. Why is it so easy to crash the phone?
October 9, 2013: Snapchat points the finger at Google, says a bug in the Nexus 4 Android 4.3 operating system — an issue out of Snapchat’s control — is to blame for the device crashes and reboots.