It would be great to see a heatmap of all the tweets that they've collected since November 1st. The real-time thing is pretty cool, but I think it would be interesting to see the most active locations from the last few months on a higher resolution heatmap.
Or even better, let the user select between fixed time periods (all time, one month, one week, etc.).
"A few companies (such as ScanScout) were acquired by other private companies, so I include those in the "still alive and doing well" category, since it was not an exit from the investor perspective (no liquidity)"
How common is it for investors not to get liquidity in this situation?
Acquisitions made primarily with private stock really fall into two buckets:
- Those where the private stock is worth more than cash. It would have been a good bet to get pre-IPO Google stock instead of the same amount in cash.
- Those where the acquiring company stock is equally risky and the acquisition is made as a last-ditch effort (fire sale, consolidate investor portfolio, etc)
Seriously though this looks like an amazing piece of software that will finally bring the full power of CSS3 animations to a much broader range of designers.
I cannot agree with this advice enough. Working for a startup, even as a summer intern, will give you a much clearer idea of what it actually means to run a company than reading HN every day.
You may even realize it's not what you want to do after college.
I know plenty of entries from the Node Knockout competition that fit this description perfectly. I wonder if Mozilla was inspired by what they saw at Node Knockout to put this on? There were a bunch of high-profile Mozilla employees judging.
A good place to start is http://html5boilerplate.com/. This provides a good starting point and includes the modernizr library by default, which makes it very easy to check for compatibility with HTML5 features like canvas, video/audio tags and websockets.
Dive into HTML5 by Mark Pilgrim has also been a helpful reference for me.
Thanks for all the feedback. This was my entry in the Node knockout competition, along with @ollerac and @steadicat. This app was built using the awesome sockets.io library which made it simple to send realtime messages without dealing with cross-browser compatibility issues. Really the server's only job is to pass messages back and forth between the clients, who do all the work of detecting the formations and updating the other players when they move.
Really happy to see socket.io working for you guys. As someone mentioned, not only should it enable WebSocket for Firefox, but also IE6-8, iPad, iPhone, Android, WebOS, Safari 3, and others (even if connected through cross-domain)
Some other projects from the knockout leveraging it:
What I find amazing is how much fun people are having with it despite the fact that we had no idea what the game mechanics would be until the last minute.
We basically started with a board of pixels, and everything else just evolved through testing and laziness ("what's the simplest thing we can do to make the game slightly less pointless?").
I think that this just the beginning for Teevox. When I met the founders last spring they were showing off a prototype iPad app that was sort of like a live newsfeed for television. As you watched a show it would pop up additional information about what was going on at that moment, like who the actors were, what song was playing in the background, trivia, and I'm sure in the future targeted ads.
I think the integration with Twitter and Facebook also indicates that they're going to be building some social features into the app, which would be pretty interesting to see. Anyway, definitely keep an eye out for these guys.
Or even better, change the default IP address for the admin login. This attack relies on a bunch of hidden iframes loading IPs that are common default addresses of the admin login page.
Twice I've had routers notify me that 192.168.0.1 is in use by another network service and automatically remap its own services to 10.0.0.x. One of these times was due to a DSL modem's web administration being on 192.168.0.1.
The attack/code he showed cannot, but what you can do it write different iframes. Here is an example:
a+'.'+b+'.'+c+'.'+d
where a=192 b=168 c=0-255 b=0-255
Of course this could be any private network address range[1]. Next you would use document.write or .innertext to make these iframes. Personally I wouldn't stop at the first one. I would log all the frames that loaded into an array and from there test them further. I would also get the users IP address and tack on :80, :8080, :21, ect and see what I am presented with- web torrent frontends, ftp servers, ect.
Or are there parts (like the spam detection algorithm) that are kept secret?