20
votes
Lets discuss tags, again
There's been some discussion around tags since users were given tag-editing privileges, such as Tag Use and Article Tags
I've noticed a few things about tags and rather than make a topic for each one I thought I'd make a few top level comments instead, hopefully with others doing the same for anything tag related they'd like to see discussed.
Some people have been adding tags that seem questionable, such as
grandstanding
(removed) andrant
(not removed)Should these be acceptable tags?
Grandstanding definitely does carry a negative connotation, but I think rant is fine enough
I would just like to point out, I did not mean "grandstanding" in a negative way, in my opinion that's what that post is and I see no difference in tagging it as that over "rant". But if "rant" is the more widely accepted vernacular I get that. I was not meaning it to be offensive.
Sorry I'm late to the topic.
I'm one that added "rant" to a topic.
As other have stated, rant is not necessarily a negative adjective.
I added the tag to a topic that was criticising some Reddit things and honestly "critique" wasn't sitting right with me because a critique is something you make to the direct criticised entity.
If you do it somewhere else, it's a rant in my book.
And again, it is not negative, it's just a more colloquial term than "complain".
Currently there are 3 types of game development tags,
gamedev
,game dev
, andgame development
that I'd like to see consolidated. My preference would begamedev
orgame development
as an extended version (see the other top-level comment about acronyms/extended tags)I wonder if its worth thinking about some kind of automatic system/AI that shows you commonly used variables of your tag on Tilde while you're typing it, so you can add the others?
Adding autocomplete based on existing tags will also go a long way to discovery and encouraging standardization.
This feature is currently being worked on: !15.
I believe in the future tags will be aliased, so that
gamedev
andgame development
would list the same topics, even if they only have one of each.Yea I guess that would be the same general idea, just done in the background without needing input. That would be nice.
What about game.dev ?
dev as a subtag of game doesn't make a lot of sense when there's a ~games group, is
game.dev
clearer thangamedev
in ~games? in ~comp?Having a
game
tag in ~games goes back to the redundant tags comment I made elsewhere.In the future I'd like to see ~games.dev as a subgroup, but for now a logical tag would be better.
Yep that makes sense. So does adding just a dev tag to ~games effectively do that? I'm a little fuzzy on how the transition is made from ~games with a tag dev to ~games.dev
I believe it can just be replaced, so say ~games.dev is created and a bunch of topics have the
gamedev
tag, they could all just be moved in to there and have the tag removed. The only question would be if gamedev tags in other groups should be moved in to ~games.dev too (for this particular subgroup I'd say so)One thing we can do to help with consolidation is to have a type-ahead when entering tags. That way someone will type out
gam
and see the most common tags that begin with that string, perhapsgamedev
,gametes
and...gamergate
.As discussed briefly here (and applied in a few of the newer topics)
Should
ask
andsurvey
be changed toask.survey
,ask.question
andask.help
, making them hierarchical.Deimos replaces
ask.recommendations
withask
andrecommendations
I really like the hierarchical
ask.x
tags, because they're an attempt towards standardization and make sense for my brain. Deimos changing that example throws me for a bit of a loop, I'll admit.I think I changed it because there are some issues and strange behavior still with the hierarchical tags.
Specifically, if you filter "ask", it won't filter out any hierarchical versions like "ask.survey" or "ask.recommendations". I know that getting rid of the "ask" posts was one of the main reasons people wanted filters in the first place, so I didn't want to ruin that. That needs to be fixed fairly soon though, so tags can be used more properly.
It's worth noting it was a long time ago so it may not hold true anymore. Also, recent threads doing
ask.survey
have not been changed back. I'd like to see this standardised in the docs if we go this way though, as it's one of the main tags mentioned.I don't believe
recommendation(s)
should be underask
, but perhaps others disagree.Some articles have the
long read
tag should this become a standard tag? does it grant any benefits? how long does an article have to be?Deimos himself suggested and uses the "long read" tag i. I think that makes it a standard tag. :)
I'd say that any article which takes more than about 5 minutes to read should be classed as a long read.
I wasn't aware, in that case it seems pretty clear it should remain and that it's not solely about the length of an article, but also how insightful it is.
I can see benefits and drawbacks of having tags for the length of articles.
Benefits would be because not everyone has time to read a long article and it could be useful to know that it's going to be a time commitment before opening the page.
Some drawbacks that come to mind is that length can be arbitrary and entirely dependent on the OPs opinion, and I don't think that's a very useful tag if that's the case. Another consequence it could have is that it can encourage laziness or the posting of lower quality articles if it becomes popular to filter out posts with a
long read
tag.I don't have any actual evidence for the latter fear, so it might not be as big a deal as I'm making it seem.
I think this would be the same scenario as an
article
tag, which Deimos commented on here. When advanced link scraping is implemented, article length is probably something could be automatically detected.I guess the obvious way it would be helpful is if someone only has a bit of time to read something. The downside is if people start filtering it out in favour of shorter, potentially low quality articles.
Looking at https://tildes.net/~tildes.official/342/daily_tildes_discussion_proposals_for_trial_groups_round_1#comment-xp2 it seems that the long read tag isn't just about length, so it's not something that can be scraped. It's also about how insightful it was (on top of being long)
you already have word count after the post title, so the tag is a little bit redundant, also the tag can be a author view, what the OP considers long i might not consider or vice versa
Word counts are only for text-posts, not articles. The tag is subjective though.
yeah, in case of links i agree on the tag use, otherwise it is redundant
I've been creating a de facto "social science" sub-group within ~science by using hierarchical "~socialscience.abc" tags on articles there. The idea is that these tagged topics will eventually form the basis for a ~science.socialscience sub-group or even a ~socialscience group.
We need some kind of shared document or wiki page where we can compile all this.
There's a wiki here
Tags are for searching for and grouping related content, yet some are so overly specific that the number of topics that would have such a tag would be incredibly limited.
this topic uses
clean power plan
instead ofclean power
this topic uses
healthcare delivery
instead ofhealthcare
I personally like tagging the publication/source and make it a habit to do so. "The Atlantic" is the name of the publication, if it were to just be tagged "Atlantic" then that would refer to the region/ocean. That way if you want to see all topics posted from a specific publication you can.
I usually use the abbreviated name of publications when tagging them (NPR, CNN, BBC, CSM, ect ect) but it's kinda hard when the publication does not have an abbreviated name.
Although I do agree with the point you are making.
My mistake, I didn't check it thoroughly. I'll remove that example.
No worries!
It makes sense at the surface and if it had been referring to the ocean I would entirely agree with you.
I agree: tags are search terms, and should be treated as such. They should tend to be more general and collective rather than particular and specific.
In that case a less specific version of the tag can be added that is still relevant. There's no harm in adding healthcare or power plan alongside the existing tags.
Standardised trigger warning tags have been discussed and used a few times, though for the sake of filtering we need to agree on a main tag, otherwise it's useless.
this topic uses
trigger warning
this topic uses
triggers
this topic uses
trigger
While we'll probably never come to a consensus on whether or not such a tag is necessary, I feel
trigger
is enough for filtering and situational awareness purposes for those who care for it. It's short and to the point.A part of me wants to add a hierchical element to warnings like trigger.rape. but idk if that's too much.
I feel like that makes sense.
The last topic I linked uses
trigger.rape
and I believe the discussion thread talked about a hierarchy system. I'd favourtrigger
ortriggers
overtrigger warning
Filtering isn't properly implemented for hierarchical tags yet.
Some tags are shortened or acronyms are used, others are extended, and in some cases both are used.
Deimos adds
tf2
tag and notteam fortress 2
in this topic
dnd
anddungeons and dragons
are both presentHow should this be handled? should both forms be added?
I don't really have a master plan for it. I think the long tags can be pretty ugly, and if there's an accepted/well-known acronym for something it's probably reasonable to use. Maybe the long form is better overall though, I don't really know. Again, maybe something like "tag synonyms" is the best approach over the longer term (though we'd still have to decide which synonym to display).
I personally prefer shorter tags if possible, and without spaces.
That said, in some cases even though a shorter form is available it is either ambiguous or not used much. For instance
league of legends
is commonly known asleague
, butleague
could very well be ambiguous in regards to esports or regular sports. Its acronymlol
is perhaps less ambiguous despite being a common acronym simply because "laugh out loud" would unlikely be an appropriate tag but what do you do about some other name, perhaps another game, that also shares the acronymlol
? who gets priority?I think we probably shouldn't try to make tags globally unique. That's one of the main benefits of the hierarchy, and we'd be losing it if we try to have a single namespace for tags.
As a simpler example, consider something like "strategy" in a game group. You shouldn't need to tag every post in the League of Legends group as "lol strategy" so that it doesn't conflict with the "strategy" posts in the Dota2 one. It's fine to have the same tag used in different places and the context come from the group (and searching and other functions should help handle this when they're more developed).
Some redundant tags appear every so often
tech
tags (I've removed them all now)meta
tags (Some were removed before, I've removed newer ones)A simple automated rule would work for most of these, don't allow a tag if it matches the group name. What other redundant tags are there?
I spotted one tag that was
tech.support
in ~tech, I replaced it withtechsupport
. When dealing with subtags of redundant tags, do replacements like this make more sense?I could very well be misunderstanding the intent between tagging and the creation of new sub~'s, but I feel like
tech.support
makes more sense. A future sub could very well be ~tech.support. I suppose the tagsupport
could be used then, but there's an ambiguity there.I was conflicted too, on one hand
tech
is redundant, yettech.support
could be a valid group and thus using a tag that matches it would appear to be more correct. I'm super in favour of tags matching potential group names.support
on its own is too ambiguous when looked at site-wide, but not when it's confined to ~tech. Should that ambiguity be allowed?I actually just today realized that clicking a tag on a post only shows me that tag within whichever ~ I'm in, not site-wide.
Speaking as a person of entirely no consequence or authority,
tech.support
seems more intuitive than just puttingsupport
, when you're posting with the idea of 'tech support' in mind.I think
tech.support
is the more appropriate tag in this case, if in the future it's made into a group the tag can help in moving old posts there.I had used meta on one or two topics in ~tildes, because I had felt that there ought to be a distinction between topics that involve the sites' functionality and those that involve the sites' functionality. You are right though, 'meta' as a tag in ~tildes is redundant -- a 'community' tag might be more suited to that purpose.
community
andsite design
would divide things up nicely.(De)pluralising tags
this topic went from
request
torequests
andsuggestion
tosuggestions
this topic went from from
trials
totrial
is this necessary? what's the best way to go about this?
A bit of info here about how I've been thinking about plurals: https://docs.tildes.net/topic-tagging#general-tagging-guidance
It's not always clear though, and also won't really matter much a lot of the time, as long as it's consistent. Eventually it may even be simplest to just have "tag synonyms" where either works the same.
In that case, should we assume that tags should try to be as "group-name" friendly as possible?
For instance,
tech.support
,games.recommendations
,games.dev
. What should the tag be in the meantime within those groups, given thattech.support
in ~tech makes the parent tag redundant, orgames.dev
in ~games? use the full hierarchy anyway?I think it's good to aim that way when it's reasonable, but don't worry too much about it. I can always bulk-convert tags when creating new groups if needed.
I changed the
request
andsuggestion
tags in accordance with the tagging guidelines Deimos linked.We need a way to leave notes explaining the actions we take. I'm thinking a meta page for each topic like wikipedia's talk page, where we can discuss what mod actions the topic needs.
Whoops, yeah that's my bad on the trial/trials tags. I saw trial was used more commonly (it also sounded a bit better in my head) so I switched over the couple of stories I saw with trials, forgetting about the specific tagging guidelines. My mistake!
I'm just trying to get some discussion going with examples, doesn't necessarily mean the examples are good/bad :)
trial
makes more sense to me as a standalone tag and is more intuitive, buttrials
makes more sense as a subgroup like ~news.trials like the docs sayIt can feel wrong to use a plural for a topic about the singular but it does seem to be the preferred way so probably best to stick to it.
The latest one uses
challenge.programming
, how do you feel about that?perhaps a way of tagging all challenges site-wide even from within their respective groups, like challenges.pixelart in ~creative for drawing some specific thing.
We've already had a few writing prompts as well.
Even if the rest of the structure wasn't used in the same way, standardizing the top-level "challenge" tag wouldn't be hard.
https://tildes.net/~tech/5er/an_isp_based_in_texas_has_complained_to_a_judge_that_the_music_industry_to_trying_to_turn_internet
Ok so I have a question about the way this post is tagged.
Among other tags it has: law, copyright, copyright law
Does it make sense to change that to just law.copyright
Looking through the existing topics with those tags,
law.copyright
would make sense to me personally.