marahmarie: Sheep go to heaven, goats go to hell (Default)
[personal profile] marahmarie

Itsa coming. Saying so because while I don't like to admit suggestions I filed 3,000 years ago still mean something to me, they do, and I was just looking at my Tags page, and holy Mother of God, I don't even know what's on it.

Mainly, I need a way to target locked posts and a way to style other effluvia that helps me get/keep things straight - neither idea is getting implemented beyond what we already have, but at least I can fix views on some other stuff - the tag count in the sidebar and comment counts on the Month page, which admittedly are more aesthetic than practical issues.

Right now I'm trying (and failing O_o) to find a post about eBay made around Christmastime; it's not under my eBay tag but should be. If I had a way to parse protected posts from public posts (it's protected) that would narrow it down a bit. And while technically there *is* a way (there's some CSS I can pull and target; I've done so in the past but don't even think I own a copy of that version of this style anymore) it's limited in scope because so many of my tags encompass both public and protected posts that there's no way for the CSS to target one or the other - so no, the CSS can't say: "Tada, here are only locked posts made under this tag."

Which is exactly what I need it to do, and doesn't seem like an unreasonable thing for it to do, but probably requires so many orders of magnitude of rewriting the backend tag publishing system that it's not worth doing (and while I don't think I can prove it as I don't know if I kept a local copy of this suggestion, I'm pretty much 100% sure I've suggested this functionality in the past).

The changes rolling out won't address that, but I almost don't care, as the CSS I can currently target will still say: "There has ever been a locked post under this tag"; it just takes longer to trawl through the results, as public posts will still be mixed in with protected (because the CSS will always, if I recall correctly, default to targeting the pseudo selector for any protected posts that fall under each tag).

ETA, next night: and that's fine and well, but the logic for deciding which tags get the public or protected parameter looks like it tends toward "whatever parameter has the most posts is Winner Takes All", which means a majority of my locked posts won't show up merely by exposing whatever tags do get the visibility protected selector assigned to them. In fact, adding such CSS would be equivalent to hiding even more posts on myself than I do now simply by mis-tagging or forgetting to tag.

But that means finding and targeting the exact CSS again, then adding it to my style sheet and updating it - I mean, to find one freaking post (there are probably others, which is why I find myself bitching about Tag page CSS in general - I know I'll have to go back and find and re-tag more stuff, not to mention change some posts from protected to public, as I accidentally forget to change the access level on more of them than I care to admit).

It would just be so nice to have a way to sort out public posts from protected ones, as that's sort of an informal filing system in itself - at least for me.

ETA2: just checked Archive Year and Month: Year doesn't parse public from protected posts via CSS, while Month shows a lock next to each protected post, so I'm not sure what else it would need - if anything - to make it more useful. (Maybe unhiding tags on that page would help - will try that next to see what can be manipulated, if anything).

ETA2a: Month doesn't parse between public and protected filters, it just slaps an .access-filter selector on anything not public, which wheeee, why don't we have standardization across our CSS, I think that kind of bugs me. Unfortunately (if you're looking to hack in some sort of workaround) the CSS is semantic, so there's no sneaking in say, dt .access-filter + tag {do this:now} and making it work. I can target surrounding CSS, but that just changes all instances of it on the page without targeting merely the protected tags I'm after.

ETA3: [personal profile] brainwane points out a few ways to parse public from protected posts, namely by using URL parameters like so: "https://marahmarie.dreamwidth.org/?security=access" or choosing from a list of parameters:

If you try a value for "security" that doesn't exist, like "custom", e.g.,
https://marahmarie.dreamwidth.org/?security=custom

you get a list:

"You can filter entries by the following security level:

Public [link]
Access List [link]
Private [link]

[personal profile] darkoshi adds that you can combine tag names and security parameters like so: "https://marahmarie.dreamwidth.org/tag/websites:+ebay?security=access". The page they saw that on also has this suggestion from [personal profile] chagrined:

you can already search for two tags at a time also but I'm on my phone and don't remember the syntax for that ottomh, I can look it up l8r if u want. I think it is limited to only 2 right now tho. but still handy.

eta: nm found it in faq it's tag/tag1name,tag2name?mode=MODE

and where I wrote MODE put either "or" or "and" (and gives only posts with both tags)

iirc can stack with security level filtering too I think

/tag/tagA,tagB?mode=and&security=private

All of these tricks are lovely and useful, but not what I want. I'm just looking for a way to parse - in particular - what's public from what's private without having to scroll through pages of posts found under each tag. Lists of posts found under each tag, sorted by public or protected parameters, would be better - an internal, non-public way to get search results for my posts, in other words, in simple list form, with dates besides the posts under each security parameter in question to help determine which is the lost post (or posts) I'm after.

Basically, I want a system so simple it works for people suffering from memory loss. I'm not claiming that might be me, but there are days it feels like it.

Re: ?security=access

Date: Apr. 7th, 2017 03:36 am (UTC)
darkoshi: (Default)
From: [personal profile] darkoshi
You can also combine a /tag/ URL with a security level parameter, like this:

https://marahmarie.dreamwidth.org/tag/websites:+ebay?security=access

I had recently discovered that via:
https://dw-suggestions.dreamwidth.org/1460727.html#comments

(And I didn't realize that tags could be put in hierarchies until looking at your tags page just now.)