The glaceon.social flavour of glitch-soc, a Mastodon fork
Go to file
David Yip 2f9bd86f6e
Merge pull request #470 from ThibG/glitch-soc/fixes/status-click-detailed
Widen clickable area of toots
2018-05-20 03:03:39 -05:00
.circleci
…
.github
…
app Merge pull request #470 from ThibG/glitch-soc/fixes/status-click-detailed 2018-05-20 03:03:39 -05:00
bin
…
config Merge branch 'master' into glitch-soc/merge-upstream 2018-05-19 22:41:10 +02:00
db Merge branch 'master' into glitch-soc/merge 2018-05-14 20:51:50 +02:00
docs
…
lib Merge branch 'master' into glitch-soc/merge-upstream 2018-05-19 22:41:10 +02:00
log
…
nanobox
…
public Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master 2018-04-11 00:50:09 +00:00
spec Merge branch 'master' into glitch-soc/merge-upstream 2018-05-19 22:41:10 +02:00
streaming
…
vendor/assets
…
.babelrc
…
.buildpacks
…
.codeclimate.yml
…
.dockerignore
…
.editorconfig
…
.env.nanobox
…
.env.production.sample
…
.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 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
…
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
…
Rakefile
…
Vagrantfile
…
app.json
…
boxfile.yml
…
config.ru
…
docker-compose.yml
…
jest.config.js
…
package.json
…
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?