Option --prefer-insecure should be --prefer-unsecure

[putridmelon]

The word "insecure" refers to a human being's lack of self-confidence, not to anything else. In all other contexts, the opposite of "secure" is "unsecure". The command-line option should therefore be --prefer-unsecure instead of --prefer-insecure.

[AGSPhoenix]

https://www.google.com/search?q=define%3Ainsecure

See definition two.

[putridmelon]

You may have Google on your side, but it remains incorrect.

[anovicecodemonkey]

The Oxford Dictionary reports it as a correct usage in both US and World English.

http://www.oxforddictionaries.com/us/definition/american_english/insecure
http://www.oxforddictionaries.com/definition/english/insecure

[AGSPhoenix]

As does Merriam-Webster: http://www.merriam-webster.com/dictionary/insecure

Definition two (again).

[phihag]

I apologize, I picked the word without thinking about it, and I'm a non-native speaker.

However, the above sources and this english.stackexchange.com question seem to agree that insecure is a good, or even the better term in this case. Also note that curl has a similar option called --insecure and the help text of wget's --no-check-certificate option uses the word insecure as well.

In any case, APIs should be kept stable, even if there is a significant misspelling. Therefore, we'll have to keep the option as is. However, in youtube-dl 2014.04.04.4, you can now use --prefer-unsecure as well.

Note that no matter the spelling, passing in the option is most likely a bad idea and only serves as a temporary workaround until we get a better mplayer interface worked out and implemented.

[putridmelon]

Sorry for my slow response, this totally escaped my attention.

Thanks very much for adding the --prefer-unsecure option, I really appreciate it :-)

I personally find it regrettable that the compilers and maintainers of dictionaries seem to take take the attitude that a word is defined by "however the masses use it", and that netizens argue cases on the basis of "what Google says" or how many links they can find to back up a claim.

Me, I know that insecure means what it means, as does unsecure, regardless of what's in Google's or anybody else's database.

However, you have a valid point about having to maintain the misspelled option as well.

Thanks again!

[AGSPhoenix]

I personally find it regrettable that the compilers and maintainers of dictionaries seem to take take the attitude that a word is defined by "however the masses use it"

That is what a dictionary is. A list of what people mean when they say a word.

Regardless, it makes no technical difference whether we have one option or two. I did have a multiple paragraph long post written up explaining how wrong you are and that you should feel terrible (I get unreasonably angry about these things), but it doesn't really matter at the end of the day. Enjoy your new option and feel free to hop on IRC or submit a new issue if you need further help.

[putridmelon]

I did have a [...] post written up explaining how wrong you are

But I'm not.

and that you should feel terrible

For what? For not bending to majority opinion?

(I get unreasonably angry about these things)

It's endearing that you admit that :-) You wish very much to be right, and I respect that. Your mistake does not lie in your desire to be right. It lies rather in your belief that invoking dictionaries, Google, the masses, or anything outside yourself, can make you right, or convince me of your rightness. It can do neither. If you wish to be right, find the truth and stand for it, irrespective of support or the lack thereof.

Good luck!