Repository navigation
Change admin UI for hashtags and add back whitelisted trends - #11490
Merged
Merged
Conversation
Gargron
added
api
Gargron
changed the title
Gargron
force-pushed
the
feature-admin-ui-hashtags
branch
from
August 5, 2019 14:24
99a830d to
b52a650
Compare
ykzts
approved these changes
Aug 5, 2019
Gargron
force-pushed
the
feature-admin-ui-hashtags
branch
2 times, most recently
from
August 5, 2019 16:36
6f82b1f to
4bc58a6
Compare
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`
Gargron
force-pushed
the
feature-admin-ui-hashtags
branch
from
August 5, 2019 17:32
4bc58a6 to
bc28ffe
Compare
6 tasks done
hiyuki2578
pushed a commit
to ProjectMyosotis/mastodon
that referenced
this pull request
Oct 2, 2019
…n#11490) Fix mastodon#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`
|
This MUST be configurable for instances. It may be scalable for a corporate mastodon server, but it is certainly not scalable for public instances like mamot.fr. Instead there should be an option for a user NOT to see toots with a certain hashtag. Because the end-user counts in public servers. While a corporate server may have a fulltime moderator to do all that, a public instance will just bottleneck the flow of information and people will find alternatives to hashtags which sensibly distorts the UX |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #271
Add back the
GET /api/v1/trendsAPI 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