Standardize und unify the tags #1143

Open
opened 2021-01-21 02:17:15 +01:00 by knochenmax · 5 comments
Owner

I noticed that there are different tags for the same ideology/content. This might be an issue if admins are subscribing only for specific tags such as fascism or covid-denial. Maybe it would be a good idea to unify and standardize the tags and implement a tag suggestion mechanism for the web frontend? E.g. when somebody types "fas" in, the system suggests "fascism". An alternative would be to show all existing tags, and then the user could copy and paste or click on a tag to add it to the suggestion.

I noticed that there are different tags for the same ideology/content. This might be an issue if admins are subscribing only for specific tags such as fascism or covid-denial. Maybe it would be a good idea to unify and standardize the tags and implement a tag suggestion mechanism for the web frontend? E.g. when somebody types "fas" in, the system suggests "fascism". An alternative would be to show all existing tags, and then the user could copy and paste or click on a tag to add it to the suggestion.
knochenmax added the
enhancement
label 2021-01-21 02:17:52 +01:00
Owner

I've been looking into auto-completion. It requires that we have 1 text field for each tag. That requires a bit of JavaScript (for an “add tag”-button) and a simple change in the backend. We can also provide backwards-compatibility for the people who don't want to enable JavaScript.

The problem is to get the previously used tags into the autocompletion list. From what I could find out it seems that the list has to be in the HTML file. That would mean re-generating it automatically every time an entry is approved or manually from time to time.

Edit: We can put the tags in a separate textfile and generate the autocompletion list with PHP, so no big problem.

I've been looking into auto-completion. It requires that we have 1 text field for each tag. That requires a bit of JavaScript (for an “add tag”-button) and a simple change in the backend. We can also provide backwards-compatibility for the people who don't want to enable JavaScript. The problem is to get the previously used tags into the autocompletion list. From what I could find out it seems that the list has to be in the HTML file. That would mean re-generating it automatically every time an entry is approved or manually from time to time. Edit: We can put the tags in a separate textfile and generate the autocompletion list with PHP, so no big problem.
Owner

Demo for autocomplete in the frontend.

Demo for autocomplete in the frontend.
Owner

I've prepared the backend, added a cronjob to re-generate the auto-completion list every hour and have the changes to the frontend ready.

Only things left to do is clean up the existing tags and push the changes to the frontend to the website.

I've prepared the backend, added a cronjob to re-generate the auto-completion list every hour and have the changes to the frontend ready. Only things left to do is clean up the existing tags and push the changes to the frontend to the website.
Author
Owner

Demo for autocomplete in the frontend.

That seems alright, I like it!

> Demo for autocomplete in the frontend. That seems alright, I like it!

Another tag that could stand to be cleaned up a bit is "lolicon", imo this should use the gender neutral term "kodocon" instead, as it doesn't really matter to most people who want to block pedophillic art the gender it depicts.

Another tag that could stand to be cleaned up a bit is "lolicon", imo this should use the gender neutral term "kodocon" instead, as it doesn't really matter to most people who want to block pedophillic art the gender it depicts.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FediBlock/data#1143
No description provided.