I think we're agreeing here: no one actually knows the boundaries of this. I'm simply not interested in being the guinea pig of where the line is of "the services that base on it". In my experience the actual deciding factor for this is when you become successful enough and worthwhile to sue. Then it's up to some judge in Texas to decide whether my service is "based on" this technology? I mean, I can't run my services at all without Linux -- I think they'd have a really good argument that my entire business is "based on it". You and I may see how this is silly, that's not sufficient for making me feel safe in a legal environment that currently rewards patent trolls for example.

> It would help if the projects were clearly stating the allowed (and disallowed) usages in advance, but it's a bit early...

If we're in "warrant territory" of explicitly stating up front every possible "OK use case" to make the user feel safe, then its either going to have so many allowable use cases as to be self-defeating, or not possibly able to predict really exciting unexpected uses and rule itself out from those domains. At the absolute minimum, I'm going to start to actually have to read over the license with a lawyer now (as opposed to one common understanding of something like MIT), since I can't imagine a "one size fits all" of acceptable explicitly spelled out use cases when the whole point of these licenses is to carve out meaningful profit areas for the project itself - something that in my opinion is going to vary greatly project to project depending on the unique features it provides.