Re:RawGit serves raw files directly from GitHub with proper ...
by InclinedPlane on Wednesday June 18, 2014 @05:20AM
(#7909156)
To prevent using them as a file host. If you can just dump files (of whatever size, it doesn't really matter) onto github and serve them natively across the web then they become a file share or a CDN. They'd have to seriously lock down the rules on publicly available free repos if that happened (and they'd have a copyright nightmare on their hand as well). Whereas if they force git into the loop on the client end then it keeps them in that repo hosting butter zone.
Re:RawGit serves raw files directly from GitHub with proper ...
by InclinedPlane on Wednesday June 18, 2014 @06:52PM
(#7913421)
It's too much work and there are better alternatives. Big files just won't work and wouldn't be superior to torrents. Small files would work but compared to imgur, flickr, youtube, pastebin, tumblr, blogger, etc. it's much more hassle to use github with no advantages.
Re:RawGit serves raw files directly from GitHub with proper ...
by dbbolton on Wednesday June 18, 2014 @03:19AM
(#7908888)
That is answered in the FAQ.
>They do this because serving raw files from a git repo is relatively inefficient, so they want to discourage people from using their GitHub repos for static file hosting.
Doing it through the github web interface takes a lot of clicks.
>They do this because serving raw files from a git repo is relatively inefficient, so they want to discourage people from using their GitHub repos for static file hosting.