@joreg and all the honorable members of the marketing departement
The way you provide access to the toolkit is truely progressive, and you have all reason to be proud of that. I don’t think anyone in this discussion wanted to challenge that.
This call is to a great part about the annoying way some institutions (as in research facilities, universities and corporations) restrict their access which makes introducing new software like vvvv already hard enough.
And you are right that this needs to be addressed in a professional manner. By anyone who faces these problems. I always did so, but I remember situations this was rather awkward.
Please consider the future daring individuals who try to bring vvvv into aformentioned institutions, the individuals that are not (yet) on a professional eye-to-eye level with their admins. They might be students, fresh starters in a company, new uni staff or have any other “underling’s” role in their hierarchy. I’d argue most of these occurances will be covered by the educational side of the license.
This is the scenario that is being addressed in this thread: some individual wants to see or show what’s possible with vvvv. However, internal rules and the stubborn admin simply refuse to execute something like crack.exe with with Administrator rights and, boom, there goes the chance of education on vvvv as well as a potential commercial licensing alongside that institution.
Its weird that it needs to be spelled out, but one quirky file like that does make the whole product suspicious. It makes admins worry at vvvvirst contact. Of course it also shows your sense of humor, and makes for excellent small talk with more open minded admins. But you should consider a more subtle approach if you want your product to be recognized professionally on a broader scale.