Mastodon Glitch Edition

Introduction

Welcome to the documentation site for glitch-soc! glitch-soc is a friendly fork of the open-source social media software Mastodon, with the aim of providing additional features at the risk of potentially less stable software. You can browse our source code and contribute to the project on Github.

What’s different?

glitch-soc adds a number of experimental features to Mastodon, such as:

Features that have made their way upstream

Some of the features originally implemented in glitch-soc have been adopted in Mastodon:

How to install and update glitch-soc?

glitch-soc is based on Mastodon’s master branch. The installation steps are thus the same as described in the Mastodon documentation.

Updating from Mastodon (or from an earlier glitch-soc version) is exactly like updating from one Mastodon version to another, and will in general require the following steps:

  1. Switch to glitch-soc, for instance by:
    • adding a new remote git remote add glitch-soc https://github.com/glitch-soc/mastodon
    • fetching it (git fetch glitch-soc)
    • switching to the master branch from that repo (git checkout glitch-soc/master)
  2. Fetch the source code (typically, git pull)
  3. Install dependencies: bundle install && yarn install
  4. Run the pre-deployment database migrations: RAILS_ENV=production SKIP_POST_DEPLOYMENT_MIGRATIONS=true bundle exec rails db:migrate
  5. Pre-compile static assets: RAILS_ENV=production bundle exec rails assets:precompile

    Due to glitch-soc shipping with two front-end flavours, this step requires more resources than it does on mainline Mastodon.

  6. Restart the services: systemctl reload mastodon-web && systemctl restart mastodon-{sidekiq,streaming}
  7. Clean Rails’ cache: RAILS_ENV=production bin/tootctl cache clear
  8. Run the post-deployment database migrations: RAILS_ENV=production bundle exec rails db:migrate

How to migrate back to upstream Mastodon?

Should you wish to migrate back to upstream Mastodon for any reason, this is possible, at the cost of every glitch-specific feature, of course. There are a few things that you need to be aware of:

How can I help?

You can get information on contributing here.

Disclaimer

glitch-soc is beta software, and under active development. Use at your own risk!

Who is running glitch-soc?

glitch-soc is currently in use on the following instances:

  (Instance not on the list? Let us know!)

  (The contents, availability, or behavior of the listed instances are not actively monitored. If you think any of this instances goes against our Code of Conduct, you are encouraged to report it to the project team)