3 ms·
Please STOP that.
by hungryforcodes 5y ago
Please STOP that.
- cybernautique 5y agoI'll make you a promise: if your code never ends up on my machine, I will never try to reverse it. Otherwise, all bets are off.
- hungryforcodes 5y agoWhy would I put it on YOUR machine? It's my code. Don't hack my servers, or all bets are off. /s
- quickthrower2 5y agoJS is often (but not always) transmitted from the server to execute on the client machine
- hungryforcodes 5y agoYou've never heard of NodeJS?
- quickthrower2 5y ago(but not always) <~ this includes nodejs
- cybernautique 5y agoFriend, I'd love to come to an agreement that your code won't end up on my machine. I'm buying beers when we get together.
- squeaky-clean 5y agoDon't request it then :p
- cybernautique 5y agoIf it's not part of any service that's marketed to me, I won't. However, if some vendor wants to run code on my machine, I _will_ be inspecting it.
- oauea 5y agoNo thanks. Anything you submit to run on my machine is fair play :-)
- hungryforcodes 5y agoThis code should never run on your machine. :P
- oauea 5y agoThen why are you obfuscating it or even worried about people deobfuscating it? This thread is about Javascript.
- hungryforcodes 5y agoDude, I write financial applications in Node. Node IS javascript. These applications run on the back end. Some of the API facing VMs have been attacked and so to be honest I've configured them so that if someone did get access to them, they wouldn't find much. Maybe just some API keys I can invalidate. Although I probably won't do it -- an obfuscator like this could be very handy here.
- Madeindjs 5y agoDid you give a try of Deno. This is a JavaScript runtime but it produce a single binary. This would make sense in your case because it can be harder to inspect it.