You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Thibaut Girka 3ea5c045d7 Use a checkbox for the “Mark media as sensitive” composer button 6 years ago
.circleci
.github
app Use a checkbox for the “Mark media as sensitive” composer button 6 years ago
bin
config Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
db Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
dist Cache error 410 responses in recommended nginx configuration (#10425) 6 years ago
lib Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
log
nanobox
public Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
spec Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml Add `tootctl self-destruct` (#10367) 6 years ago
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
AUTHORS.md Bump version to 2.8.0rc1 (#10340) 6 years ago
Aptfile
CHANGELOG.md Bump version to 2.8.2 (#10703) 6 years ago
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
babel.config.js Weblate translations (2019-04-10) (#10545) 6 years ago
boxfile.yml
config.ru
docker-compose.yml Fixed Healthchecks in docker-compose.yml (#10553) 6 years ago
package.json Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
postcss.config.js
priv-config
scalingo.json
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 6 years ago

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?