> What they did was suddenly pull the plug on a free, public service for one specific user, which just happens to be a competitor.
Or, to rephrase:
They pulled the plug on one user who happened to be hostile, and who was abusing their free resources by issuing hundreds of thousands of requests a day.
Which, when you phrase it that way, not only sounds reasonable, it sounds obvious.
What you, and other's, are missing is that WPE is not a typical user. They're a corporation with hundreds of thousands of customers. Using your free resources is expensive. Like, money expensive.
This is like if you set up a free little API and then Amazon decided to use it. Would you let that fly? Would you foot the bill? What if Amazon is now your competitor? Surely then you'd happily pay the bill?
Get real. You would 100% do the same thing in that situation.
> They pulled the plug on one user who happened to be hostile, and who was abusing their free resources by issuing hundreds of thousands of requests a day.
Well, I'm not really seeing the evidence for abuse, to be honest. They were using these resources like any other WP hoster.
> What you, and other's, are missing is that WPE is not a typical user. They're a corporation with hundreds of thousands of customers.
As are Automattic, Pressable and many others.
> This is like if you set up a free little API and then Amazon decided to use it. Would you let that fly? Would you foot the bill? What if Amazon is now your competitor? Surely then you'd happily pay the bill?
This is painting the case in a way that I don't see supported by the presented facts. Just to be clear:
If I provide a free API and Amazon suddenly starts using it, increasing my expenses by an order of magnitude, then yes, I'd block them immediately.
If, however, my API is used by millions of customers, advertised as free and some percentage of these requests are sent by Amazon-hosted versions of my software, the situation would be quite different. I understand the intention of not wanting to foot the bill of a competitor, but in that case it does not seem unreasonable at all to give prior notice, even if just for a few days.
The way you paint the situation implies that WPEngine was suddenly DDOS'ing the API and required an immediate, unannounced blockage. But, from the facts presented, this doesn't seem to be the case at all. Also, just to be clear, this blockage affected uninvolved third parties - if this was just affecting the company, I'd probably have no compassion for WPEngine. But technically they actually blocked people and companies who bought hosted WP from WPE and a little leniency would have been a _much_ better look for Automattic.
Also, just to be clear - this API was provided by the WordPress Foundation, which is not a competitor of WPE. Automattic is. This seems like a major conflict of interest.
I do get Matts motivation of not wanting to provide free services for a company he regards as really bad, but the way this was handled in terms of public communication, shaky legal accusations, actions with uncalled for immediacy and overall emotional language is just not a good look. This could have been and should have been handled much more professionally, at least in my opinion.
Or, to rephrase:
They pulled the plug on one user who happened to be hostile, and who was abusing their free resources by issuing hundreds of thousands of requests a day.
Which, when you phrase it that way, not only sounds reasonable, it sounds obvious.
What you, and other's, are missing is that WPE is not a typical user. They're a corporation with hundreds of thousands of customers. Using your free resources is expensive. Like, money expensive.
This is like if you set up a free little API and then Amazon decided to use it. Would you let that fly? Would you foot the bill? What if Amazon is now your competitor? Surely then you'd happily pay the bill?
Get real. You would 100% do the same thing in that situation.