Re:Improving our homemade JavaScript obfuscator
by javajosh on Monday September 09, 2019 @11:00AM
(#20918805)
I would guess he was or is looking to defeat obfuscation of some bots (see his previous post https://antoinevastel.com/javascript/2019/08/31/sneakers-sup...) and then got distracted/fascinated by the techniques the obfuscators used. I'd be generous and read the post in the satirical style of "10 ways you can screw up the web".
BTW I totally agree with the sentiment that obfuscation is bad - and I would include shipping bundles without sourcemaps. The web got popular because of transparency, and people learning from each other. (If you really have IP-expressed-in-code you want to protect, don't ship it to clients!)
Re:Improving our homemade JavaScript obfuscator
by lultimouomo on Monday September 09, 2019 @06:53AM
(#20916966)
He's a researcher, he might be working on browser fingerprinting so that browsers can avoid it. That's how I interpreted it, at least; the fact that he interned at Brave seems to confirm it.
Re:Improving our homemade JavaScript obfuscator
by cannedslime on Monday September 09, 2019 @07:10AM
(#20917054)
Seems like most of his work on fingerprinting is centered around bot and headless browser detection.
Re:Improving our homemade JavaScript obfuscator
by hombre_fatal on Monday September 09, 2019 @10:28AM
(#20918502)
> So obviously the work he does is for ad agencies that frankly never gave two fricks about performance.
Yikes, super hostile about an assumption you pulled out of your bum. Let's not dismiss other people's work so flippantly.
Re:Improving our homemade JavaScript obfuscator
by cannedslime on Monday September 09, 2019 @11:00AM
(#20918806)
You are right. In hindsight it wasn't a reasonable assumption.
Unless you are making a browser game and want to make life sad for cheaters, I don't really see a need or reason for obfuscating, and even then its not even ideal and a biproduct of a lazy solution (ie. not running simulation on a server)