I mean, yes, I do think it's "on them", I do think it's reasonable to criticize the definers of jargon terms that confuse people due to mismatching with their p

I mean, yes, I do think it's "on them", I do think it's reasonable to criticize the definers of jargon terms that confuse people due to mismatching with their plain reading of the terms... I think your other examples are indeed examples of the same kind of issue. For instance, I would say that "organic" is a much worse offender due to it targeting a much larger audience than our computing jargon does. I don't know whether "ethically sourced" has a technical definition that is a good match for my intuition of what it means, but I wouldn't be shocked at all to discover that it does not. But like I said, I'm sympathetic to the definers of these kinds of things. They want something that works as marketing, so they use plain words that people have positive associations with ("free", "open", "organic", "ethical"), but then those words are too vaguely defined for their purposes so they also attach further meaning to them. But then that results in this tension, where people naturally assume the words mean only what they mean, and some community of gatekeepers has to be vigilant to come in and set the record straight. Notably, we don't do this sort of thing with medicines, for instance. There isn't a community of people who have to correct peoples' use of a descriptive plainly worded jargon term like "happy pills", they are instead referred to as SSRIs, which has no plain reading and thus no potential for confusion. I agree that it isn't good for companies to take advantage of this plain reading / technical definition mismatch, but I also think it's inevitable when trying to have it both ways by using a plain-sounding term while attaching it to a technical definition.