Tour for All 2020: Stage 1 Longer Race C/D

Provisional finish in 7th. This morning Zwift Power has me at 5th in the B category (which is different in this Tour For All event than a normal B category).

Category A/B are longer routes. Category C/D are shorter routes. Category A/C are 1-5 w/kg and C/D are 1-3.1 w/kg. I’m choosing Category B to have a longer ride at the lower power category. More similar to the Category C I normally ride.

Wink Begins Taking Hostages

The CNET headline is a bit less dramatic (Smart home hub maker Wink moves to a subscription plan), but there’s not too much incorrect in my own personal phrasing.

Bad ways to move to a subscription model:

  • Promise (on your product packaging!) there is no subscription fee
  • Add a subscription fee
  • Give current customers a little less than a week to move to your subscription model
  • Break existing functionality next week for those who don’t sign up for a subscription plan

Fantastical might have been a decent model for moving to a subscription plan from a pay-up-front model.

For users who only used Fantastical on iPhone, I can see the complaint about pricing — it went from a one-time purchase of $4-5 to a $40 annual subscription. That’s a big jump. But — and this is a huge “but” — Flexibits (Fantastical’s developer) went out of its way to let anyone who owned Fantastical 2 keep the features they already had access to when upgrading to Fantastical 3. If you owned Fantastical 2 you can use Fantastical 3 free of charge and keep the features you already had.

I continue to use Fantastical 2 features I paid $5 for a few years ago. I don’t need the stuff you get from the subscription, and in my professional life I can’t choose to use Fantastical anyway (but would if I could). Put between the subscription or not, I’d fall back to Apple’s calendar on iOS (which is what I use on my iPad and Mac).

When Every App Crashes

From AnilDash:

The flagship mobile apps from Google, Spotify, Apple, NYT, Venmo, Walmart and many other huge companies all broke for about 30 minutes. A simple explanation of the cause is pretty brief: they all use code from Facebook, so when that broke, they all started crashing.

Issues #1373 and #1374 on GitHub have a combined 226 comments since last night. Amazing the level of confusion in some of them.


Are we ready to ask the real questions here?Why the heck does Facebook do unwanted requests during my apps startup? What kind of info are they sending back to their servers?

Or the most real question of all – why include code in your app that you don’t understand and potentially spies on your users?


@tianqibt “a few minutes” isn’t really an acceptable response for a crash that’s taken down our entire userbase. Still crashing for me. What steps in the future will be taken to prevent this?

You’re using something you got for free and demanding top notch service and an explanation? 😂


All code is terrible code. It’s like looking behind the scenes at how sausage is made.

h/t to Gui Rambo for finding this.

Crit City Race (C)

Zwift: 23rd out of 78 (91 started).
ZwiftPower: 2nd place (provisionally? right now?)

Got roasted at the end by a train of 5-10 riders plowing by. Last lap, best lap? Have to aim for some better tactics next time.

Zwift decided to up my FTP from 218 to 230 following this race, though. Guess there’s that!

But in the Face of Evidence

From FiveThirtyEight:

Then how’d it get here at all?

There’s a simpler, if less flashy, explanation for the emergence of a new SARS. A study, published in 2018, of four rural villages in Yunnan province located near caves containing bats known to carry coronaviruses found that 2.7 percent of those surveyed had antibodies for close relatives of SARS. Thousands, if not millions, of people are exposed to wild coronaviruses every year. Most of them aren’t dangerous, but “if you roll the dice enough times,” Goldstein said, you’ll see a bad one.