Then, there are some tags which are misspelled. An example is phbb, which seems to be a mistake of phpbb.
Then, it seems like hcaptcha does not have an icon, and is placed in the Other Tags tag grpup, instead of the Official Plugins tag group. Furthermore, graphviz is missing its icon, while topic-list-author is in the Other Tags tag grpup instead of the Official Theme Components tag group.
Wait! There’s more. The ai-artifacts and ai-custom-prompt are placed in the Other Tags tag group, when they should be in the Discourse AI Features tag group instead. Additionally, the sidebar-tags tag is in the Official Plugins tag group and not in the Official Theme Components tag group.
I apologize in advance if this is being too nitpicky.
Thanks, Nate! Appreciate your attention to detail. As Lilly says, many of these tags are used in various ways not visible to the public. In private categories and personal messages with customers. I look forward to bringing some order to the /tags page!
I just tried adding phpbb to the topics currently tagged phbb and it did not work for some reason. That’s weird. phpbb is in the Migrations tag group but that tag group doesn’t limit who can use the tag.
Quite a bunch of tags here on Meta are ‘visible to Everyone but can be used by staff (I’m assuming)’, so they can be seen in the tag picker (e.g. typing ‘qu’ shows tags like quest and basic-downgraderequest). However, these tags don’t actually need to be seen by the rest of the community, I suppose, except internally. So would it make sense to make these just visible to internal groups instead of Everyone? Or was there a specific rationale for doing this?
if a tag is functionally listed as restricted it should never be seen in the UX by unauthorized members, regardless of how inherently sensitive the data is.
Just-in-time teaching is always a delicate balance between confusing the user by not showing a tag they know exists but can’t use for “reasons”, and bombarding the user with information they can’t do anything about
I’ll have a look if I can improve the user-experience for those tags
the problem is that i don’t understand the current functional logic. why even show the existence of tags restricted to secure categories to unauthorized users?
as an admin, if i make a tag only to be used in a restricted category in the category settings page (Restrict these tags to the 'X' category & Restrict these tag groups to the 'X' category), then i guess i would expect that tags respect category permissions, and thus only users with permissions to that category to be able to see the tag anywhere (regardless of Tag topic allowed groups, or if the user still can’t see any topics with the tag).
i get the wording says “available” and not “viewable”, but still seems odd to me. and of course the bots-gone-mad tag can be seen in a number of places by a user not permitted to that category.
so it is a situation where admins have to be told not to create sensitive tags in secure categories even if the tags are restricted to those categories because they can be found by unauthorized users, or at least, users that the tags are not intended for.
.
). i was literally just typing random words to see what would show up.
