Fix#271
Add back the `GET /api/v1/trends` API with the caveat that it does
not return tags that have not been allowed to trend by the staff.
When a hashtag begins to trend (internally) and that hashtag has
not been previously reviewed by the staff, the staff is notified.
The new admin UI for hashtags allows filtering hashtags by where
they are used (e.g. in the profile directory), whether they have
been reviewed or are pending reviewal, they show by how many people
the hashtag is used in the directory, how many people used it
today, how many statuses with it have been created today, and it
allows fixing the name of the hashtag to make it more readable.
The disallowed hashtags feature has been reworked. It is now
controlled from the admin UI for hashtags instead of from
the file `config/settings.yml`
body_remote:Someone from %{domain} has reported %{target}
subject:New report for %{instance} (#%{id})
new_trending_tag:
body:'The hashtag #%{name} is trending today, but has not been previously reviewed. It will not be displayed publicly unless you allow it to, or just save the form as it is to never hear about it again.'
subject:New hashtag up for review on %{instance} (#%{name})
appearance:
advanced_web_interface:Advanced web interface
advanced_web_interface_hint: 'If you want to make use of your entire screen width, the advanced web interface allows you to configure many different columns to see as much information at the same time as you want:Home, notifications, federated timeline, any number of lists and hashtags.'
@ -939,6 +943,8 @@ en:
pinned:Pinned toot
reblogged:boosted
sensitive_content:Sensitive content
tags:
does_not_match_previous_name:does not match the previous name