![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Add the ability for logged-in users to visibly sort the Tags Page by access level.
Title:
Add the ability for logged-in users to visibly sort the Tags Page by access level.
Area:
Styles
Summary:
There is currently a hidden feature on the Visible Tags Page: the ability to show the approximate access-level assigned to each tag. I would like DW to add CSS or a combination of JavaScript and CSS to all our journals to show the hidden feature to everyone who opts-in.
Description:
Currently the Visible Tags page shows all your tags in a single, alphabetically sorted list but does not *visibly* indicate which tags are used on private, access-list-only or public posts. So one day about a year ago I asked myself, "Why not?" and wound up writing CSS that exposed the access-level of all my private and access-list-only posts. This became a fantastic sorting system since I have no other way to tell what I've thrown where without using the Manage Tags page, which can be kind of awkward and time-consuming.
So a week ago I took this a little further and refined the CSS so that 1) only logged-in users see the access-levels alongside each tag and 2) logged-in users see the exact access level used on each tag - public, private, or access-list-only. Here's a screen cap of my current Visible Tags page using my latest CSS for it (logged-in view - logged-out you won't see any of the extra information shown in this screen cap):
http://i287.photobucket.com/albums/ll128/marahstest/expose_access-level_tags_page.jpg
What I'm humbly hoping for is this system of sorting tags by access-level, as seen in the screen cap, gets adapted site-wide either as the default view on the Visible Tags page (of course, it will be visible to logged-in users by access-level only) or else becomes an opt-in default option (which is where JavaScript would probably come into play; otherwise, this is a pure CSS hack).
There are a few possible issues with adapting this styling: 1) it may take more firepower to serve up the additional CSS (but I'm thinking it would not be enough to crash servers or do anything that dramatic as things stand; it's just hard to calculate how much this might slow things down without knowing how much firepower DW has to spare) and 2) there is currently an issue where if you use a tag at more than one access level (say you use your "cats" tag both publicly and on several access-list-only posts) it will get an HTML tag indicating it's for public use only, which means DW won't be able to style it with the specific CSS to reflect that you used it three times publicly and three times for access list readers. Until that split-usage quirk is fixed, my idea makes for an imprecise-at-best look at how your tags are being used. But I think it's still better than not having any sorting system in place at all; in the meantime you can still use your Manage Tags page to drill down more precisely.
If this were to get adopted, I could see future improvements to it such as sorting tags by access level on the Visible Tags Page instead of sorting them entirely alphabetically as we do now, adding the ability to style each access level separately, and so on.
This suggestion:
Should be implemented as-is.
15 (31.9%)
Should be implemented with changes. (please comment)
0 (0.0%)
Shouldn't be implemented.
3 (6.4%)
(I have no opinion)
28 (59.6%)
(Other: please comment)
1 (2.1%)
no subject
no subject
So an enthusiastic YES! from me for this suggestion. :)
[ETA] As per cesy's comment: the style in the posted screencap is a mixed bag on privacy.
If you were to look at my LJ tags page (you can, if you'd like--it's the same username), you'd not see any tags used only on locked or private entries. If a tag is used on a mix of open and locked/private entries, though, the table does give you that information. For instance, both "private" (only me) and "under the cone of silence" (only friends) are invisible to me when I'm logged out. But I can still see that "aha!" (mixed public/friends) is used on one locked entry.
It's not much of an issue for me, but I imagine it might be for others.
no subject
But I can still see that "aha!" (mixed public/friends) is used on one locked entry.
But that's not a privacy issue. Anything the public can see, your friends can see, too. :)
As per cesy's comment: the style in the posted screencap is a mixed bag on privacy.
My screen cap, the one I put in the OP? As I said in the sentence that preceded it, "logged-out you won't see any of the extra information shown in this screen cap". Logged-in you won't, either, unless I have already granted you the correct access level to do so (and of course, I haven't done so, since no one but me is allowed to see my private posts, and no one but my access-list is allowed to see access-list-only posts on my DW). That's why I posted a screen cap, to show everyone what they can't see otherwise so they can understand how my suggestion would look and work.
no subject
(Screencap was also referring to that Smooth Sailing image.)
no subject
no subject
no subject
But that's not a privacy issue. Anything the public can see, your friends can see, too. :)"
I think you've got it backwards - it's not that a friend can see both "aha!" entries, but that looking at that page logged out, right now, I can see that there is an "aha!" entry I can't see, because I'm not on
no subject
no subject
no subject
Just as a matter of fact...
(edit) Unless...OK, think I got it...tags worked the same way there as here until last week, so on LJ right now if you split a tag up amongst public and friends posts, the friends posts count won't show because the rounding up is done in the public post's column. Got it! It is indeed the same bug we had, and that's what the bug looks like once my Suggestion here is implemented there. This won't happen on DW now, though, because swaldman patched the bug last week, promise. :)