> If you want to be specific about the meaning of open source, just say "OSI open source" or something.

is wrong. "OSI open source" and "open source" are synonyms.

Exactly. In common, everyday usage, when people talk about "Open Source" this is what the majority mean. It's not a "de jure" definition, but it is a "de facto" definition. Open Source means compliance with the OSD. There are terms for those other licenses - "shared source", "source available", etc. Use them if that's what you mean.

The OSI is really just a way of branding certain licenses so IT departments at companies can point their legal departments at the website and say, "Look, this is legit." We forget today that in the 1990's people would assume that software they didn't pay for was shoddy, or that if they were running it, it was stolen and they were going to be audited and sued.

I think Amazon running their own ElasticSearch service and competing with Elastic is entirely faithful to the original spirit of free software, where Stallman was backporting innovations from commercial Lisp Machines onto the MIT free Lisp Machine OS that anyone could use.

There is the model right now of founding a company to host your software or similar as a funding model. While it is popular, I doubt it is any more sustainable than any of the other models we've seen. My lesson from all of this is that capitalism lacks funding mechanisms for producing commons, and that the proper solution is to produce non-capitalist avenues for doing so.

I am the people. I do not agree. Now what?

Worst case? You walk through use life using terms in non-standard, idiosyncratic ways, and people are constantly confused by your speech, or argue with you because you don't have a shared understanding of the world.

You can't just hand wave that ambiguity away and pretend that only the OSI definition is understood and used. You have to accept the "open source" is an ambiguous term and you will need to use qualifiers or additional context if you want to avoid ambiguity when using that term.

Yet people really only know of Open Source as a common term to describe these projects.

Simply because the source is openly available to read, the licence can still say "you can read but no touchy touchy or compiling it".

While technically it doesn't stop you from actually doing this, in a court of law you'd be found to have violated the licence. So it wrecks the idea of businesses doing it, because usually the licence holder won't care unless someone is making money from it.

Free software lets you do whatever you want, but you gotta show your code. Big difference in practice, especially when it comes to running a business.