mhusby

Just add onto this, the grace period is normally 10-20 days some registrar's leave the domain working during this time but some take it down. Then it goes into a "redemption period" for anywhere between 25 - 60 days. In the redemption period the registry tacks on a fee that is somewhere between $60 - $200 so the extra fee gets kicked up the chain.

Registrar: Who you registered the domain with

Registry: The company that owns the tld

It is absolutely something that each business will need to work out for themselves.

What I am getting at is that just because IE10 is falling in line as far as standards go that doesn't magically earn back all the trust they have spent years destroying. A track record is something that is hard to shake weather it is good or bad, so I am just saying that it is going to take some time...

If you are interested in erlang ChicagoBoss is a rails like framework for erlang. http://www.chicagoboss.org/

2nd'ed Also here is a promo code to get $97 off you first year... so you end up with 1 year of hosting for $13

HN97OFF

I have used http://www.techscratch.com/ for some help with graphics and design stuff. Its not exactly this, its mostly for small tasks (1 - 5 hours) and you get points that you can then spend to get tasks done.

One thing that I have found to help me is to break things down into very small tasks, something that I can get done in about 1/2 an hour. It can be as small as creating the signup page or doing a password reset page. I found that sometimes when I got started I would roll through a few of them, but even if I only did one thing making progress every day would feel really good.

I may be missing something, but why not just write it ci? Assuming that you have proper indexes on the tables people will be querying, I cannot see a request taking more then 100ms. Even if it is 200 you wouldn't need that matt more instances running, 40 would should be enough.

yeah I went with a 64Gb on newegg last week, with a mail in rebate and the coupon I got it for $60. For that price you cant go wrong. I have found that moving my itunes/office/virtual machines to a external I can get by fine. Right now I am eyeing the OptiBay to replace the superdrive with my old 500Gb hdd. Seems like the best of both worlds. (http://store.mcetech.com/Merchant2/merchant.mvc?Screen=PROD&...)

Yeah, there isn't really any error handling. If hn returns an error it just dies, just try reloading the page

I build this for adding GZIP to HN for browsing on my mobile, but as a nice side effect it also does ssl

https://quickhn.appspot.com/

It is just a VERY simple proxy running on Google App Engine, if you want to throw up your own the source is on github here

https://github.com/matthusby/HN-Proxy

Thanks for the feedback! I will try to get that stuff revved and submit for a update asap.

As for marketing this post is all I have done so far, and I do plan to do a follow up post when I have a little data.

Have you checked out the crash reports in iTunesConnect? They are under [Your App] -> view details -> crash reports

I guess I can see that argument, but at the same time its so easy to add memcache that it really seems silly not to add memcache for you models at are accessed a lot. Here is a simple user model, adding memcahce is a total of 7 lines. I just cant see the case where you wouldn't add this to start with:

  from google.appengine.api import memcache
  from google.appengine.ext import db

  class User(db.Model):
    email = db.StringProperty()
    password = db.StringProperty()
    sessionKey = db.StringProperty()

    def userKey(self):
      return "User.session="+self.sessionKey

    def put(self):
      super(User, self).put()
      memcache.delete(self.userKey())
      memcache.add(self.userKey(), self, 600)

    def getCurrent(self, request):
      user = memcache.get(self.userKey())
      if user is None:
        user = User.all().filter('sessionKey = ', request.header.cookie.get('user'))
        memcache.add(self.userKey(), user, 600)
      return user

I think in this reference they are not talking about storing live data in memcache, just copies of objects for faster access. So when you are getting the information about a user you check memcache first, if its not there look it up in datastore and add it to memcache. Then when the user loads a second page you can get the information directly from memcache instead of having to look it up again.

Sorry about that, here is the link: http://forums.dropbox.com/topic.php?id=33706

And couldn't they just give a warning "Hey, may not work, please don't report bugs" and for reference this is the only software that is not working correctly for me so far.

I am not sure on the details, but it has something to do with the server that they are running. Whatever the server is it doesn't do gzip or ssl, but the proxy does both :-)