this is cool!
I made a similar nodejs application too sometime back, but mine is still with some bugs.
Node.js used to mirror DOM across browsers
21–30 of 53 posts
Re: Node.js used to mirror DOM across browsers
#22Wow.....What a nice post!!....Your post is an excellent example of why I keep coming back to read your excellent quality content that is forever updated.I would like to read newer posts and to share my thoughts with you.Thanks a lot....
Re: Node.js used to mirror DOM across browsers
#23Earlier quoted context omitted.
Suppose I send you a link to a page I own. I start this thing on said page and track what you do with the rest of the session on the off-chance that you do something sensitive with it. It's like a single-tab key/screenlogger. Combine this with traditional phishing methods (which already work) and you might get valuable data. It's going to be at least as effective as current phishing methods, with the added advantage…
Re: "sounds plenty dangerous to me" Often, it's the "sounds plenty dangerous" innovations (fire, automobile, chainsaw, theory of relativity), that provide the most utility.
Oh, certainly. The fact that it can be used for evil makes it no less impressive and useful for other purposes. But thinking of this attack makes me wonder if our browser security models are getting outdated. With things like this possible, and so much valuable data being web-based these days, is there any way of using cool things like that yet avoiding the major risks?
Re: Node.js used to mirror DOM across browsers
#24I'd love to be able to just add a script tag to my website, and then log into some web based service which shows me a list of the current sessions on my website allowing me to click on one of those sessions and monitor their progress through the site using this dom mirroring technique.
There must be money to be made in this sort of service?
Re: Node.js used to mirror DOM across browsers
#25I'd love to be able to just add a script tag to my website, and then log into some web based service which shows me a list of the current sessions on my website allowing me to click on one of those sessions and monitor their progress through the site using this dom mirroring technique. There must be money to be made in this sort of service?
Sounds like a novel way of stalking.
Re: Node.js used to mirror DOM across browsers
#26Re: Node.js used to mirror DOM across browsers
#27I'd love to be able to just add a script tag to my website, and then log into some web based service which shows me a list of the current sessions on my website allowing me to click on one of those sessions and monitor their progress through the site using this dom mirroring technique. There must be money to be made in this sort of service?
Sounds like a novel way of stalking.
... or customer support.
Re: Node.js used to mirror DOM across browsers
#28Earlier quoted context omitted.
It's done via proxy, node.js, and websockets =) No iFraming. Since we're proxying, we can dynamically hijack the links and insert JS.
What are you using for server side dom manipulation? jsdom? apricot? node-xml? libxmljs? I spent a lot of the weekend working on a webcrawler, but couldn't find a xml parser that didn't choke on the internet-at-large. Any chance you'd consider open-sourcing?
I haven't seen their code, but I'm not sure why you'd need server side DOM manipulation for this. I'd implement all of that in the browser, and just let the server handle passing events back and forth.
Re: Node.js used to mirror DOM across browsers
#29Earlier quoted context omitted.
Security risk in what? Users not paying attention to the URL bar?
Suppose I send you a link to a page I own. I start this thing on said page and track what you do with the rest of the session on the off-chance that you do something sensitive with it. It's like a single-tab key/screenlogger. Combine this with traditional phishing methods (which already work) and you might get valuable data. It's going to be at least as effective as current phishing methods, with the added advantage…
You understand this works by proxying webpages, right? The URL bar is going to show the URL of the proxy, not my bank.
If you consider this to be dangerous that's a flaw in every web browser ever, not this piece of software. This kind of thing was possible 10 years ago too.
Re: Node.js used to mirror DOM across browsers
#30I am not prone to melodramatic statements, but seeing this I had the same feeling I had the first time I started using GMail. It's not necessarily the DOM sharing, which is cool enough. I just think that the emergence of sockets in new browsers is going to bring in the "next level", whatever that ends up being. Seriously incredible, especially considering the development timeframe.
It's fun, yes, but at the same time, it's nostalgic. We've had such technology for decades. There have been desktop sharing apps for years, in Java applets etc. So whilst it's cool that the browser wars are generating a ton of improvements, none of them so far are really things that will blow users minds. HTML5 is just catching up to where other platforms were 10 years ago.
Agreed. In some ways the browser actually lowered people's expectations of what "computers" can do.
Perhaps the focus shifted.
When I first saw Wolf3D as a kid I was amazed that the computer could do that. Same when I first used a GIS.
These days when people get "excited" about something like Facebook, it's not because it's a technical achievement. It's something more human. Which perhaps is why I don't get it.
Maybe browser technology is "good enough". Perhaps the point is to be able to get apps out to people as simply as possible. It's just a URL.
Due to the fact I don't feel a point coming on any time soon I'll end here.