I wonder if people start abusing this if Github were to put any restrictions on it somehow. For quick one off single page things sure why not, but if people start trying to host huge websites on Github? I'd be curious as to their response.
Yeah, this is ripe for abuse by pornographers. :(
How to host and manage static sites (of unlimited size) for free on Github
21–30 of 35 posts
Re: How to host and manage static sites (of unlimited size) for free on Github
#22Be careful though, if you push something on gh-pages it will be public, even if your repo is private.
From what the guys at Github told me, they don't have to restrict their users as long as you don't commit obvious abuses. Either very large files or gigantic amount of files, which will both create issues with Git. In short, "don't be a dick".
Re: How to host and manage static sites (of unlimited size) for free on Github
#23Earlier quoted context omitted.
You know what? Me too. I miss Geocities and I never realized until just now. That was a great internet. The people's internet. I was 13 years old but I was allowed to make a website for free, with no help or direction from parents or teachers or anyone, with barely anything to learn. And when I was done it was there. It was a thing I made on the internet and I could show anyone. And I did, and it was probably embarra…
I wish I could upvote this comment more than once. I remember getting on Geocities in 1996 and finding a burgeoning community, full of randomness and fun, all learning as we went along about how build websites. I remember mine was in the “Bourbon Street” “neighbourhood”. I had a lot of fun that year, messing about on IRC, learning HTML, building (ugly :-) websites, helping others do the same. Can't believe I sound no…
My father always used to say "Leave the computer alone and do your homework. No one will pay you for 'playing' on the computer".
5 years later he was my first paying client. Nowadays people only pay me when I "play with my computer".
Re: How to host and manage static sites (of unlimited size) for free on Github
#24Re: How to host and manage static sites (of unlimited size) for free on Github
#25I miss Geocities
I miss when people I know used LiveJournal. LJ encouraged people to write, long form. Then came MySpace and the birth of the status update, which was on even ground with the blog feature. Then Facebook banished blogging to the "Notes" area that nobody ever read, while elevating the status update to the central communication channel. Then, of course, Twitter boiled it down to nothing but status updates.
I miss when more average Internet users made home pages. I miss when more of them blogged, and participated in communities that revolved around the blog format rather than status updates.
Re: How to host and manage static sites (of unlimited size) for free on Github
#26I miss Geocities
Something has been lost in the evolution from home pages to Facebook and Twitter. The creation part of the equation has been reduced down to nothing more than choosing a picture to stick in a predefined slot. I miss when people I know used LiveJournal. LJ encouraged people to write , long form. Then came MySpace and the birth of the status update, which was on even ground with the blog feature. Then Facebook banished…
> Then, of course, Twitter boiled it down to nothing
> but status updates.
IIRC, Facebook copied the 'status updates / news feed' idea from Twitter.Re: How to host and manage static sites (of unlimited size) for free on Github
#27...if you give something for free and don't set limits, people will find ways to abuse it ...and then you'll have limits for everyone ... I ask all web developers out there to not use Github pages for clients' websites , it's not like you don't have room in the budget for almost-free webhosting for static websites, it's probably something like 0.(...)1% of website maintenance and dev costs and there already are free…
They just don't care because you end up doing something that takes you 5 minutes and little to no energy which would be next to impossible for them.
Since the margins are so high, you also have freedom to make nice discounts without a loss.
Re: How to host and manage static sites (of unlimited size) for free on Github
#28The license part of the README.md says "The content in this repo is BSD licensed".
AFAIK licensing requires:
- A copyright line with the year (or years) and the name of the copyright holder.
- IIRC a way to contact the copyright holder is required (email, URL, etc), but I may be wrong and it's just optional.
- A copy of the license grant/notice is required, ie. the "boilerplate notice" form Apache license that includes a link to the full license text.
In this case, does the "The content in this repo is BSD licensed" sentence have any kind of effect?
EDIT: ate a word, formatting
Re: How to host and manage static sites (of unlimited size) for free on Github
#29Earlier quoted context omitted.
Yeah, this is ripe for abuse by pornographers. :(
Really? Care to expand? That just surprises me!
Unrelated to porn this sort of thing could be great in general as all the content is searchable it would be a goldmine for information on how to use a function or do some specific action. I already use git as a codex of sorts!
Re: How to host and manage static sites (of unlimited size) for free on Github
#30OT, but I'd love to know what HN think about this: The license part of the README.md says "The content in this repo is BSD licensed". AFAIK licensing requires: - A copyright line with the year (or years) and the name of the copyright holder. - IIRC a way to contact the copyright holder is required (email, URL, etc), but I may be wrong and it's just optional. - A copy of the license grant/notice is required, ie. the "…
Generally a author has copyright over their works without having to explicitly says so. Saying "Copyright (c) YYYY AUTHOR NAME" is just a way of asserting it to remove potential confusion or ambiguity.
With no licensing, there is no right to use a copyright work (except fair use). BSD licensing a work is granting permission is a set of circumstances, not revoking permission. Thus if a license is not correctly applied the work cannot be used, rather than the inverse.
As for "The content in this repo is BSD licensed" - the usual licensing wording is again a convention designed to be as clear as possible, but the wording applied there probably counts as it pretty clearly intends to give permission. The "probably" is why people ought to stick to known and understood conventions.