SOmething like vBSEO, encrypted to the neck, so nobody can run it without a license.
Anyway, I dont believe we should do this to hacks, we should do it to vB Releases.
If there weren't any nulled vbs around, people wouldnt come here and as a licensed user to grab hacks for him.
Anyway, theres always a way around. But encrypting vB is not good IMO. I mean, its not good to have the code encrypted because doing so, vb.org wouldnt exist.
I believe this issue has already been discussed by the developers of this product.
|