Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
I'm not sure at the moment. It's a bit complex - it's been elevated to MS (huzaah for contacts!) and they are calling me on Friday afternoon to go through it.
The algorithm isn't particularly special, to be honest.
I started obfuscating it when the product was in Beta and it was being tested in a few places where I knew the competition also had installations - I wanted to prevent the competitors from seeing what I was doing before it was fully launched. Now that it's out there and the competition have seen it, I'm not convinced that it's necessary.
Any thoughts on whether obfuscation should be used or not?
I ask because PlanB is now being bought by a number of organisations throughout Europe. Up until now, I have been obfuscating it, but the obfuscation is getting to the point where it is causing a problem.
Leave a comment: