This is documented in the Vagrantfile, but not in the README. As far as I know,
following the short guide without installing this plugin will not make the
container accessible at mastodon.local, thus breaking the last step of the
guide.

* Modify syntax

* Change ** bold to ### header

* Revert license edit

* Change references to tootsuite/mastodon to mastodon/mastodon

* Remove obsolete test fixture

* Replace occurrences of tootsuite/mastodon with mastodon/mastodon in CHANGELOG

And a few other places

Freenode was taken over by a different entity, and former Freenode
staff created LiberaChat.

Short summary of the situation: https://blog.bofh.it/debian/id_461

With more details:

* https://gist.github.com/joepie91/df80d8d36cd9d1bde46ba018af497409
* https://gist.github.com/aaronmdjones/1a9a93ded5b7d162c3f58bdd66b8f491

* Update Gemfile

* Update README.md

happy new year 🎉

* Update package.json

* Update README.md

The introductory paragraph has been edited to be more cohesive.

fix a spelling error

This is so incredibly small, but assuming this is a needed change. Might want to check year in other files.

* Improve README

* Update README.md

* Update README.md

* Update README.md

* Update README.md

Add link to quick start guide, link to general documentation, fix link to list of servers, remove Liberapay

* Add license info to README

* Reference AUTHORS file

Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

and change badge's URI to https

Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

* Remove docker guide and put it in docs repo

* Move tasks to docs repo

* Move requirements to contributing doc

* Move advice about tagged releases to docs repo

* Move local domain and host config to docs repo

* Link to related tech

In current order, docker-compose build results in
ERROR: Couldn't find env file: /a/hopt/mastodon/.env.production

Re-ordered the steps so it doesn't read "Do this, but first, do this
other step"
Added note about keeping the REDIS and DB settings as they are for
Docker use
Add which variables you will NEED to set to make the Mastodon work
Add how to generate the secrets
Add how to connect to your Mastodon
Add a note to read the Production-guide

Add a note to ensure users are using the right version of docker-compose.

This month I traveled to Cambridge, Massachusetts with my friends and attended LibrePlanet 2017. At the talk *Technology for direct actions*, Andrew Seeder pointed out that we often call free software an "alternative" to what exists. But an alternative is something that is mostly similar, and differentiated by preference rather than need. For instance, a trackball is an alternative to a mouse, but a jail is not an alternative to a bedroom. Andrew suggested that we start looking at free software as "solutions" rather than alternatives. So I propose boldly proclaiming that Mastodon is not an alternative to Twitter, but rather a solution to it.