Your self-hosted, globally interconnected microblogging community

docker activitypub fediverse social-network activity-stream mastodon microblog social-web webfinger

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

Thibaut Girka 4a70792b4a Merge branch 'master' into glitch-soc/merge-upstream Conflicts: - `Gemfile.lock`: Not a real conflict, just a glitch-soc-only dependency too close to a dependency that got updated upstream. Updated as well. - `app/models/status.rb`: Not a real conflict, just a change too close to glitch-soc-changed code for optionally showing boosts in public timelines. Applied upstream changes. - `app/views/layouts/application.html.haml`: Upstream a new, static CSS file, conflict due to glitch-soc's theming system, include the file regardless of the theme. - `config/initializers/content_security_policy.rb`: Upstream dropped 'unsafe-inline' from the 'style-src' directive, but both files are very different. Removed 'unsafe-inline' as well.		5 years ago
.circleci	…
.dependabot	…
.github	…
app	…
bin	…
config	…
db	…
dist	…
lib	…
log	…
nanobox	…
public	…
spec	…
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	…
.profile	…
.rspec	…
.rubocop.yml	…
.ruby-version	…
.sass-lint.yml	…
.slugignore	…
.yarnclean	…
AUTHORS.md	…
Aptfile	…
CHANGELOG.md	…
CODE_OF_CONDUCT.md	…
CONTRIBUTING.md	…
Capfile	…
Dockerfile	…
Gemfile	…
Gemfile.lock	…
LICENSE	…
Procfile	…
Procfile.dev	…
README.md	…
Rakefile	…
Vagrantfile	…
app.json	…
babel.config.js	…
boxfile.yml	…
config.ru	…
crowdin.yml	…
docker-compose.yml	…
ide-helper.js	…
package.json	…
postcss.config.js	…
priv-config	…
scalingo.json	…
yarn.lock	…

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.