Your self-hosted, globally interconnected microblogging community. https://joinmastodon.org/
 
 
 
 
 
Go to file
Thibaut Girka 00fcdebed7 Merge branch 'master' into glitch-soc/merge-upstream
Conflicts:
	db/migrate/20170716191202_add_hide_notifications_to_mute.rb
	spec/controllers/application_controller_spec.rb

Took our version, upstream changes were only minor style linting.
2018-10-05 15:23:57 +02:00
.circleci
.github
app Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
db Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
streaming
vendor/assets
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.yml
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-10-05 15:23:57 +02:00
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
docker-compose.yml
jest.config.js
package.json
priv-config
scalingo.json
stack-fix.c
yarn.lock

README.md

Mastodon Glitch Edition

Now with automated deploys!

Build Status

So here's the deal: we all work on this code, and then it runs on dev.glitch.social and anyone who uses that does so absolutely at their own risk. can you dig it?