It's worse than that, people don't value it very highly if it's free.
Really, what would happen if it became a for profit product? Would I pay for access to the greatest single repository of information the world has ever seen? Or would I shrug my shoulder and let Google tell me that I actually meant to query something else, and trust that the top placed link is really the best?
Wikipedia is already monetized, but not like most platforms:
How many times have you actually clicked the "donate" button when Jimmy Wales asks you to?
It's still interesting to note that the Wikimedia Foundation is getting more cash in donations than it requires to operate. If it wasn't a non-profit, it would actually turn out a profit.
Both of which are probably on the low end of what the content is worth.
When you really think about it, we write off free access to the largest repository of information ever as something which just happens to exist.
It is happening with me right now. I am searching for a Jekyll theme, and there are a bunch of free ones, but because time is money I will only try the paid ones.
Mobile app stores are a cesspool of terrible ideas and naive people who think if only they give away their time developing free software some company will notice and bless them with a job. The few gems to be found are a stark contrast.
The problem with these proposals is that it creates an unequal relationship; some developers have more rights just because they started the project, even if others have contributed significantly.
My intent is to go for full-on AGPLv3 and not accept PRs initially. If someone sees a bug they can tell me "if these options are picked there is an infinite loop" or "you've missed input sanitisation here" and I'll put together a fix for it. That way all the code is mine, I have full control, and I don't have to worry about treading on someone else's toes if I relicense later. When/if I later decide upon a more permissive license, or to try monetise through commercial licensing, or if I chose another route entirely, then changing will be frictionless.
In the meantime anyone wanting to work on it themselves because I'm too slow, they don't want to work my way, or "just because", are free to fork (assuming they are happy with AGPL), or contact me to negotiate other terms, or write something themselves from scratch to deal with the itch (again: these are not Big Things, I certainly don't expect to be releasing the NextBigThing™).
What's commercial use? Creative Commons has been messing around with this question for something like decade and has never come to a resolution.
So, sure, advocate for changes to the open source definition if you like. But there are reasons that a lot of people are resistant.
You can always release your software under the AGPL (which is an OSI-approved license)--which would effectively prohibit its use by cloud providers. Probably very few others will use it either but that's the tradeoff you make.
But I know other people who think that using NC content even on a personal blog that uses Adwords is a strict no-go. Or you try to define NC in terms of US tax code which is fraught for a lot of reasons.
ADDED: Personally I think the latest round of the licensing wars is overblown. If you want to use a more restrictive license, go for it. Just don't expect the development model benefits of open source software. Of course, most open source doesn't reap those benefits either because vibrant communities are relatively rare.
Edit: and another question alltogether is whether it's going to work well against FAANG with nearly unlimited cash to employ hordes of lawyers