OpenCloud
/
mastodon
mirror of https://github.com/tootsuite/mastodon
1
1
Fork 0
Code Issues Releases Wiki Activity
Your self-hosted, globally interconnected microblogging community. https://joinmastodon.org/
7,702 Commits
137 Branches
269 Tags
1,018 MiB
Ruby 56.5%
JavaScript 28.3%
CSS 8.5%
HTML 6.5%
Dockerfile 0.1%
 
 
 
 
 
Go to file
Thibaut Girka e4c3ea1809 Force sensitive content flag when posting a toot with a CW 
Indeed, when the “Always enable the Content Warning field” setting is enabled,
sending a content-less toot with a CW would move the CW to the toot's content
and leave the toot not marked as sensitive.
 		2018-10-20 17:06:21 +02:00
.circleci
…
.github
…
app Force sensitive content flag when posting a toot with a CW 2018-10-20 17:06:21 +02:00
bin
…
config Fix deleting individual notifications from glitch-soc's web interface 2018-10-15 22:36:55 +02:00
db
…
dist
…
lib
…
log
…
nanobox
…
public
…
spec
…
streaming
…
vendor/assets
…
.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
…
.yarnclean
…
AUTHORS.md
…
Aptfile
…
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
…
docker-compose.yml
…
jest.config.js
…
package.json
…
priv-config
…
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?