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 115b1abb6e Rename hide_followers_count helper to hide_followers_count? 6 years ago
.circleci Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
.github
app Rename hide_followers_count helper to hide_followers_count? 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
lib Override current_user when generating static pages 6 years ago
log
nanobox Update Nginx config for Nanobox apps (#9310) 6 years ago
public Replace animated oops.gif by a non-animated image 6 years ago
spec Change instance_presenter_spec to point to glitch-soc instead of tootsuite 6 years ago
streaming Only stream local-only toots to logged-in users 6 years ago
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 Update AUTHORS.md (#9141) 6 years ago
Aptfile
CHANGELOG.md Bump version to 2.6.5 (#9413) 6 years ago
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
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
boxfile.yml
config.ru
docker-compose.yml
jest.config.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 6 years ago
priv-config
scalingo.json
stack-fix.c
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?