DEV Community

Nicolas Hoizey
Nicolas Hoizey

Posted on • Originally published at

Medium is only an edge server of your POSSE CDN, your own blog is the origin

This article was originally seen on my own blog, obviously.

People tend to be lazy (I am often) and chose the easiest tool to do the job, even if it's not the best one. Medium is the new Blogger1, but with a much nicer content editing UI, and a cleaner presentation of content to readers2. People can create and account and start publish in a few minutes, it's really easy. But how can all this be free?

Medium can do anything with your content

Andrea Phillips already said it a few years ago in her post The Problem With Medium:

you’re giving your writing to a corporation for free, and they can do anything they want with it. Forever. Without paying you. Ever.

The Terms of Service have evolved since Andrea's post back in 2013, but are still to be carefully considered (emphasis mine):

By posting content to Medium, you give us a nonexclusive license to publish it on Medium Services, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it). In consideration for Medium granting you access to and use of the Services, you agree that Medium may enable advertising on the Services, including in connection with the display of your content or other information. We may also use your content to promote Medium, including its products and content. — Content rights & responsibilities section of current Medium Terms of Service

Of course, Medium is an obvious black sheep, but the same can be said about most other centralized and closed services.

Bad things can happen

Additionally, Medium is a service that can disappear like many others before, and your content might be lost. I will never accept to take such a risk for my content.

Also, there are sometimes issues with content moderation, like Peter O'Shaughnessy experienced a few days ago:

Disappearing content can happen on any platform, like it did on Twitter recently, but when you don't own the platform, you don't have any way to fix the issue, you can just wait for the platform owner to do it, if it pleases him.

POSSE is the best option

POSSE means Publish (on your) Own Site, Syndicate Elsewhere.

Like Webmentions, POSSE is a creation of IndieWeb, which gives this description:

POSSE lets your friends keep using whatever they use to read your stuff (e.g. silo aggregators like Facebook, Tumblr, Twitter, etc.).

It's a key part of why and how the IndieWeb movement is different from just "everyone blog on their own site", and also different from "everyone just install and run (YourFavoriteSocialSoftware)" etc. monoculture solutions.

You really own your content, on your own (cool) URLs, and it's up to you to make it last.

But you also syndicate it on other platform (most being centralized and closed) that might have greater reach. Ideally, copies of your content on these platforms should link to your canonical URLs. Even Medium allows it.

IndieWeb listed a few ways to POSSE to popular services and social networks.

This blog is already POSSEed on Twitter and Facebook thanks to the Atom feed, IFTTT and Buffer.

The Content Delivery Network

You can think of these other platforms as edge servers in a Content Delivery Network.

The goal is to "distribute service spatially relative to end-users to provide high availability and high performance". The edge server that will serve an HTML page or static resource to a user is often the closest one. These edge servers get the content to serve from the origin server, operated by the content owner. The end-user might never contact the origin directly, but the most important is that she gets the pages and associated resources.

Medium, Twitter, Facebook and others are edge services for your content, they are the platforms where you will find — unfortunately — more readers that on your own URL.

Your platform is the origin.

Let's make copies of our own content to Medium

You can manually import any post onto Medium, just like I did for my recent post about big emojis not rendered by Chrome. But there are very few formating options, it's really not made for such technical writings with code blocks.

There is also an API that allows you to POST you content to Medium. Jeremy Keith blogged about this, and shared his PHP code.

If like me you use Jekyll, Aaron Gustafson, author of the plugin I use for Webmentions has created another plugin for Crossposting to Medium From Jekyll, taking inspiration for Jeremy Keith's PHP code. I might try it soon.

But setting your own platform is not so easy

I know it is not easy for most people to create and host their own platform, like Nicolas told me on Twitter:

Remouk also added that the reach of our own platform is almost nonexistent, and that he has more comments on social shares than on the actual contents themselves:

I experience the same, that's why I'm really happy that Webmentions, and Bridgy allow me to get Twitter comments back to my posts.

So, yes, it's obvious not everyone who wants to publish content is able to build and host his own platform. Even tech-savvy people can have difficulties doing so.

Your "own" platform is the nearest you can (get help to) setup

If you can't do it right now, let's say hosting your own platform is your long term target.

You can start by choosing a better platform that Medium to create your content, the origin that will serve all edge platforms you want to have for their greater reach.

Such a platform can be Github with Github Pages, where your content will more be yours than on Medium. You can also use the hosted Or whatever where you will be confident enough you won't lose your content, and ownership of it.

But first, chose your own domain name, and use it for your canonical URLs. If you want later to change the platform, you can change where your domain points to, and your canonical URLs will be safe.

It's free on Github, and only costs 4€ a month on

It is one of the first items in the IndieMark set of metrics for "measuring the indieweb-ness of a site, and a step-by-step approach to incrementally adopting indieweb features on your site".

It is really worth it.

I'm not alone recommending this:

  1. Ev Williams, the CEO of Medium, is one of Twitter's co-founders, but was previously headding Blogger. 

  2. I must say I really don't like the way they deal with images through, with this ugly blur. 

Top comments (3)

ben profile image
Ben Halpern

I feel like we've independently came to a lot of the conclusions reached here. Without being really steeped in this specific philosophy, we've tried to make this concept happen.

I'd be curious to hear if you have any feedback on how we can best serve this ideology and make it clear that it's a first-class use case in these parts.

nhoizey profile image
Nicolas Hoizey

I'm really happy to read you came to the same conclusions!

I'm new to your platform, so it might be too soon to be able to give any feedback, but I already like that you let us add a canonical URL to our Front Matter, and provide a way to create post drafts from a feed.

I see you also provide a feed for my content, so people can use your platform as a source, and POSSE anywhere else.

To really be interesting for POSSE, through, you would have to provide users with the ability to use their own domain. It's the only way they can start publishing there, and be free to move elsewhere later, without losing all canonical URLs they would have put on other platforms.

Not specific to POSSE, I really like the fact you give us a Markdown editor instead of a shiny but very limited WYSIWYG editor. It gives us more features, similar to what we find everywhere in our projects nowadays. We can feel more at home here, thanks to this.

ben profile image
Ben Halpern

Great to hear the feedback.

Re: Domains, I've always thought of this as sort of an antipattern from a pure technical perspective, especially with things like serviceworkers which really scope to a domain, but always willing to continually have this conversation.

On that note, we will be open-sourcing our code and have the theoretical notion of a decentralized-but-compatible web of similar platforms. We don't have any designs to go too hard into this arena on day one, but it's an idea we're keeping around as a strong possibility.