Category Archives: Blog Administration

Temporarily Or Permanently, I’ve Moved…

… to my old Blogger blog. But rather than bookmarking it directly, you should bookmark the following link:

http://www.yellowdoggereldemocrat.org/

That’s a forwarding address that will take you to wherever I’m blogging at the moment. Create a link in your browser and paste that URL into it directly, and I promise you you can forget about the actual site address for a long time. If I stay on Blogger, that link will take you there. If I move back to WordPress, that link will take you here. If you blogroll me, please use this forwarding address, not the one your browser shows, in your blogroll.

Don’t bother commenting on this WordPress blog, even if you manage to sneak one past the filter. New posts and new comments go on the Blogger blog until further notice.

This whole experience has been a royal PITA which I hope to spare you all in the future.

UPDATE: I logged out of WordPress to test behavior on an “ordinary” (non-owner) user, and afterward, for a good 10 minutes or more, any attempt to log in resulted in a socket disconnect. WordPress itself was not down; I checked. I don’t know what’s going on, but it’s not looking good for the “home team.” As mentioned above, there’s a link which goes to the blog I’m using at the moment; please save it and use it.

Please Use The Same Site Name As This One…

… but substitute “blogspot” for “wordpress” in the URL. I have an interesting story to tell you, but I need to do it there, not here. Hell, I might even have to ROT13 it… nah. It’s not raunchy enough for that. Oh, and you might want to bookmark the other site, just in case…

NYT Unclear On The Concept

They got me. I just clicked a link from Paul Krugman’s blog to his column today, and was informed that the allowed count of free articles read per month has been reduced from 20 to 10. OK; it’s their “newspaper.”

But I would have thought an organ like the NYT (you may decide for yourself which organ it is) would want EVERYONE to read its opinion columns for free, all the time, to obtain maximum influence in the marketplace of ideas.

I vaguely remember that links from a blog are supposed to fly through with no interference, so here’s a link to the Krugman article I was trying to reach. I’ll update you with the result.

UPDATE: yep… slick as cat-poop on the floor outside the litter box! So… NYT doesn’t want bloggers to read its op-eds, only to link them. Riiiight…

A Minor Blogospheric Complaint

There’s a blog on my blogroll that I rarely visit. Why? Because it displays, repeatedly, the following notice:

PLEASE SUPPORT
XXXXXX XXX XXXXX
BY REMOVING
AD BLOCKING ON OUR SITE

Short answer: NO.

I understand why creators of large blogs may resort to ads to recover their costs. But on two occasions I have visited major, big-name blogs on which ads have attempted to install a virus on my computer. One of those two attempts succeeded.

On a lesser level, for a while, there was a car ad on another major, big-name blog which began an audio track as soon as the page was loaded, in defiance of any Mute status I may have set.

I am aware that WordPress inserts occasional frequent ads in my blog, apparently always on an individual post page, a practice with which I am unhappy, but have no choice but to accept if I use their services. So far, no one has complained of any invasive behavior on the part of those ads. I never see them unless I visit while logged off. Please be clear: that is WordPress’s doing, on all its non-premium WordPress-hosted blogs.

But I have no stock in your viewing those ads. If you want to use AdBlock or something similar, go for it. The aforementioned site that puts up whining notices about blocking of its ads can just do something unnatural with a corkscrew as far as I’m concerned. Actually, they can simply refuse to serve a client who has ads blocked. I’m fine with that; I’ll just remove them from my blogroll. But suggesting that I have an obligation to view their ads is just over the top.

‘You’ll Wonder Where The Yellow Went…’

Truly ancient Americans among you will remember the referenced Pepsodent toothpaste commercial. The rest of you will join me in wondering where the yellow went… the yellow background on this blog. It just disappeared… I didn’t do anything to make it go away. Blame WordPress… the free blogging service, and worth the price!

UPDATE 2:37pm: Ah, yellow, thou hast returned!

My Mission As A Blogger, Validated

For the past three days, I know I must be doing something right: more than half the comments left here (and promptly deleted, usually after reading no more than five words or so) were from right-wing trolls.

So if you’re a potential troll, and you want to encourage me to keep doing what I’ve been doing, which is actively soliciting votes in November to send your kind into a much-deserved oblivion… go ahead, motherfucker; make my day!

Monday Morning Doc Appointment

It’s routine: it’s been several months since I’ve been in, and a cripple like me really does need regular checkups. My PCP is a reasonable man… no BS, no excess, but thorough on the things that count. Even though he’s a nice guy, I can’t say I really look forward to any doc visit…

Look for posts Monday, late afternoon or early evening.

A Heartfelt Plea To WordPress.com

Gentlefolk,

Would you PLEASE, PLEASE STOP FUCKING WITH THE POST EDITOR? It seems as if you are determined to wreak havoc on those of us who switch back and forth between Visual mode and HTML mode.

This morning, for example, you implemented paragraphs as two line breaks, as you have done for ages.

This afternoon, you started using <p>…</p> tags… and you wrapped the whole post into one huge mass with few if any line breaks to guide the eye of the person editing the HTML.

And now you seem to be back to two line breaks.

Just STOP IT ALREADY!

Frustratedly yours,
Steve

Ah, Sweet Mister ‘‑’ Of Life, At Last I’ve Found You!

Yes, Virginia, there IS a non-breaking hyphen, Unicode U+2011, or (in an HTML document)

&‍#x2011;

Unlike an ordinary hyphen, this one will not allow a browser-inserted line break immediately following it. This is easier with non-breaking spaces; you just use the entity name

&nbsp;

in your HTML document, and the browser inserts it for you. But with hyphens, to prevent an untimely line break, you have to use the non-breaking hyphen character. There’s apparently no easy entity name for it; use the code above directly in the HTML, or copy-paste it as described below.

If you forget its Unicode character number, or if you’re not fond of messing with HTML, you can search your character map for “NON-BREAKING HYPHEN” and copy-paste what it finds. I have tested the resulting character in the current Firefox and Google Chrome browsers; it works in both.

Why, oh why is this not universally known? I’ve been looking for such a thing for several years, and only today did Google search turn up something useful.

ASIDE: if you try to copy and paste the code for the non-breaking hyphen above near the top of the post, you will find that when you paste it, it may or may not work, depending on the editor you’re working in… e.g., Linux folks will find it does not work in gedit, but works in the WordPress editor. That’s because there’s an additional invisible character in the above example between the & and the # known as a “zero-width joiner.” I had to insert it to overcome WordPress’s insistence on interpreting the ampersand‑”amp”‑semicolon as a literal ampersand in that context only. I do not know why it does that; I do not believe it is correct… but I had to insert the zero-width joiner to get WordPress to display the code properly. Your best bet is to type the code manually:

ampersand‑#‑x‑2011‑semicolon.

Be sure the ‘x’ is lower case.

Or just use the Character Map (same name in Windows and Linux) and forget about HTML.

Inconstant Comments

WordPress.com comments are behaving badly. L’Enfant de la Haute Mer had the first problem with a comment that duplicated itself. Many hours later, I just had the same problem in replying to one of c’s comments. I don’t know what they’re tinkering with, but if you wait a while, things will probably settle down… into a reliably broken state. 😈