curl the source down works, but it makes things more complicated. The source code is obfuscated making it incredibly hard to read. This is where using the web debugging tools shine. If I want to figure out which code is trigger what, I can just look at the call stack. I also wanted to look at the internet traffic to see how things work from there. I could intercept all the HTTP requests but that wouldn't give things like the call stack. I think it would be much easier if there's a way stopping the debugger spamming trick.
tkperson
joined 1 year ago
I see 👍. Thanks for keeping this instance running smoothly 😁
I used it about 2 weeks ago, and I remember seeing a bunch of posts.
Edit: I just checked other instances, that selection is working. This seems like a problem only exists on lemm.ee
oh that forever loop caused my browser to crash
That icon did skip over the debugger keyword, but it didn't solve my issue because it still prevented me from viewing that website's source. Now the websites just becomes super laggy. I'm assuming that there's a forever loop that does nothing running in the background now that the debugger keyword constantly gets skipped over.
Can there be a solution where I can replace debugger to something that can cause the thread to sleep for like half a second?
that doesn't work because the debugger spam spawns a new console/thread or whatever; making a "new file" every time the spam started. There's no fixed line number to skip over.
I'm trying to take a look at a scamming website, but it's using the debugger spamming to make reverse engineering difficult. Is there a way to just disable the debugger keyword? I don't really like to give the websites control over whatever I want to view.
If I checked the calendar correctly today is the last day of July?
-40C is -40F -45C is -49F
can someone confirm if this is the real oldest lemmy post?
the oldest commit on github seems like its made about 4 years ago
I used the greasymonkey script with tampermonkey without any modification. And it seems like that script magically worked even though the code doesn't look like it applies to all of the cases. Thanks, this helped a lot.
Update: After further testing, the script doesn't really help a lot, because it broke all the JavaScript used on that website all together, which explains why the debugger stopped spamming. Disabling all the JavaScript is not what I want; I want to be able to use the browser tools to trace certain functions.