Live data from Hacker News

Try and view the source

kurlak.com

71–80 of 86 posts

Re: Try and view the source

#71
post #49

I hit F12 in Chromium, dev tools open with the tree, knowing that I'm viewing the DOM and not the source I hit the Resources tab, and there is the source. Not a problem at all. In fact, I had to remember to go back to right clicking and View Source to try and figure out why this was so highly ranked and lots of the comments confused me. Now I see why... but just like using JavaScript to try and detect right click, us…

> I bet someone does it on their live site. I doubt it, as this method breaks forward/back functionality, thus probably breaking most sites. Having said that, for all links, you could do a further re-write using the history API, before allowing the redirect to take place. I guess that would actually make it usable even if, as you say, it's futile in the end.

Many sites (hi, Twitter; #! you, too!) happily break the back button. It is a standard technique to "boost" engagement and "reduce" bounce rate. Seems spiritually inline line with this view-source gimmick.

Re: Try and view the source

#72

Earlier quoted context omitted.

You do know about `curl`, right?

Why use a popular utility when you can write your own in CoffeeScript !?

Because coffeescript runs in any browser and is easier to install under more platforms and security configurations than curl? The browser is the VM of the Internet. It is more standard that POSIX now, for non-system level user space functions, at least.

Re: Try and view the source

#73
post #66

cute trick. I'll definitely use it as an extra security measure next time I'm working on something that leaks an id in the source

Please post the URL of your site, so we can all enjoy the functionality and not see any leaked IDs. And some AWS functionality would be great, I would love to use EC2 cluster computes on the "free" teir...

Re: Try and view the source

#74
post #71

Earlier quoted context omitted.

> I bet someone does it on their live site. I doubt it, as this method breaks forward/back functionality, thus probably breaking most sites. Having said that, for all links, you could do a further re-write using the history API, before allowing the redirect to take place. I guess that would actually make it usable even if, as you say, it's futile in the end.

Many sites (hi, Twitter; #! you, too!) happily break the back button. It is a standard technique to "boost" engagement and "reduce" bounce rate. Seems spiritually inline line with this view-source gimmick.

Well, it's not really the same.

On Twitter if I'm viewing an individual tweet page, and then click onto the authors profile page, and then click "back" in my browser, I will not be redirected to a different page altogether like in the OP's demo.

Re: Try and view the source

#76
post #56

Earlier quoted context omitted.

Why is this possible? Is there a way to surpress this weirdness? I want to be able to trust my address bar again.

I believe that RTL character is one of the main failures of UNICODE. This should be part of the markup / rich text, not part of the plain text.

I use it when I write Hebrew mixed with English...

Re: Try and view the source

#77

Right mouse button > inspect element. Wasn't aware there was another way...

That's not view source. You are looking at the current state of the DOM. Usually, it will be similar, but what you're looking for is the source that your browser received from the server. Inspect element won't give you that.

Re: Try and view the source

#79
This is dumb. What's the point? "OH NO, I CAN'T HAVE MY HTML SOURCE GOING OUT WHEN I SEND IT TO PEOPLE TO BE RENDERED BY THEIR BROWSER." Derpity derp derp.

Look, anyone who wants to see the source will get to it. Anyone who doesn't want to see the source won't even try. All you're going to do is make people think you're paranoid about your top secret HTML. Hope you got a patent for your and

tag configuration...

Re: Try and view the source

#80
This is very interesting. I tried with the View Source option. Failed. But using the Debugger I got this:

Source history.replaceState(null, null, 'source.html' + String.fromCharCode(8237));

Can you view my source from Chrome?

Post reply on HN