thnidu: my familiar. "Beanie Baby" -type dragon, red with white wings (Default)
thnidu ([personal profile] thnidu) wrote in [site community profile] dw_suggestions2011-12-31 07:51 pm

Make the tag "security" label useful, or remove, or at least explain it

Make the tag "security" label useful, or remove, or at least explain it


The "security" label on the tag management page is (1) redundant and (2) misleading. (1) It is simply the lowest level (highest line on the chart right above it) that applies to any post tagged with it. (2) By being there at all, it suggests that it is useful, e.g., a settable value for "who can see this tag".

See Request #12096, under "Site Interface". I asked about the tag, and was told
"Tag security is tied to entry security. If the posts used for those tags are public, then the tags will also be public."

My reply:

So, if I use a tag only for filtered posts, the page for that tag will say "Security: filtered". But the first time I use it for a public post, the "security" level will change to "public". In other words, it's exactly equal to the label on the lowest security level (highest line on the list just above it) with a non-zero count.

The screen is deceptive. Giving a "security" level for the tag strongly implies that there is a security level ASSOCIATED SPECIFICALLY with the tag, and that it can be set somehow. I've been assuming I can set security for any post independent of any other post and any other setting. This "security" field is not only useless -- totally redundant with the list above it -- but misleading as well. Either

1. make it meaningful -- e.g., by letting the user set "who can see this tag" (I may not WANT everyone to know that I've tagged a particular post as "love life", or that I have such a tag!)
2. or rename it, e.g., "lowest security level of posts with this tag", or something shorter that says the same thing, if you can think of a wording
3. or remove it entirely.

Is the meaning of this field described anywhere online? Unless you follow option 3, there should at least be a link on the "security" label to explain it.

My preference is #1. I know that would take more work than #2 (+ the info link), but that would be adding something useful.

Poll #9006 Make the tag "security" label useful, or remove, or at least explain it
Open to: Registered Users, detailed results viewable to: All, participants: 65

This suggestion:

View Answers

Should be implemented as-is.
28 (43.1%)

Should be implemented with changes. (please comment)
8 (12.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
28 (43.1%)

(Other: please comment)
1 (1.5%)

montuos: cartoon portrait of myself (Default)

Re: I really like 1, though I can understand how 2 is the easier way to go.

[personal profile] montuos 2012-01-07 01:43 am (UTC)(link)
Option #2 is something that can be quickly and easily accomplished, and I agree that the current wording is confusing at best. For best results, also add a link to a FAQ entry. (I just went over and looked, and I have no idea what "trusted" means!) I think this needs to be done regardless of whether option #1 is chosen and implemented.

I really really really like option #1 and would love to see it implemented!

  • how to make it obvious that specific tags are nonpublic

    Use the same lock icon that filtered posts have.

  • if this gets implemented, how to deal with pre-existing tags?

    Set each at its current lowest security until it gets deliberately changed otherwise. It will probably be more effort to implement, but it will cause infinitely less annoyance for users. There are one or two tags I'd like to change to a tighter security level, but most of them are fine as they are, and I really don't want to have to go through and change every single one of them to a different level!

  • how do we tell the Entry Creation page what security level a given tag should be?

    For brand new tags created by using them in an entry, default could be either private (safer and probably easier to code) or whatever security level that entry gets when it posts (this would be more useful to me than defaulting to private). More complex controls should be reserved for Manage Tags.

I'm opposed to option #3; I rather like being able to select a tag and be assured that I haven't used it publicly, even if I can't directly verify which filter(s) I've used it in.