The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
David Yip 908a770d2b
keyword mute: use mentions scope in home feed filtering (#454)
If a status shows up in mentions because all keyword mutes that might
apply to it are marked as "don't apply to mentions", then it ought to
show up in the home feed also.
2018-06-12 17:14:35 -05:00
.circleci Add CONTINUOUS_INTEGRATION: true to .circleci/config.yml (#7447) 2018-05-11 11:51:07 +02:00
.github Multiple Issue templates (#7402) 2018-05-08 13:35:33 +02:00
app keyword mute: use mentions scope in home feed filtering (#454) 2018-06-12 17:14:35 -05:00
bin Port travis_retry for CI (#7379) 2018-05-06 10:55:50 +02:00
config Merge remote-tracking branch 'glitchsoc/master' into 454-allow-keyword-mutes-to-skip-mentions 2018-06-12 16:39:30 -05:00
db Thread scopes through #matches?. #454. 2018-06-03 23:00:50 -05:00
docs
…
lib Merge remote-tracking branch 'tootsuite/master' into merge-upstream 2018-06-07 05:13:49 -05:00
log
…
nanobox
…
public
…
spec keyword mute: use mentions scope in home feed filtering (#454) 2018-06-12 17:14:35 -05:00
streaming Add media timeline (#6631) 2018-05-21 12:43:38 +02:00
vendor/assets
…
.babelrc
…
.buildpacks
…
.codeclimate.yml fix RuboCop error (#7442) 2018-06-04 14:49:10 +02:00
.dockerignore
…
.editorconfig
…
.env.nanobox
…
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
.env.test Add parallel test processors (#7215) 2018-04-21 21:36:22 +02:00
.env.vagrant
…
.eslintignore
…
.eslintrc.yml Merge remote-tracking branch 'origin/master' into gs-master 2018-06-02 16:15:36 -05:00
.foreman
…
.gitattributes
…
.gitignore
…
.gitmodules
…
.haml-lint.yml
…
.nanoignore
…
.nvmrc
…
.postcssrc.yml
…
.profile
…
.rspec
…
.rubocop.yml fix RuboCop error (#7442) 2018-06-04 14:49:10 +02:00
.ruby-version
…
.scss-lint.yml
…
.slugignore
…
.travis.yml ci: Hack around a Travis condition, I guess 2018-05-18 09:51:00 -05:00
.yarnclean
…
AUTHORS.md
…
Aptfile
…
CODE_OF_CONDUCT.md
…
CONTRIBUTING.md Merge remote-tracking branch 'origin/master' into gs-master 2018-05-04 12:16:12 -05:00
Capfile
…
Dockerfile
…
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2018-05-19 22:41:10 +02:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-05-19 22:41:10 +02:00
LICENSE
…
Procfile
…
Procfile.dev
…
README.md Replace badge to CircleCI (#7216) 2018-04-21 21:56:40 +02:00
Rakefile
…
Vagrantfile
…
app.json
…
boxfile.yml
…
config.ru
…
docker-compose.yml Remove Puma pidfile before boot if container receives SIGTERM (#7052) 2018-05-25 18:50:31 +02:00
jest.config.js
…
package.json Merge remote-tracking branch 'origin/master' into gs-master 2018-06-02 16:15:36 -05:00
scalingo.json
…
stack-fix.c
…
yarn.lock Merge remote-tracking branch 'origin/master' into gs-master 2018-06-02 16:15:36 -05:00

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?