Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Yeah, it generally returns some variant of information about the technology that is powering a web application such as ASP.Net or express.


sort by: page size:

Ah ok, it is just getting all of the info that a website could potentially get from your browser.

Probably communication with the browser over a kind of web API.

Interesting. So this could be used internally in a web app i guess.

Nah, it does not power the web in any way. It is a html/java script application framework.

Nginx powers the web. Chrome powers the web. Rails powers the web.


Good writeup on the reverse engineering.

I'm still a little confused as to what the code was doing, though. It gathers statistics about your user machine (none of which seemed too personal - basically IP, OS, country, etc).

But then what is it doing? Opening a virtual browser or simulating clicks to some ad network?


Or server-side. We used it to provide quick insight into API useage with a tool the client was already using

This is more than just a browser extension right? The data displayed comes from a server component?

AFAIK yes. The spec defines the high-level API you use withing the browser.

That's definitely server side JS, but I thought the person I was replying to meant a web server that was written in JS, but I suppose "powered" could mean that it just runs JS.

I saw that link elsewhere in this thread after my reply, and I also thought that this might have been what was being referred to.


Check out the browser extension "wappalyzer" which helps to identify technologies used on websites. It shows that the website you link to has some decently advanced stuff going on, including backbone.js and a windows server api.

Is there any more information on this that is more accessible to someone who is just a web-dev?

The browser connection API maybe?

Ah the web engine that has a different set of features depending on the browser that uses it.

Yep - the web page is a client-side app, proactively warning the user about problems in the network

Transistors, OS kernel, server runtime, server, client runtime (+ transistors, OS kernel), client, UX design, business matters.

But how it's used? A browser-based client and a bit of server code probably.


It's server-side and the browser extension unpacks the result.

The thing being described is basically a custom web browser.

It's a shared code base with the web application.

By the performance of it, probably some bloated server-side Javascript running on a toaster.
next

Legal | privacy