The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
ThibG d680c61993 [Glitch] Do not empty timeline of blocked users on block
Port 94aceb85ad to glitch-soc
2019-03-26 16:07:47 +01:00
.circleci
.github
app [Glitch] Do not empty timeline of blocked users on block 2019-03-26 16:07:47 +01:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2019-03-26 16:02:54 +01:00
db
dist
lib
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2019-03-26 16:01:59 +01:00
streaming
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc Upgrade Node.js to v8.x on nvmrc (#8023) 2018-07-15 12:29:17 +09:00
.profile
.rspec
.rubocop.yml
.ruby-version
.scss-lint.yml
.slugignore
.yarnclean
AUTHORS.md
Aptfile
CHANGELOG.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 2019-03-26 16:02:54 +01:00
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 2019-03-26 16:02:54 +01:00
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
docker-compose.yml
package.json
postcss.config.js
priv-config
scalingo.json
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?