[tamarian]

I'd say no. I would like to say yes, provided some clear rules are set and respected, but since the rules would complicate things, it's best to let the commercial add-on developers manage their own hacks. It's very much a case of a few bad apples ruining it for the rest.

With the increasing tendancy toward encoded scripts, embedded checks, information sending, "home calls", and conflcting privacy policies, license keys checking, and the eventual disputes between hackers and customers, vb.org staff may find themselves in the middle, even when they don't have access to the developers records or even the code, to verify who's right, or enforce anything. It could get real ugly, real soon.