I'm concerned with the move that FreeCodeCamp just pulled by leaving Medium
Tags: meta, news, freecodecamp, writing
Published: 2019-05-28 18:41:28

FreeCodeCamp is a great organization and I presume the best intentions of everyone involved.  That said,  I am puzzled and concerned by their move off of Medium which was [announced yesterday](https://www.freecodecamp.org/forum/t/we-just-moved-off-of-medium-and-onto-freecodecamp-news-heres-how-you-can-use-it/279929).

## What they did

FreeCodeCamp announced that they moved off of Medium, for a lot of the right reasons:

> We now have our own open source publishing platform where you can write about anything you want the developer community to know about.
Your audience will be bigger than ever.
No more popups or sign-in prompts. Readers can enjoy your articles without any fuss.
The transition has been a long one, and we’re still fixing quite a few bugs.

I have expressed concern over Medium's business model, product and misaligned incentives in the past. That is a big part of [dev.to](/)'s existence. But that is a different story.

My bigger concerns right now are that FreeCodeCamp seems to have pulled this off in a way that likely violates the terms of their agreement, explicit or implicit, with Medium and all of the authors of their publication.

## What I can tell

All articles once posted to FreeCodeCamp's Medium publication now redirect to articles that look like this:

![example of FreeCodeCamp article title](https://cl.ly/6a840d5900ab/Image%202019-05-28%20at%202.23.25%20PM.png)

Clicking _Visit author's page_ goes nowhere.

I know for a fact that the author of that post did not consent to having their content moved off of Medium (where they can accrue followers, distribution, and generally partake in their initial agreement with Medium).

In fact, that article was originally posted on [dev.to](/) and then cross-posted to Medium and published to the FreeCodeCamp.

On [dev.to](/):

{% link https://dev.to/aspittel/the-most-important-non-programming-skills-for-programmers-iii %}

On [Medium](https://medium.com)

{% medium https://medium.com/free-code-camp/the-most-important-non-programming-skills-for-programmers-d39fadc1a0fa %}

This author actually took the time to set the canonical URL on Medium to the original post on [dev.to](/), which was not upheld with the migration by FreeCodeCamp.

### [Medium Source Code](https://medium.com/free-code-camp/the-most-important-non-programming-skills-for-programmers-d39fadc1a0fa):

![Medium source code](https://cl.ly/5889f8e4f072/Image%202019-05-28%20at%202.27.10%20PM.png)

### [FreeCodeCamp Source Code](https://www.freecodecamp.org/news/the-most-important-non-programming-skills-for-programmers-d39fadc1a0fa/?source=---------4------------------):

![FreeCodeCamp Source](https://cl.ly/8f3078e790ae/Image%202019-05-28%20at%202.27.44%20PM.png)

As the founders of a service that provides a shared distribution relationship with our authors, we take these things very seriously. This is what our [faq](/faq) says on the subject, to complement the [terms of use](https://dev.to/terms):

> Yes, you own the rights to the content you create and post on dev.to and you have the full authority to post, edit, and remove your content as you see fit.

Medium's [terms](https://medium.com/policy/medium-terms-of-service-9db0094a1e0f) tell a similar tale:

> You own the rights to the content you create and post on Medium

I want to be told that I'm missing something. [Hackernoon](https://hackernoon.com/) is currently involved in a long and drawn out exodus from Medium which seems to be taking all of these issues into account.  In fact, here's what Medium said in regards to the HackerNoon issue:

> Publications on Medium are bound by the Medium Terms of Service, and they have no right to your content that you do not explicitly grant them.  That includes exporting, copying, or reposting your content to any website that is not Medium.com

FreeCodeCamp seems to have just pulled the plug and taken everyone's Medium content with them, to be displayed in a different context, wiping out the canonical URLS, while depriving the authors their ability to edit, delete, or manage in any way.

Please let me know in the comments if I really am missing something.