I think this move is great. I'd rather have this money go to the foundation, than ParseAPIco.
I think this move is great. I'd rather have this money go to the foundation, than ParseAPIco.
Of course anyone can use it commercially and for whichever reason they like. But by creating a walled 'premium' offering you are going against the premise of 'anyone can use it' since not anyone can use the commercial api.
Surely if Google or anyone wants the api so badly they're willing to pay for it, they should fund it. Why does that mean it needs to be 'locked'?
No doubt the enterprise API will add attractive value for smaller companies without the resources to process the raw dumps but I’m skeptical that this will convert Google et al into well-paying customers. Unless they start restricting the free dumps...
They are both users who are paying for the service.
The difference is that funders have political power over the project beyond the scope of their own use.
Customers are always better and more fair to everyone than funders.
Creating an enterprise product with enterprise funding means Wikimedia is directing energy and resources to serve enterprise alone. These APIs were likely demanded by larger tech firms, and I imagine they discussed with Wikimedia the possibility of creating a commercial service. Now they got what they wanted, it won't be a public resource, and it's design won't be guided by the public either.
Now the lines are very blurry. A wiser strategy would have been to create a separate private entity.
Unless I am mistaken, seems like they did do that?
"the foundation’s newly created subsidiary, Wikimedia LLC"
https://www.wired.com/story/wikipedia-finally-asking-big-tec...