You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Sasha Sorokin 66c0953c33 [Glitch] Improve safety of Blurhash component 4 years ago
.circleci
.github Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
app [Glitch] Improve safety of Blurhash component 4 years ago
bin
chart helm: bump chart and default image version to 3.1.5 (#14256) 4 years ago
config Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
db Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
dist
lib Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
log
nanobox
public
spec Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
streaming Fix streaming server only working for streams allowing local-only toots 4 years ago
vendor
.buildpacks
.codeclimate.yml
.dockerignore
.editorconfig
.env.nanobox
.env.production.sample Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
.env.test
.env.vagrant
.eslintignore
.eslintrc.js
.foreman
.gitattributes
.gitignore Change Redis#exists calls to Redis#exists? to avoid deprecation warning (#14191) 4 years ago
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.profile
.rspec
.rubocop.yml
.ruby-version
.sass-lint.yml
.slugignore
.yarnclean
AUTHORS.md
Aptfile
CHANGELOG.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Capfile
Dockerfile Update Dockerfile (#13582) 4 years ago
Gemfile Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
Gemfile.lock Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
LICENSE
Procfile
Procfile.dev
README.md
Rakefile
SECURITY.md
Vagrantfile
app.json
babel.config.js
boxfile.yml
config.ru
crowdin.yml
docker-compose.yml
ide-helper.js
package.json Merge branch 'master' into glitch-soc/merge-upstream 4 years ago
postcss.config.js
priv-config
scalingo.json
yarn.lock Merge branch 'master' into glitch-soc/merge-upstream 4 years ago

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?