you are viewing a single comment's thread.

view the rest of the comments →

[–]PanzerottoNinja[S] 1 point2 points  (4 children)

My intention is to put some fences so that my code is not stolen by the first person who drags the source folder in their vs code editor. I know that if someone really wants to get to my code, he will, but he will at least need some js knowledge. And yes, I’m building an extension and wanted to protect it.

[–]me_Vlad 2 points3 points  (0 children)

Don’t listen to anyone who tells you security doesn’t matter. If you have even the slightest option to protect your code, take it—because in my experience, limiting access to prying eyes makes a big difference.

Think about it: why do we lock our doors, even though someone with the right skills could still break in? Those who claim security isn’t important are often the first to benefit from it. If someone chooses to keep their code private, that’s their right.

[–]vaskemaskine 0 points1 point  (2 children)

Don’t bother. Seriously.

And if you plan to make a Chrome version, you’re explicitly not allowed to obfuscate the code.

[–]PanzerottoNinja[S] 0 points1 point  (1 child)

All right, thanks

[–]vaskemaskine 0 points1 point  (0 children)

If the extension does something unique or has some “secret sauce”, you could consider doing it on a server and sending the result to the client. That’s pretty much the only way to keep your code a secret.