OpenCloud
/
mastodon
mirror of https://github.com/tootsuite/mastodon
1
1
Fork 0
Code Issues Releases Wiki Activity

Updated FAQ (markdown)

master
Eugen 2017-01-03 00:27:31 +01:00
parent 20296aad8b
commit aa1d103c56
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
FAQ.md

@ -40,14 +40,4 @@ Because Mastodon has been created from a blank slate, it is much simpler to have
Development of Mastodon and hosting of mastodon.social is funded through my [Patreon (also BTC/PayPal donations)](https://www.patreon.com/user?u=619786). Beyond that, I am not interested in VC funding, monetizing, advertising, or anything of that sort. I could offer setup/maintenance services on demand.
The software is free and open source and communities should host their own servers if they can, that way the costs are more or less distributed. Obviously it'd be hard for me to pay the bills if literally everyone decided to use the mastodon.social instance only.
#### What about private accounts?
Features to limit interactions with strangers are planned (e.g. ignore notifications from people who aren't following you, or who you don't follow). But hiding content from the public is not currently planned, it's a bit of a protocol issue rather than software issue, it's not impossible but it'd have to be further down the road and with coordination from other OStatus-based projects like GNU social and postActiv.
#### How do blocks work?
Blocks prevent the blocked person from contacting you, i.e. their mentions, favourites, reblogs or any other interaction with you is hidden. You will not see replies to a blocked person, even if the reply mentions you. You will not see reblogs of posts by the blocked person. You will not see passing mentions of a blocked person except in the public timelines.
The blocked person does not get notified of your block. Their subscription to your feed is not revoked, feed is not hidden. Until private accounts exist, there's no point to it, here is why: Blocks do not federate. Even if they did, nothing stops a rouge person from coding an instance that ignores them. Enforcing blocks through hiding posts, *but only locally* would make federation less favorable and the mantra of this project is "local and remote users are treated equally in all features". Besides, notifying a blocked person of the block while still leaving vectors open will just lead to those vectors being used to gain access again. In my experience, shadowbanning is one of the more effective tools of moderation.
The software is free and open source and communities should host their own servers if they can, that way the costs are more or less distributed. Obviously it'd be hard for me to pay the bills if literally everyone decided to use the mastodon.social instance only.