summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/api/swagger.yaml2
-rw-r--r--docs/user_guide/settings.md3
2 files changed, 4 insertions, 1 deletions
diff --git a/docs/api/swagger.yaml b/docs/api/swagger.yaml
index 75fa2a777..563a0c16f 100644
--- a/docs/api/swagger.yaml
+++ b/docs/api/swagger.yaml
@@ -8403,7 +8403,7 @@ paths:
type: file
- description: |-
Type of entries contained in the data file:
- - `following` - accounts to follow. - `blocks` - accounts to block.
+ - `following` - accounts to follow. - `blocks` - accounts to block. - `mutes` - accounts to mute.
in: formData
name: type
required: true
diff --git a/docs/user_guide/settings.md b/docs/user_guide/settings.md
index 17f2c5962..691181cb9 100644
--- a/docs/user_guide/settings.md
+++ b/docs/user_guide/settings.md
@@ -266,3 +266,6 @@ Both merge and overwrite operations are idempotent, which basically means that d
!!! info
For a variety of reasons, it will not always be possible to recreate every entry in an uploaded CSV file via importing. For example, say you are trying to import a CSV of follows containing `example_account`, but `example_account`'s instance has gone offline, or their instance blocks yours, or your instance blocks theirs, etc. In this case, the follow of `example_account` would not be created.
+
+!!! warning
+ The CSV format for mutes does not contain expiration data, so temporary mutes are exported (and imported) as permanent mutes.