Commit 7dae19e9 authored by Eugen Rochko's avatar Eugen Rochko

Update content/posts/2019-10-04_Mastodon-3.0-API-and-deployment-changes.md

parent e846215e
Pipeline #850 passed with stages
in 23 seconds
......@@ -4,10 +4,12 @@ subtitle: "New APIs, deployment options, and admin settings"
description: "Detailed notes on REST API changes, new deployment options, new admin settings and how to use them"
draft: true
author: gargron
date: 2019-10-04
date: 2019-10-12
tags:
- mastodon
- api
categories:
- Guides
---
### New REST APIs
......@@ -135,7 +137,7 @@ Sometimes various counters in Mastodon get out of sync with reality. To fix acco
**Trends**
Hashtags will not trend without your approval. Whenever a hashtag is beginning to trend, you receive a notification e-mail asking to review it. You can disable those e-mails from your personal e-mail notification preferences. You can disable the trends feature altogether from admin settings.
Hashtags will not trend without your approval. Whenever a hashtag is beginning to trend, you receive a notification e-mail asking to review it. You can disable those e-mails from your personal e-mail notification preferences. You can disable the trends feature altogether from admin settings. Or you can choose to auto-approve hashtags instead, which may be suitable for trusted communities.
The hashtags area in the admin UI has been updated. When looking at hashtags that are pending review, you can approve or reject them in batches. From individual hashtag view, you can control whether the hashtag can trend, whether it can appear on the profile directory and in searches, or whether it can be used at all. You will also see which servers you know about are contributing how much to that hashtag's usage to help you determine whether to let it trend or not.
......@@ -157,4 +159,4 @@ The custom emojis area in the admin UI has been updated. You can now assign emoj
**Spam checks**
When a user mentions someone who isn't following them *and* it's not a reply to something directed at that user, their message is run through a simplistic spam check which detects repeating messages. When spam is detected, the offending user is auto-silenced and a new report is created automatically. If that was a mistake, you can manually unsilence the user, and they will be exempt from future spam checks. You can disable the spam check feature from admin settings.
When a user mentions someone who isn't following them *and* it's not a reply to something directed at that user, their message is run through a simplistic spam check which detects repeating messages. When spam is detected, a new report is created automatically. If that was a mistake, you can mark the report as resolved and it will exempt that user from future spam checks. You can disable the spam check feature from admin settings.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment