Hey there,

Yes, I put in some rate limiting for the launchers, and it appears to have gotten backed up a bit. I'll see what I can do, but we're in a private beta right now, so I'm more inclined to work on the stuff our regular users are bringing up and worry about hn-scale later :)

That said, shoot me an email, [email protected], and I'll get you into the beta if you'd like, with access to the docs. Though honestly, so far the main support method has been through chat/im/email/skype with me or my cofounder, and we generally take notes from those conversations and turn that into docs.

if so, maybe you can cache the 'top apps', thus people can see what is it about ?

Hi I'm working with sgrove on the project. We had considered an app cacheing or reuse approach for dealing with this influx of traffic, however we wanted every one to have a fresh install experience.

We very well could have directed you to an existing unclaimed install of a popular app and saved the resources of spinning up another. We felt that this could be messy as you might end up on an app that somebody had polluted with test/demo data and settings.

We cache dependencies for popular apps.

i understand your goal. but realize that current experience is "frozen at 8%"... not a super first impression either.

just suggesting to improve the hn post consequences

Same thing happened here. It seems like an interesting idea but there are a whole bunch of questions I was left with, like what happens to my data, where is the application running, what is the end goal of the project, etc. In all fairness I didn't dig around to perhaps this is all explained somewhere on the site.

No no, no need to be fair about that, there's precious little docs publicly right now :) It'll be rectified, but we're deciding which docs to write by working with developers and end users in the private beta.

I'll add your questions http://news.ycombinator.com/item?id=2403003 and answer there - Lemme know if there's anything else you'd like to know!