FWIW, after looking into this a bit, it seems to me like that issue is only about as harsh as is warranted, calling someone out for pulling a fast one on their users.

Certainly, I would be shocked if anyone considered Karl Fogel to be some kind of asshole, and yet he can be found in the comments not only defending the premise but also defending the issue's anger.

> I realize that @ddevault's reaction may seems strong, but that's because what you are doing innocently is a tactic that many others have done maliciously. Even if your intent was not malicious, the effect is the same: you are confusing the marketplace needlessly. A bunch of people will get home, open up the bottle, and be surprised to discover lemonade when they very clearly bought "milk".

Karl Fogel shows a good example how issues like this should be treated: https://github.com/SparkDevNetwork/Rock/issues/5068

Another thing that should not be forgotten is that bug reports are there to contribute to the software. Not for support requests, not for rants, not for personal attacks on the developers, and not to explain them how wrong they are. "This wording exposes you to a lawsuit/might be offensive to certain contributors/is off-putting" would be ok.

> Karl Fogel shows a good example how issues like this should be treated

Didn't this issue (n8n) actually get resolved favorably (open-source -> source-available) while the "how issues like this should be treated" was resolved (by the maintainer) by basically saying "fuck off, we will keep lying"?

Just want to make one thing clear. It did not get favorably resolved because of the way it got communicated, it got resolved favorably despite of it.

Btw. Karl Fogel was also part of the n8n open-source discussion and that was for sure also one of the reasons why it got resolved the way it did.

They are a total kook and they make the ecosystem worse by being such an asshole all the time. Just a constant stream of garbage alienating normal people from the industry.