Hacker News new | ask | show | jobs
by blobman 3461 days ago
If you're getting over the bandwidth limit of 100GB or 100,000 requests per month, you could definitely afford to host your site elsewhere...
5 comments

My blog gets about 19k uniques a month for which linode shows bandwidth as 39GB. I have a side project (https://www.findlectures.com) that got 60k page views this month, but only because it was linked in lifehacker & The Next Web. Between scrapers and HTTP requests that do feature detection, the number of requests would easily be 10x the number of users.
And since you mention Linode, which has no free tier, you must be able to afford to host your site somewhere other than Github Pages. So that works out quite well!
Agreed- it's just a hobby thing though.
Just wanted to say thats an AWESOME side project!!
Thanks!
My blog serves ~500k requests per month, mostly to bots. My pages generally have few external resources; with a typical CMS site this would be more like 5M requests.

(This is with ~15k pageviews-not-from-bots per month.)

Wow. That's actually quite low.

I would have topped both limits with any single article that went to the front page of HN :D

Note that this is only human traffic. Wordpress stats have good bot detection.

Spot on. They're PAGES for info and such, not free WEBSITES.

This is why we can't have nice things. People don't accept a no that's free, when clearly they should.

I don't think there is a useful distinction between PAGES and WEBSITES.

https://pages.github.com/ advertises Websites for you and your projects., and I imagine most of the examples they show at the top get more than 100k requests, since that's not all that much for e.g. documentation or demos for a reasonably popular project. (Although it is possible that the corporate-backed projects in there actually pay for Github, just not specifically for Pages).

Just to make it clear, I'm not criticising GitHub here: It seems like they uses this a guideline/reasoning help for when someone doesn't play nice, not as strict rules to enforce, which seems totally fair. They should absolutely do something against sites misusing this service. Demanding money for commercial use would also be possible option. (they of course are also free to make strict rules for all pages, but that would have a large impact for quite a few projects I imagine)

The point is, they could have called them gh-sites. Yes. Words matter. #Duh

If your "pages" are pulling that much traffic then put on your big boy (or girl) trousers, take off the training wheels and get a proper website. GH is not a hosting service. They're "kind" enough to offer free repos and that's not good enough? Y'all have lost your perspective.

Just like there's a difference between pages and sites, there's a difference between grateful and ungrateful. Y'all are like the guest that never leaves, never cleans up, never buys food, etc. That's just not reasonable.

This strikes me as a pretty useless distinction. Github frequently refers them as "sites", i.e. websites, and advertises using them to host Jekyll-generated blogs.

This is why we can have nice things. People always push up against limits as long as they aren't shut down.

Words? Who needs them? Let's just say anything and/or assume we heard whatever we wanted to hear. What could go wrong? Right?

gh-pages.

The intent of GH's offer is to assist and support OS projects. Not let some wiseass freeloader treat GH like a proper hosting company. Clearly ppl are taking advantage of that, but GH is the bad guy/gal?

gh-pages.

Geez. Why did I bother? Words? They have no value.

Actually, 100,000 requests per month is a little less than a req per second. Which means that if you want to have all the services that GH is offering, I guess you would pay quite a lot (relatively speaking).
> a little less than a req per second

There are 86400 seconds in a day. At a little under a request per second, you're going to hit 100k some time around 3am on the second day, depending on what you take "a little under" to mean.

100 K Requests are really not much. The page itself, some css, some scripts, some images and you hit the 100 K with less visitors.
It's actually about two requests a minute.