A fork of glitch-soc.
 
 
 
 
 
 
Go to file
Thibaut Girka 6777dfc8d9 [Glitch] In keyword filter, account for reblogs, HTML and whole-words
Port 404c7702ec to glitch-soc
2018-07-10 14:06:04 +02:00
.circleci
.github
app [Glitch] In keyword filter, account for reblogs, HTML and whole-words 2018-07-10 14:06:04 +02:00
bin
config Migrate glitch-soc keyword mutes to Mastodon's 2018-07-09 19:19:23 +02:00
db Migrate glitch-soc keyword mutes to Mastodon's 2018-07-09 19:19:23 +02:00
docs
lib Merge branch 'master' into glitch-soc/tentative-merge 2018-07-09 07:13:59 +02:00
log
nanobox
public Merge branch 'master' into glitch-soc/tentative-merge 2018-07-09 07:13:59 +02:00
spec Migrate glitch-soc keyword mutes to Mastodon's 2018-07-09 19:19:23 +02:00
streaming
vendor/assets
.babelrc
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/tentative-merge 2018-07-09 07:13:59 +02:00
.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
.travis.yml Re-install test/dev dependencies before running tests 2018-07-09 19:19:23 +02:00
.yarnclean
AUTHORS.md
Aptfile
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Merge branch 'master' into glitch-soc/tentative-merge 2018-07-09 07:13:59 +02:00
Gemfile
Gemfile.lock
LICENSE
Procfile
Procfile.dev
README.md Remove reference to BTC, update video link 2018-07-05 21:02:21 +02:00
Rakefile
Vagrantfile
app.json
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?