Protecting Javascript Code/Logic

[DS]

Hi,

I am looking for an advice on how to protect our javascript code logic of Chrome Extensions/App.

Google Program  Policy says "Where possible, make as much of your code visible in the package as you can. If some of your app's logic is hidden and it appears to be suspicious, we may remove it."

Recently, many of my extensions are all TAKEN DOWN just because I had minified my javascript code logic for the sake of performance and hiding some logic.  I don't wanted somebody else just copy paste my code and create copy of similar extensions, it did happen several times.

So, is there any way to secure our javascript code/logic?

Regards,

DS

[Andy Kenward]

I think the only way to do this is the put your logic on a server and making calls to it from your extensions to get a response with logic results.

[Mohammad AlBanna]

I'm having this problem now, please share with us what have you done to get your extension accepted?

[Daniel Herr]

I add a check somewhere in my code that checks if chrome.runtime.id is equal to the id of my extension in the webstore, so that if my code is just copied it will not work without being modified.

[Omnray]

More interesting question is what to do if JS code is just generated, for example from Dart language or other languages, as for example in my work.

Also i agree that minification though not completely remove plagiats incidents and pirates yet SERIOUSLY reduce such issues. 

And this is in fact have real time and resources price, especially for small indie developers.

Also, as i know, this is not meantime an a paragraph from a Google Program Policies, it's from FAQ. 

So if this is the only reason why your extensions taken down then it's somebodys petty tyranny. 

Although remains unclear how to deal with it, and unfortunately this is not a first such incident here.

On Tuesday, July 15, 2014 2:29:41 AM UTC+3, DS wrote: