Re:Medium is a poor choice for blogging
by _emacsomancer_ on Tuesday November 13, 2018 @02:26PM
(#18444011)
Gitlab has a similar feature. (I haven't used either Github or Gitlab directly to publish a blog, but they're also usefully integrated in the Netlify/Hugo blog workflow.)
I'm curious as to why you say it's 'critical' to have your own domain on Github pages? Is it to do with search engine listings?
Re:Medium is a poor choice for blogging
by braythwayt on Tuesday November 13, 2018 @09:38AM
(#18441224)
Joel Spolsky (if you don’t know him, he was one of the first “Celebrity Bloggers” in tech culture) gave me a piece of advice more than a decade ago: Own your own domain and publish under it, that way you always control your content and the links to your content.
If my blog was raganwald.githubpages.com, GitHub could theoretically decide that githubpages needed to be deeply integrated with Windows or some other foolishness, and I’d be screwed.
But since my blog appears to the world as raganwald.com, I can leave GitHub Pages whenever I like, and all the links will continue to work. It's about long-term control, and for that you need:
1. Control your content, ideally with a copy of the source on your own devices at all time, in an open format with an ecosystem of tooling, and;
2. Control your domain name.
If they ever shutter the service, it is very easy to generate all the HTML pages with Jekyll, and then throw them up on a static host.
Every single one of Medium’s discoverability and traffic benefits feel like Faustian bargains to me, so I am not going there.
The last time I experimented with publishing in a walled garden was Posterous, mostly because they were a YCombinator startup at a time when that wasn’t some kind of golden ticket, and I wanted to make a gesture of support for them and for YCombinator.
Posterous shuttered, and I republished my work using GitHub Pages, but all the old urls broke, and I’m never doing that again.