node.js ko

Observer

Observer

by Speedo

44.37

overall

If the server feels slow or sugglish it’s because i’m on the front page of hacker news and a idiotic amount of traffic is being generated.

It should work properly again.

The application

Observer allows you to watch your application users in real time, and see in your browser what they are doing, all the events are duplicated and emulated.

If a user clicks on a button that triggers an alert or a other javascript interaction, the same interaction will happen on your page. You can see what the users are typing or what keyboard short cuts they are using.

If you want to interact with the following user you can press the chat button at the top of the menu bar to start a anonymous chat with them.

Don’t have time to follow all your users? No problem, all session are stored in our database so they can be re-played at a later point of time.

Judging Instructions

Just like all other sites, this demo works best in Google Chrome because it can use the full power of WebSockets. But any good HTML5 powered browser should work. Or IE users with chrome frame :)

Also please note that this is a solo entry, it was not build by a complete team of coding monkeys so please vote accordingly.

And thanks for taking the time to review this application, it’s build upon blood and tears, so I’m grateful that you guys are taking the time to review it.

Who

How

The technology

The site is build upon a custom content management system that is driven by MongoHQ’s mongodb. It allows me to edit the pages on the fly without having to push code changes. This makes it a really flexible application, where I can spawn pages by just working in the back-end of my application. New pages can be generated on the fly and bugs can be fixed without having to reboot the server and lose the persistent connection that socket.io has established with my server.

The cms allows different template engines, such a Jade or EJS. I personally think that is pretty rad.

The connections and the following are established by Socket.IO. It uses the rooms the functionality of socket.io to follow the different connections. Both the user and the observer join the same room, where the events are broadcasted to.

Administration / logged in version of the Observer runs through a different namespace so we can do a authorization check based on the information we gathered. We check if the user is logged in to the observer.no.de site, and checking the session of it. If you are not authorized to login you get notified of it.

NPM libraries used to achieve this awesomeness

useragent@0.1.2 ./node_modules/useragent 
ejs@0.4.3 ./node_modules/ejs 
underscore@1.1.7 ./node_modules/underscore 
long-stack-traces@0.1.2 ./node_modules/long-stack-traces 
connect@1.6.4 ./node_modules/connect 
datejs@0.0.2 ./node_modules/datejs 
validator@0.2.7 ./node_modules/validator 
jade@0.15.2 ./node_modules/jade 
express@2.4.6 ./node_modules/express 
nko@0.1.1 ./node_modules/nko 
mongodb@0.9.6-13 ./node_modules/mongodb 
socket.io@0.8.1 ./node_modules/socket.io 
├── policyfile@0.0.4
├── redis@0.6.6
└── socket.io-client@0.8.1

public vote

Hello people, I would like to ask you guys for one last big favor, if you love this service and would like to continued after the Node Knockout please cast a vote at http://observer.no.de/vote.

By winning in the solo category I would gain sufficient funds and toys to build a working commercial service out of it.

Votes

Your Vote

Voting is now closed.

Other Votes