31–40 of 396 posts
In any case, it is stupid to give one platform all the power (see YouTube). Internet should be decentralized.
Best alternative are static generators like Jekyll or static CMS like Publii https://getpublii.com
Obviously a bit more involved than your examples.
It's 2018, and there are a gazillion ways to get yourself in control of your stuff. The next free framework that comes, which promises a clean, non-distracting view, will also (most probably) eventually add advertisements, because, well, corporations need money.
In my humble opinion, just write your Markdown files, and use one of the bajillion Static Sites Generators to create/host them, or fork a framework that already does this such as [1], copy-paste them in, and you're set.
This article seems to miss the point of medium entirely. He fails to mention that you can be paid for content you create on medium, and content consumers don't have to sell their eyes to advertisers. Yes, they have to be pushy so they can acquire that critical base of paid users, but I'll take that any day over traditional advertisers. Now, if you aren't interested in being paid for the content you create, then mediu…
For me, "the point of medium" is entirely different. I don't blog regularly... I hardly ever write anything. When I do, medium offers me a large audience. I don't feel pressured to write periodic posts in order to maintain my audience. I just write something when I feel like it. No self-hosting solution can give you that.
Best alternative are static generators like Jekyll or static CMS like Publii https://getpublii.com
Disabling JavaScript and cookies for medium.com domain, and a bunch of uBlock rules [1] should do the job [1] Here's mine: medium.com##.metabar medium.com##.js-stickyFooter medium.com##.js-postAttributionFooterContainer medium.com##.js-postActionsFooter .buttonSet medium.com##.button--follow
So why the hell did you use it to write this article, then? I wrote a tool which converts your Medium blog into a Jekyll blog, for publishers hoping to migrate: https://git.sr.ht/~sircmpwn/unmediumify
So why the hell did you use it to write this article, then? I wrote a tool which converts your Medium blog into a Jekyll blog, for publishers hoping to migrate: https://git.sr.ht/~sircmpwn/unmediumify
thatsthejoke.jpg
But seriously, my guess is that the author wants you to see the things that he's talking about on the page. Like you read that the banner sucks and you can look up and see the banner and understand immediately what he's talking about without having to take his word or trust that supplied images aren't photoshopped to hell.
Best alternative are static generators like Jekyll or static CMS like Publii https://getpublii.com
Isn’t the main draw of medium the discussion? Static sites by their nature aren’t built for discussion considering the lack of a real database. Of course you could add a third party commenting system like discus, but then you relying on a third party service for comments and all the privacy and support concerns that come from that.
Best alternative are static generators like Jekyll or static CMS like Publii https://getpublii.com
Isn’t the main draw of medium the discussion? Static sites by their nature aren’t built for discussion considering the lack of a real database. Of course you could add a third party commenting system like discus, but then you relying on a third party service for comments and all the privacy and support concerns that come from that.