@ShortwaveCoffee in south Minneapolis was closed when I visited at noon today, 8/24. Lights out, door locked. There was no sign on the door. Anyone know what is going on?
@WPezDeveloper@wp_acf No, you don't get to say when to "call it a day." Can you name another hosting service that did such a misfire on this issue? As for risk, I'll not trust @wpengine on future alerts if they don't provide some accounting for what happened, and indicate how they will do better.
@tdmoose@frontendben@wp_acf@wpengine Let's call it a day. Threaded ideas on Twitter doesn't work. What @wpengine did was a simple CYA. There was far more risk in not doing what they did, then what they did. Damned if they did. Damned if they didn't.
@pluginvulns@frontendben@wp_acf@amberweinberg@wpengine What I want to see is evidence that @wpengine made this available, not, that a report was out in the wild. This was not in ther email, or on their site, even logged in as a user. Their techs were not aware of it, or failed to disclose it.
@WPezDeveloper@frontendben@wp_acf@amberweinberg@wpengine@wpengine support was not in sync with the message in the email. I was told by their representative to remove the @wp_acf plugin. When I confronted the tech with the contradiction, he backtracked a bit. They really didn't have to handle it the way they did.
@frontendben@wp_acf@amberweinberg@wpengine Um. Could feels like the keyword. They suggest a warning to assess risk. Let's be honest. If they didn't say anything and something went sideways they'd be screwed. Too much risk. Not enough reward. @wpengine pretty much had to do what they did. Ugly? Sure. But coulda been worse