When I hover over anything in Safari it disappears. https://www.dropbox.com/s/7j32ek1lmb0l6zd/Screenshot%202013-...

Doesn't load in Firefox or any mobile browser I have on iOS (Chrome, Mobile Safari & Dolphin)

The Facebook login feature isn't working with the API. Getting massive headache emails now. Luckily we have lots of alternative login methods.

I hope people will see the importance of not putting all of your eggs in one authentication basket.

Noticed right after I posted. Gave it an upvote

Cool. Suggest we delete the submission and this discussion, although if you don't, it doesn't matter. I'm just a bit obsessive about tidiness. Born from working on the C2 wiki, I guess.

Edit: Although I see now that this submission has a few upvotes, so maybe we'd better not delete it. <shrug>

Glad I didn't

I love the spirit of this, but I would never put it on a serious site.

I put things on the web so people can see/use them. If they come to my site, I want them to get what they're looking for. If I'm going to serve a 404, it's either because a) I screwed up, or b) somebody mistyped something. In either case, distracting them with something else can only take them farther away from their original goal.

I wonder whether that works at all for web sites that have essentially global reach. Children from the US are unlikely to appear in Germany all of a sudden, I guess. (Incidentally, the example page for »Other countries« was in Greek which I cannot even read).

For something like Github, the more international it is, the better

I wonder—can they demonstrate whether or not it’s achieved anything? It’s an interesting idea, but I’m dubious about its efficacy. Now if Microsoft and GitHub both used it—

I use it in production. You will always have 404's and this is what I feel to be a meaningful 404.

Bought a copy. The PDF has the end of every line cut off :/

http://i.imgur.com/c4ZBUvq.png

Yep, I'll have a fix in a few hours. Sorry about that!

No problem at all. The HTML version works just fine and I prefer HTML versions to PDF's anyway.

Looks fantastic for what it's worth! :)

I uploaded a new version with the fixed PDF. Just click the download link in your receipt email and you should be good to go.

> personally think that developers shouldn't care about code beauty, because that's not their job.

I believe anyone else on your team will waste a lot of time and effort figuring out the spaghetti code you wrote.

Think. Then code.

I signed up my project. But the form seems to be the standard form you guys use for everything else. There were no fields for the specifics that are defined on the open source page.

I think it would be clearer if you had a slightly customised form for the process

we're using the same form as publishers and getting in touch on the approval with the following steps. Feel free to bounce any questions to info@influads.com

Ah ok that makes sense. Thanks for the clarity :)

Waste of money if you ask me. My opinion of this theme is that it provides a very poor user experience. The buttons do not look clickable at all. Unless you hover over them, which is useless on a mobile device

I much prefer Almost flat UI such as Gmail and http://websymphony.net/almost-flat-ui

That is definitely a forgotten debug point

Well it is front paged on HN

I assume Belhor means the UI responsiveness. The :hover transitions are a bit too long for my tastes and it definitely creates a laggy feeling.

Scrolling up and down the page feels a little laggy too (Chrome 24, Win7). Is that a drawback of how the 'responsiveness' is coded?

Going to the URL of the iframe directly is much faster for me: http://groundwork.sidereel.com/home.html

That completely made the difference, they should probably consider changing that.

Indeed, went from unusable to smooth on a nexus 7

Thank you all very much for the feedback on this, I wasn't aware of the negative impact the viewport resizer was having on these mobile devices. It is to be expected that iframes would perform poorly on them and I had included a regex to redirect mobile user agents to the home.html page to avoid them having that served up. Perhaps the mobile device detection needs a more reliable method... Any suggestions? :)