A glitchy but lovable microblogging server
Go to file
David Yip 0aba716fe1
Merge pull request #471 from impiaaa/thread-icon
Add an extra icon to indicate that a status is part of a conversation
2018-06-01 00:35:13 -05:00
.circleci
.github
app Adjust spacing between status icons 2018-05-31 21:55:44 -07:00
bin
config Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
db
docs
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-05-23 16:05:19 +02:00
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
streaming Add media timeline (#6631) 2018-05-21 12:43:38 +02:00
vendor/assets
.babelrc
.buildpacks
.codeclimate.yml
.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
.env.vagrant
.eslintignore
.eslintrc.yml Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.postcssrc.yml
.profile
.rspec
.rubocop.yml
.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
app.json
Aptfile
AUTHORS.md
boxfile.yml
Capfile
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
docker-compose.yml Remove Puma pidfile before boot if container receives SIGTERM (#7052) 2018-05-25 18:50:31 +02:00
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
jest.config.js
LICENSE
package.json Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
stack-fix.c
Vagrantfile
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 2018-05-29 13:52:26 +02:00

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?