Re:Reverse engineering guide for beginners: Methodology and ...
by bwidlar on Monday June 12, 2017 @11:19AM
(#14537980)
Blank page without javascript. Bye.
[ Parent
| on HN ]
Re:Reverse engineering guide for beginners: Methodology and ...
by dylz on Monday June 12, 2017 @01:27PM
(#14539049)
0) that's most definitely not blank page, I have noscript and it does load content.
1) what kind of response is this?
Re:Reverse engineering guide for beginners: Methodology and ...
by elboru on Monday June 12, 2017 @01:32PM
(#14539088)
I have JavaScript enabled and it showed a blank page for me too, I had to reload the page a couple of times, I guess it's getting some traffic from HN
Re:Reverse engineering guide for beginners: Methodology and ...
by bwidlar on Monday June 12, 2017 @02:07PM
(#14539447)
Using JSBlocker here. no content.
Just doing some futile effort to show web developers
that to get some basic text without javascript is cool.
Of course, do whatever you want with your site.
Maybe I was a bit rude.
Re:Reverse engineering guide for beginners: Methodology and ...
by dylz on Monday June 12, 2017 @02:09PM
(#14539460)
Noscript+Firefox here. There's full content - the entire page has a JS-disabled full text of every post wrapped in a large <noscript> block.
Does jsblocker completely wipe out noscript tags or something?
Re:Reverse engineering guide for beginners: Methodology and ...
by tokenizerrr on Monday June 12, 2017 @01:43PM
(#14539212)
Idiot who voluntarily breaks their web browser, then complains that it's broken. Bye!
Re:Reverse engineering guide for beginners: Methodology and ...
by tempfs on Monday June 12, 2017 @02:16PM
(#14539534)
Context: Visiting a website written by/for reverse engineering, a subset of Hacking.
Assertion: Visiting a hacking website with Javascript disabled is a bad thing.
Hmmm...
Re:Reverse engineering guide for beginners: Methodology and ...
by tokenizerrr on Monday June 12, 2017 @02:22PM
(#14539593)
Not a bad thing. You are obviously more than free to configure your browser however you want. Just don't whine about it. Maybe give some constructive criticism (It would be nice if..., Maybe you could consider to...).
Or just open the developer console and inspect the source, like a hacker/reverse engineer.