I would like to know who those 100 users are.
WP7 is a fair reason in my biased opinion
IE has 1% of market share ... on HN: "Show HN" aftermath
31–37 of 37 posts
Re: IE has 1% of market share ... on HN: "Show HN" aftermath
#32I'm surprised that only 3.5% appear to be using 27" iMacs or 27" Apple displays. I thought they were pretty ubiquitous at startups now (though less popular than MBPs, of course).
Re: IE has 1% of market share ... on HN: "Show HN" aftermath
#33I would like to know who those 100 users are.
Re: IE has 1% of market share ... on HN: "Show HN" aftermath
#34Your calculation of claimed percentage of robots is deeply flawed. Not only do web browsers aggressively cache CSS files, but internet service providers also aggressively cache them. Though I'm a rare exception, my web browser is configured to ignore CSS completely, including both in-page styles and all additional loadable files. A configuration like this is very rare because it's difficult to do and the result often…
Same goes for JS files. There is only on page that I'm serving. I also know that there is 10% of visits are returning "customers". So there should be around 90 css/js files served per 100 html serves but it's not. Few minutes after releasing the app on HN I saw a swarm of "...bot" user-agents in my logs and lots of 405 errors also for the "...bot" user-agents. That made me think that the disproportion might be cause…
The tough questions is, why are you getting hammered by bots?
Re: IE has 1% of market share ... on HN: "Show HN" aftermath
#35Re: IE has 1% of market share ... on HN: "Show HN" aftermath
#36Earlier quoted context omitted.
Same goes for JS files. There is only on page that I'm serving. I also know that there is 10% of visits are returning "customers". So there should be around 90 css/js files served per 100 html serves but it's not. Few minutes after releasing the app on HN I saw a swarm of "...bot" user-agents in my logs and lots of 405 errors also for the "...bot" user-agents. That made me think that the disproportion might be cause…
After looking carefully at the image you linked to, the first 405 seems to show your web server is configured to disallow HEAD requests (and probably others). The failed HEAD requests by " bot " User-Agents (along with what looks like some bots using forged User-Agents) is interesting since a HEAD request, if successful, does not actually load the page data and should not count in your page load stats. In other words…
HN -> Twitter -> A swarm of bots sitting on Twitter
When I re-posted my app on Sunday to get extra stats I saw the same thing. The Terminator Judgment Day happened but just on Twitter.