The glaceon.social flavour of glitch-soc, a Mastodon fork

Go to file

Thibaut Girka 57f31b361f Add an option restricting secondary toot privacy to that of the toot being replied to		2018-07-12 19:15:44 +02:00
.circleci	…
.github	…
app	…
bin	Add symbolic link for yarnpkg (#7894 )	2018-06-26 20:34:01 +02:00
config	Merge branch 'master' into glitch-soc/merge-upstream	2018-07-11 17:57:08 +02:00
db	…
docs	Fix redirect link on Tuning.md (#1595 )	2017-04-12 12:40:37 +02:00
lib	…
log	Initial commit	2016-02-20 22:53:20 +01:00
nanobox	[Nanobox] Tuning Update (#6660 )	2018-03-06 21:59:35 +01:00
public	…
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	…
.env.test	…
.env.vagrant	…
.eslintignore	Dev Tooling fixes (eslint/editorconfig) (#1398 )	2017-04-11 00:36:03 +02:00
.eslintrc.yml	…
.foreman	Replace sprockets/browserify with Webpack (#2617 )	2017-05-03 02:04:16 +02:00
.gitattributes	…
.gitignore	…
.gitmodules	…
.haml-lint.yml	…
.nanoignore	Remove Storybook (#4397 )	2017-07-27 22:30:27 +02:00
.nvmrc	…
.postcssrc.yml	…
.profile	…
.rspec	…
.rubocop.yml	…
.ruby-version	…
.scss-lint.yml	…
.slugignore	Remove Storybook (#4397 )	2017-07-27 22:30:27 +02:00
.travis.yml	…
.yarnclean	…
AUTHORS.md	…
Aptfile	…
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	Merge branch 'master' into glitch-soc/merge-upstream	2018-06-15 20:51:39 +02:00
Gemfile.lock	…
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
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	Merge remote-tracking branch 'tootsuite/master' into glitchsoc/master	2018-06-12 13:17:21 +00:00

README.md

Mastodon Glitch Edition

Now with automated deploys!

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?

You can view documentation for this project at glitch-soc.github.io/docs/.
And contributing guidelines are available here and here.