marahmarie: Sheep go to heaven, goats go to hell (Default)

What with how my DW tags are an eye-crossing experience and my CSS is incapable of separating post security fact from fiction because That's Not How This Works, MM™? Looks like it's pretty much sorted. I have no new suggestions to make thanks to the ingenuity of other DWers, so now it's just a matter of waiting for my wishes to bubble up through the pipes.

My top 3 picks for "If these get implemented then I think I'll be OK"

The following were "migrated", which I think means "submitted to the bugtracker"

My additional picks for "If these were implemented, then I might've been OK"

The following were "rejected" or marked "exists"

marahmarie: Sheep go to heaven, goats go to hell (Default)

The Importer's been kind of blowing up? So please, if anyone can jump in there so I can submit my own (comparatively unimportant) questions and have a reasonable chance of being answered before even more of my hair turns grey, that would be awesome.

marahmarie: Sheep go to heaven, goats go to hell (Default)

ETA, 4-12-17: updated with new post; doing ETAs was too complicated.

And this is where both Dreamwidth search and my tags would've failed me: the word "eBay" wasn't in the title of one post, and neither had "eBay" listed as the tag (nope, the tag chosen for both - apparently after I threw a dart at it, blindfolded - was "experiential", my fancy term for "completely uncategorized but might wander off into the personal". Except even that's not a good way to find the unfindable because sometimes I don't use that tag, or I use one related to the subject matter but not the main point of it, or I don't add any tags at all).

Again, if there was some handy-dandy way to parse public from protected posts that gave a list of results for each parameter (I'm not even sure it would have to be tied into tags, but to have both - tag + security or just security - would be better) as opposed to scrolling through pages of posts to find titles that sort of sound like what I'm looking for, would cut both time and my anxiety and confusion, which only makes me more forgetful, since these things tend to snowball in on themselves once finding lost posts becomes a time-consuming PITA.

Which leads to me making more mistakes, which is a rabbit hole I promise y'all don't want to go down.

While I do enjoy hunting things down (online or off), you can pretend I never told any of y'all that as far as hunting things down on my DW goes, because I hate not being able to (instantly) find whatever's on it (a topic I apparently need to re-familarize myself with).

[staff profile] denise is still holding one suggestion of mine in queue (the suggestion is on a totally unrelated subject) so I'm debating whether to stack another suggestion about this topic on or wait until the last suggestion clears (don't quote me, but this time I'm pretty sure it clears). And I'm not sure what the new suggestion should be, and also not sure which version of said suggestion I'm 100% sure I posted last time around, nor whether it got published or rejected, so I think I should look through my previous posts on Suggestions, read other people's similar ones, and check out how searching posts by tag/security works on Wordpress and other shared social media sites before I write some new idea up for DW (update, 4-12-17: Denise is still holding the same suggestion in queue. The rest of this is expanded upon in my next post).

But right now I'm going pretty strong on lists: ie, what you get on editjournal or with Search, so my idea might build off that (I dislike using URL parameters because I don't want to see posts results, I want to see results with lists of posts, so they're out of the running, pretty much).

marahmarie: Sheep go to heaven, goats go to hell (Default)

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: "" or choosing from a list of parameters:

If you try a value for "security" that doesn't exist, like "custom", e.g.,

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: "". 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


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.

marahmarie: Sheep go to heaven, goats go to hell (Default)

That's what I get for going offline for a few days, I swear to God (I just needed a break, it happens)...I come back tonight (well, right that tonight?) and I've got 40 comments/poll votes to look over.

My mind's not exploding or nothing, nope, not mine. :)


ETA, a few hours later: I wrote title text on the link above (now deleted) saying at least four of my Suggestions went up but only two did (Give Us The Ability to Delete Junk Data and Spam From Polls and Add time/date stamp to Inbox messages) but the latter isn't under this username*, which I'll explain at the end.

What confused me was I linked to a poll of mine in the first Suggestion which made me think I saw at least three new polls in my Inbox. I assumed they were all Suggestions when one was actually that same poll I made a while back. Also, it got spammed and I became a total bear in the comments to everyone perhaps because it got spammed, perhaps because I really, really hate spammers. And spam. My apologies! Belatedly! It got new life and everyone's voting on it again. Gaaaaaaah. I'd like to rip my hair out.

I think [staff profile] denise was holding at least six of my Suggestion posts since the last time she ran the queue, with two of those published yesterday - but I have to check through copies I made to be sure.

If I got at least two rejections in the last year (which is possible: there's definitely been at least one!), have two new posts up and am missing two more, that's two more rejections I might be getting - but again, I have to find the folder on my computer that holds them, which I had to create years ago to account for how much time goes by between submissions and Denise running the queue.

Without this folder I have no idea, after a while, what it was I even suggested. (Unfortunately I don't keep offline copies of rejections received - but they might be preserved in my email Inbox, so if I feel like going on a wild goose chase to match up rejections to what I've submitted, that's the only way to go about it.)

*The Suggestion made under username [personal profile] style_tester was mine. I have two CSS testbed journals - that and [personal profile] style_test - so if you ever see me do stupid, stupid shit like leave a comment or post to Suggestions under these names, it was an accident, not because I'm trying to keep things all like on the downlow. I guess coding makes me start thinking about different things because my mind wanders, then I forget to log out and log back in under this name to post whatever I was thinking so gaaaaaah I don't know.

ETA, 2-24-17: apparently the folder I can't keep track of Suggestions without? I deleted it at some point. I have copies of suggestions made but only the ones submitted up until mid-2015, but they're not in a folder, so something went wrong. No new rejection letters since posting this, so I guess that's it.

ETA2: But heh, as soon as I posted the first ETA, it hit me I forgot to check my external hard drive! There is hope I might still find something! But I'll have to find and hook up that hard drive, first.

ETA3, 2-28-17: Checked my external hard drive, OneDrive, current hard drive contents, past hard drive contents, but nothing I've submitted in roughly the last two years shows up. I've got one more thing to try, but I don't know when: I switched hard drives on my laptop sometime last summer or fall. I have an external connector to hook the last one back up and look it over but since I usually wipe and format them, I'm not holding my breath.

marahmarie: Sheep go to heaven, goats go to hell (Default)

ETA, 2-22-17: Aaaand killed, rewrote and re-submitted this request, try next one... bingo. (Actually, I'm surprised "Wow, that's weird!" took a whole week to find me. My luck holds as usual).

ETA, 2-28-17: Not weird, just another issue.

  • Move background images from WP to DW (but keep WP backups and WP style sheet, just in case)
  • This layout looks 7 years old and is actually 7 years old; maybe do something about it - ETA, 2-28-17: maybe not? I actually hate doing new code.

Dreamwidth is running a beta of HTTPS Everywhere. This page turns it on; right now it's the second red button down from the top.

I turned it on tonight (actually, just minutes before opening the editor for this post) and have done exactly zero poking or prodding. Since I'm a frequent finder of Wow, that's weird!, if there's any Wow, that's weird! then hopefully my luck will hold. I like finding bugs, as long as they're not destroying things (though, theoretically, I could like a bug that destroyed some or even all the things, but that's probably a pretty far out edge case involving a fake news website of some sort. Thousands to choose from...).

I asked in a DW comm thread and was told by [staff profile] denise that turning on HTTPS Everywhere, the Dreamwidth Beta, won't conflict with keeping HTTPS Everywhere, the browser add-on, enabled while on Dreamwidth, so apparently you'll be able to keep both running at once.

Being me, I'll try the beta both with and without the add-on (I've been using the add-on for a while and am kind of stuck on it - it's not bad as long as you don't force it to run literally "everywhere", which prevents about half the web from appearing in your browser) so I can see how it all gels.