this post was submitted on 21 Nov 2023
1591 points (98.1% liked)

Programmer Humor

32568 readers
233 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] griD@feddit.de 28 points 1 year ago (1 children)

Obviously there a people in charge now who will never understand the Streisand effect. They could have kept it quiet and just... allow... the technical adept users to do their thing. Now, they are the laughing stock and get unwanted attention. Also, from my layman understanding, this shit won't fly in the EU at all.

Or, to say it differently: This is the best thing to happen to Mozilla in quite a long time and I'm a fan.

[–] Anticorp@lemmy.ml 11 points 1 year ago (2 children)

I'm out of the loop. What happened? Did someone decompile their code and find definitive proof of a throttle for Firefox?

[–] griD@feddit.de 20 points 1 year ago* (last edited 1 year ago) (2 children)

some explanation

To be fair, they used setTimeout() and not thread.sleep() because the latter isn't possible out of the box in JS ^^

[–] Wild_Mastic@lemmy.world 14 points 1 year ago* (last edited 1 year ago)

Users who have ad blockers installed may experience suboptimal viewing

Yeah let me turn off the adblocker just for having an even more suboptimal viewing due to ads. They're lunatics.

[–] Thorned_Rose@kbin.social 3 points 1 year ago

Thanks for the explainer! Also, Google's response is such a crock of shit.

[–] Synthead@lemmy.world 17 points 1 year ago (1 children)

JavaScript is an interpreted language, so no decompilation is necessary, although this is repeatable by using a Firefox user agent.

[–] kogasa@programming.dev 6 points 1 year ago (2 children)

You can build a virtual machine in JavaScript and execute compiled code on it

[–] palordrolap@kbin.social 3 points 1 year ago (1 children)
[–] kogasa@programming.dev 2 points 1 year ago

Oh yeah, you shouldn't. But people do this for fingerprinting, bot detection, and other "adversarial" scenarios where you really don't like the person executing your code. It's somewhat plausible Google would use this technique to do something scummy like this (although that is not the case).

Relevant article and a great read: https://www.nullpt.rs/reverse-engineering-tiktok-vm-1