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.
 
 
 
 
 
 
David Yip 908a770d2b
keyword mute: use mentions scope in home feed filtering (#454)
7 years ago
.circleci
.github
app keyword mute: use mentions scope in home feed filtering (#454) 7 years ago
bin
config Merge remote-tracking branch 'glitchsoc/master' into 454-allow-keyword-mutes-to-skip-mentions 7 years ago
db Thread scopes through #matches?. #454. 7 years ago
docs
lib Merge remote-tracking branch 'tootsuite/master' into merge-upstream 7 years ago
log
nanobox
public
spec keyword mute: use mentions scope in home feed filtering (#454) 7 years ago
streaming Add media timeline (#6631) 7 years ago
vendor/assets
.babelrc
.buildpacks
.codeclimate.yml fix RuboCop error (#7442) 7 years ago
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 7 years ago
.env.test
.env.vagrant
.eslintignore
.eslintrc.yml Merge remote-tracking branch 'origin/master' into gs-master 7 years ago
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml fix RuboCop error (#7442) 7 years ago
.ruby-version
.scss-lint.yml
.slugignore
.travis.yml ci: Hack around a Travis condition, I guess 7 years ago
.yarnclean
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 7 years ago
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 7 years ago
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
boxfile.yml
config.ru
docker-compose.yml Remove Puma pidfile before boot if container receives SIGTERM (#7052) 7 years ago
jest.config.js
package.json Merge remote-tracking branch 'origin/master' into gs-master 7 years ago
scalingo.json
stack-fix.c
yarn.lock Merge remote-tracking branch 'origin/master' into gs-master 7 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?