Which do you prefer - free visible-code (crippled) OR free encrypted-code?

[Princeton]

Encrypted source code applications are a hot topic these days. Some people don't like the idea; but, others could care less.

The bottom line is ... the application, it's goals, and the people behind it. Does it fullfill a need? Is the company trustworthy?

With that said, if you had a choice, which would you prefer?

1. Free visible-code but stripped & crippled
2. Free encrypted but complete

Keep in mind that with either choices, there will be a need for the company/coders to earn an income from product to continue development and support.

Make your choice and tell us why.

[AWS]

I go for number 1. I like to be able to look through the code and modify to my liking.
I am not a trusting person so my first thought is if the code is encrypted something is being hidden in it. I can't help to think that there is more behind encrypting code then just protecton from copying.
If the free crippled version also comes in a full featured pay version I will buy the full version.

[davidw]

Those, to me, are good but hard questions to consider.

On one hand, yes, they are both free, but on the other hand, what am I sacrificing for free?

Evaluation:

The visible, stripped & crippled - what pupose does it serve? Does it serve my needs? Will it compromise other software/code/etc.? If without restriction I can work with it and I can accomplish my goal without sacrificing the security and stability of what it is connected to, then I'm usually for it. However, if it does not 100% meet my needs, if it proves to be more hassle than its worth, or if there are security issues that create backdoors into other areas that may render my operations useless, then I must pass without a shadow of a doubt.

The encrypted source code - why is it encrypted and for what purpose other than to prevent others from looking at it or altering it? If I get free, yet encrypted software from someone, and something happens to my operations, what recourse do I have (if the code is unfixable by me)? If the company that provided me with the code decided that they no longer wanted to run their business and was tied with the encryption, per se, it would render that software useless. If the company decided at a later date it wanted to start charging those who ran that software or for those who declined payment, render it or their operations useless (which was tied to the encryption), those are things I'd have to consider. I was just reading about a company doing something similar - non vbulletin software related (under a lawsuit now) where the software was free and after so long they decided they wanted to charge and force users to pay or their system would run amuck with spyware/adware/etc. that was pre-programmed in the software.

Hard choices. Can I live without it? Possibly. It really depends on your needs. I could be wrong.

[Princeton]

I understand that there are many issues to consider but that goes with installing any software.

This thread isn't about these issues it's about encrypted software ... would you consider it if the software is WHAT YOU ARE LOOKING FOR? yes or no

Crippled software is software that does not have all the features - yet, it's core is available to you. For example, a crippled visible {fill in the blanks} application is available but does not provide all the features that would come with the free encrypted full version.

The crippled visible software gives you an opportunity to test the application. It also would allow the community to help develop it's core functions/plugins/etc.

Why would anyone want to provide "free encrypted software"?

There are many reasons but for starters:

• the obvious - to protect the code from prying eyes
• to prevent removal of copyright
• to hinder development of like software
• for inhouse statistics analysis (track usage per registered member/domain - eg. each encrypted software is domain specific - no callbacks)
• to create paid addons and services for free software OR
• to provide support specifically to members who support the software (eg. paid support via development site)

As with anything, encrypted or not ... you should be able to install and uninstall with ease.


The bottom line is I'm interested to see how people feel about encrypted software.

I am aware that it's not a good idea to ask about "encrypted software" in a coding community; but I have nothing to loose.

[RedTyger]

I think that generally speaking, encryption is in the distributers interest while open source is in the end-user's overt interest. I fully respect the reasons behind encryption but unless you intend to do no modification at all it's not as useful as open/visible source to anyone wanting other than stock.

[davidw]

Originally Posted by Princeton

would you consider it if the software is WHAT YOU ARE LOOKING FOR? yes or no

given that without conditionals, I'd have to say no. With conditionals as outlined in the statement above if my personal concerns were met, yes.

[MRGTB]

I would never install a free hack with encrypted code, you don't know what your installing. Whats stopping a person from adding spyware that you know nothing about because the code is encrypted. Also like another person mentioned, it takes away the ability to customize the code to suit your own site and also check code for bugs that might have been overlooked.

Plus if it's FREE (and nothing is said about it going commercial in the future), why bother with encryption anyway. That would just indicate a person is releasing something for free at first on the sly, with the sole intentions you'll be acting as "beta testers" unknowingly to iron out bugs before it goes commercial further down the line, which your unknowingly going to have to pay for. I can't see any other reason why a person should have a FREE product with encrypted code if he intends for it to remain a free product.

We know vBSEO uses encrypted code to protect his product, but then he always did make it clear from day one that it was a commercial product that you had to pay for in the end and hand picked beta testers who applied, which is different. I really don't like the idea of something being released as free with encrypted code. Just doesn't make any sense at all to me, and makes you suspicious as to the real reasoning behind it further down the line.

Now if you was going to release a product with encrypted code for free at first (and make it clear from day one it will be a commercial product in the end). Which they will have to pay for, thats different! It all depends how you release a hack with encrypted code. If your going to act as though the hack will always be free. I strongly disagree, because there should be no reason for it to be encrypted in that case. The same way free programs like "eMule" are open source.

[phill2003]

Originally Posted by Gary Bolton

I would never install a free hack with encrypted code, you don't know what your installing.

Paying does not guarantee the voracity of the hack or trustworthiness of the person/company releasing it.


I have no problem either way and to be honest i don't think people can complain when something is free ...

[MRGTB]

Originally Posted by phill2003

Paying does not guarantee the voracity of the hack or trustworthiness of the person/company releasing it.


I have no problem either way and to be honest i don't think people can complain when something is free ...

I see your point, but if it's FREE why bother encrypting the code in the first place. It's not as though it's a paid product, so he wants to protect the code from being ripped off and sold by another person :classic:

[Marco van Herwaarden]

I am 100% folowing the line of Gary here. Free & encrypted, a deadly combination i would never trust.

(Simply because nothing in life comes for free, and i like to be able to check what/how i am "paying").

PS Ofcourse there are many more arguments for either side, but this one would already be a show stopper for me.