summaryrefslogtreecommitdiff
path: root/docs/user_guide
diff options
context:
space:
mode:
authorLibravatar tobi <31960611+tsmethurst@users.noreply.github.com>2024-07-17 16:46:52 +0200
committerLibravatar GitHub <noreply@github.com>2024-07-17 16:46:52 +0200
commit0aadc2db2a42fc99538fbbb096b84b209b9ccd68 (patch)
tree38c58d163004d43da80d33477a6e9f22547bdb15 /docs/user_guide
parentgive read-only access to /dev for ffmpeg to access /dev/urandom (#3109) (diff)
downloadgotosocial-0aadc2db2a42fc99538fbbb096b84b209b9ccd68.tar.xz
[feature] Allow users to set default interaction policies per status visibility (#3108)
* [feature] Allow users to set default interaction policies * use vars for default policies * avoid some code repetition * unfuck form binding * avoid bonkers loop * beep boop * put policyValsToAPIPolicyVals in separate function * don't bother with slices.Grow * oops
Diffstat (limited to 'docs/user_guide')
-rw-r--r--docs/user_guide/posts.md29
-rw-r--r--docs/user_guide/settings.md50
2 files changed, 39 insertions, 40 deletions
diff --git a/docs/user_guide/posts.md b/docs/user_guide/posts.md
index fb46bb20e..6e2f57e6f 100644
--- a/docs/user_guide/posts.md
+++ b/docs/user_guide/posts.md
@@ -75,35 +75,6 @@ Public posts can be liked/faved, and they can be boosted.
**Public posts are accessible via a web URL on your GoToSocial instance!**
-## Extra Flags
-
-GoToSocial offers four extra flags on posts, which can be used to tweak how your post can be interacted with by others. These are:
-
-* `federated`
-* `boostable`
-* `replyable`
-* `likeable`
-
-By default, all these flags are set to `true`.
-
-Please note that while GoToSocial strictly respects these settings, other fediverse server implementations might not be aware of them. A consequence of this is that users on non-GoToSocial servers might think they are replying/boosting/liking your post, and their instance might behave as though that behavior was allowed, but those interactions will be denied by your GoToSocial server and you won't see them.
-
-### Federated
-
-When set to `false`, this post will not be federated out to other fediverse servers, and will be viewable only to accounts on your GoToSocial instance. This is sometimes called 'local-only' posting.
-
-### Boostable
-
-When set to `false`, your post will not be boostable, even if it is unlisted or public. GoToSocial enforces this by refusing dereferencing requests from remote servers in the event that someone tries to boost the post.
-
-### Replyable
-
-When set to `false`, replies to your post will not be accepted by your GoToSocial server, and will not appear in your timeline or create notifications. GoToSocial enforces this by giving an error message to attempted replies to the post from federated servers.
-
-### Likeable
-
-When set to `false`, likes/faves of your post will not be accepted by your GoToSocial server, and will not create notifications. GoToSocial enforces this by giving an error message to attempted likes/faves on the post from federated servers.
-
## Input Types
GoToSocial currently accepts two different types of input for posts (and user bio). The [user settings page](./settings.md) allows you to select between them. These are:
diff --git a/docs/user_guide/settings.md b/docs/user_guide/settings.md
index 1b243f166..9cef48eff 100644
--- a/docs/user_guide/settings.md
+++ b/docs/user_guide/settings.md
@@ -133,11 +133,7 @@ See the [Custom CSS](./custom_css.md) page for some tips on writing custom CSS f
!!! tip
Any custom CSS you add in this box will be applied *after* your selected theme, so you can pick a preset theme that you like and then make your own tweaks!
-## Settings
-
-![Screenshot of the settings section](../assets/user-settings-settings.png)
-
-In the 'Settings' section, you can set various defaults for new posts, and change your password / email address.
+## Posts
### Post Settings
@@ -151,16 +147,39 @@ The plain (default) setting provides standard post formatting, similar to what m
The markdown setting indicates that your posts should be parsed as Markdown, which is a markup language that gives you more options for customizing the layout and appearance of your posts. For more information on the differences between plain and markdown post formats, see the [posts page](posts.md).
-When you are finished updating your post settings, remember to click the `Save post settings` button at the bottom of the section to save your changes.
+When you are finished updating your post settings, remember to click the `Save settings` button at the bottom of the section to save your changes.
-### Password Change
+### Default Interaction Policies
-You can use the Password Change section of the panel to set a new password for your account. For security reasons, you must provide your current password to validate the change.
+Using this section, you can set your default interaction policies for new posts per visibility level. This allows you to fine-tune how others are allowed to interact with your posts.
-!!! info
- If your instance is using OIDC as its authorization/identity provider, you will not be able to change your password via the GoToSocial settings panel, and you should contact your OIDC provider instead.
+This allows you to do things like:
-For more information on the way GoToSocial manages passwords, please see the [Password management document](./password_management.md).
+- Create posts that nobody can interact with except you.
+- Create posts that only your followers / people you follow can interact with.
+- Create posts that anyone can like or boost, but only certain people can reply to.
+- Etc.
+
+For example, the below image shows a policy for Public visibility posts that allows anyone to like or boost, but only allows followers, and people you follow, to reply.
+
+![Policy showing "Who can like" = "anyone", "Who can reply" = "followers" and "following", and "Who can boost" = "anyone".](../assets/user-settings-interaction-policy-1.png)
+
+Bear in mind that policies do not apply retroactively. Posts created after you've applied a default interaction policy will use that policy, but any post created before then will use whatever policy was the default when the post was created.
+
+No matter what policy you set on a post, visibility settings and blocks will still be taken into account *before* any policies apply. For example, if you set "anyone" for a type of interaction, that will still exclude accounts you have blocked, or accounts on domains that are blocked by your instance. "Anyone", in this case, essentially means "anyone who could normally see the post".
+
+Finally, note that no matter what policy you set on a post, any accounts you mention in a post will **always** be able to reply to that post.
+
+When you are finished updating your interaction policy settings, remember to click the `Save policies` button at the bottom of the section to save your changes.
+
+If you want to reset all your policies to the initial defaults, you can click on `Reset to defaults` button.
+
+!!! danger
+ While GoToSocial respects interaction policies, it is not guaranteed that other server softwares will, and it is possible that accounts on other servers will still send out replies and boosts of your post to their followers, even if your instance forbids these interactions.
+
+ As more ActivityPub servers roll out support for interaction policies, this issue will hopefully diminish, but in the meantime GoToSocial can offer only a "best effort" attempt to restrict interactions with your posts according to the policies you have set.
+
+## Email & Password
### Email Change
@@ -171,6 +190,15 @@ Once a new email address has been entered, and you have clicked "Change email ad
!!! info
If your instance is using OIDC as its authorization/identity provider, you will be able to change your email address via the settings panel, but it will only affect the email address GoToSocial uses to contact you, it will not change the email address you need to use to log in to your account. To change that, you should contact your OIDC provider.
+### Password Change
+
+You can use the Password Change section of the panel to set a new password for your account. For security reasons, you must provide your current password to validate the change.
+
+!!! info
+ If your instance is using OIDC as its authorization/identity provider, you will not be able to change your password via the GoToSocial settings panel, and you should contact your OIDC provider instead.
+
+For more information on the way GoToSocial manages passwords, please see the [Password management document](./password_management.md).
+
## Migration
In the migration section you can manage settings related to aliasing and/or migrating your account to another account.