about summary refs log tree commit diff
path: root/app/views/admin/tags/show.html.haml
AgeCommit message (Collapse)Author
2019-10-24Add noopener and/or noreferrer (#12202)BSKY
2019-10-01Fix hashtag link to directory in AdminUI (#12005)mayaeh
* Fixed not to generate link if no user used hashtag in directory * Added missing translation for AdminUI custom emojis * run yarn manage:translations en
2019-09-15Change the hashtag link from WebUI to public page (#11845)mayaeh
2019-09-03Fix error in admin UI for hashtag usage breakdown (#11743)Eugen Rochko
2019-09-01Fix wrong percentages in admin UI for hashtag usage breakdown (#11714)Eugen Rochko
2019-08-08Fix weekly usage not being displayed correctly in hashtag admin UI (#11524)Eugen Rochko
Fix percentages in usage breakdown having too many digits Change trending hashtags to only ask for review if a hashtag enters the top 3 position in the set, since it's the only items shown in the default web UI
2019-08-07Add breakdown of usage by source to admin UI for hashtags (#11517)Eugen Rochko
Allows determining where the majority of posts in a hashtag come from on a given day at a glance.
2019-08-07Add number of pending accounts and pending hashtags to admin dashboard (#11514)Eugen Rochko
2019-08-05Change admin UI for hashtags and add back whitelisted trends (#11490)Eugen Rochko
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`