7,119 karma · joined March 16, 2009
Great idea, but just because you believe in an open enterprise doesn't mean you should go around lifting everyone else's hard work to kickstart your own.
EDIT: I sit corrected. The dashboard is a dead rip off of Pivotal. I just did a comparison of one of the dashboards linked above to the source of the tracker on one of my projects. Shared class names throughout, exact same structure.
I expect this out of an MBA with no idea of the culture and ethos behind dev, but someone who's at least knowledgable enough about HN to post it here. Wow, that's a new low. At this point, saying you're going to send private emails of apology isn't enough, if you want to be truly open the only way I see to repair your reputation is a mea culpa on your blog. Really disappointed.
http://www.theatlantic.com/national/archive/2010/10/for-the-...
I can't wait for the material for this to come out. It'd be great if it was on GitHub or some similar service so we there's an open source way to get people into open source.
Just wait until someone tries to smuggle something onboard using their iPad or Kindle. shakes head
On reporting it, the response was essentially, "oh you didn't have to go to that much trouble, you could have just used your user/pass from curl…" Completely obvious to the fact that they're app/site was completely vulnerable to session hijacking.
One of the problems of app frameworks, if you don't know what they're doing (and more importantly, not doing) you can get yourself in a heap of trouble before you even realize there's an issue. But boy, you sure can make it to market fast. shakes head
Doesn't matter how good of a hacker you are, if they haven't heard of you or what you do, you still have to impress. I've known a lot of gifted hackers that sound like buffoons when they get sidetracked and a lot of mediocre (but generally very successful) coders that don't get phased by anything.
I think Damien and crew can and will get their pitch down and find a funding source in the near future. My money's on this one being one of YC's shoulda's.
Are you looking to generate code because you want to write a DSL (or full language) and have it spit out valid JavaScript? Jison (http://zaach.github.com/jison/) does that.
If you're looking for code generation just because you're coming from Java and think you need to generate code because everything is so complex and that simple tasks require 5+ classes, each implementing more interfaces than that, and… well, you're in luck. JavaScript is much simpler than that. Welcome to modern languages. :-)
The first book is aimed at getting your started down Git with little or no previous knowledge, the second book serves the same purpose assuming you have a basic grasp of VCS, but it serves a dual role as a reference.
Check out some of the excerpts that are available on the book's site to get an idea for what it looks like. The idea is that it gives you a quick reference when you're trying to remember how to do a particular task.
This book is much more concise and assumes the reader has a basic understanding of version control systems and is looking to get up-to-speed on Git.
Most of these startups treat the iPhone as if it were some magical device that's plugged straight into their API. I actually participated on a Get Satisfaction thread for Gowalla where one person claimed they liked that it was iPhone only (which dates how long ago it was) because it made it "secure" and couldn't be "hacked the way Foursquare can."
Needless to say, they were disabused of that notion pretty quickly when checked in at the Gug, the Apple flagship store in London, and my home within the space of 30 seconds. It literally took 3 minutes to figure out - most of which was spent setting up my iPhone to proxy through my laptop. They were (and keep in mind, this is back when Gowalla was still iPhone only) sending everything in clear text.
They also didn't regenerate session IDs for anything at the time. I logged out and logged back in, same session ID. I logged out via my iPhone, loaded up their site and changed my password, then logged back in, same session ID. Basically, once you had sniffed one session ID you were set. I tried it a week later and was still able to use the same session ID without any problem.
It's amazing that things like session hijacking are so unknown and unfamiliar to people people relying on web frameworks to do everything for them. At the time they were using Merb---I found out by hitting an "/unknown/and/unknowable/" page and seeing their backtrace output. Session hijacking is a solved problem, why they were subject to it I can't fathom.