There is far too many hackathons for non-students, such as AngelHack, BattleHack, Startup Weekend (arguable to whether an hackathon) amongst many more.
A lot of student hackathons accept dropouts too on a case-by-case basis. But there's hackathons for all :)
This was partly an instinctive decision, but I think it's too easy to go mobile. Part of the reasoning for having a tangible card is the novelty and the failproof factor behind it.
Okay, Phishing 2.0 may have gone a bit too far. I hold my hand up there. As for LastPass, I use that and it's great -- but this poses a problem for those who don't use LastPass, etc. or those who use mobile.
With relative ease, you can build websites with a cheap $10 SSL that can impose to be a PayPal page. JavaScript can provide phishing and accessing cookies, but beyond that, I'm not really sure what else it can offer.
It may be simple code, but I think the title of the post explained that.
It was purely gathering thoughts to what I consider a flaw. Sure, it's not the only way to do it -- but this is it in it's simplest form.
False redirections is the principle. I'm not sure how to fully eradicate it in that sense, but I think to bring attention to the possibility is somewhat beneficial rather than sensationalist.
W3C only do web standards: HTML, XML, CSS, XSL, etc. According to ECMA International, they maintain JS. But I'm not sure, each browser does it's own thing.
A lot of student hackathons accept dropouts too on a case-by-case basis. But there's hackathons for all :)