Tag: blogging

Posted on
by

I’ve deleted redundant or trivial items, split some digests by topic, tagged, categorized and titled the rest, fixed typos and expanded abbreviations, reformatted quotes, links and lists, imported photos, and more…all in an attempt to make the archive a little more useful.

After trying to unify some of the more eclectic mixes of unrelated one-line remarks and links, I’ve decided it’s time to stop automatically importing “tweets” to the blog. Sure, the digests maintain quantity, but I think it’ll be better to keep the quality up instead. What makes a good status update doesn’t always make a good blog entry, and I’d frequently find myself either staying up late to edit that day’s “Line Items” post or rewriting it the following day. (Plus I was always worried about a bug in Twitter Tools that would cause a duplicate post about 30-50% of the time.)

I think the blog will be better off if I copy, expand or skip stuff from Twitter at my own pace and put it in a more suitable format to begin with.

Posted on
by

I use the Broken Link Checker plugin on this blog and on Speed Force to find broken or moved links. In addition to helping you manage them in the admin interface, it can also assign formatting (as a CSS class) to mark them in your posts.

Cool! Readers can see that the link is broken before clicking on it!

But what’s the best way to label the links?

The plugin uses strike-through by default. You are marking something that’s gone, but strike-through usually means the text is being crossed out. That’s fine for a link in a list, but something like “Catering was provided by MyNiftyFoodCo” implies that the name of the company is wrong, not that the website is gone.

Just making something italic or changing the color doesn’t work either, because it’s arbitrary. Nothing about an italic link (which could be a title), or a random other color, suggests that something might be missing.

What I’ve come up with is to reduce the contrast on broken links. It combines two familiar schemes:

  • High contrast for new links and low contrast for visited links.
  • “Graying out” inactive items in software.

So here, I’ve got bright blue for new links, darker blue for visited links, and broken links as black (well, very dark gray), the same color as surrounding text. I’m keeping the underline in place so there’s still some indication that it’s a link, but it’s not as strong as the label for one that’s still functional.

It’s still not ideal, since color is the only difference, but it should cause less confusion than the strike-through.

Posted on
by

At this point, the only (useful) official word from Amazon as to why thousands of books with LGBT themes disappeared from search results over the weekend is the “embarrassing and ham-fisted cataloging error” statement sent to Seattle Post-Intelligencer and other sources, also mentioning a number of other categories impacted. This article also has the unconfirmed word from former Amazon employee Mike Daisey that it was a matter of user error where someone mixed up some tags while working on the site, and the change just propagated globally.

Before Amazon finally spoke, tehdely posted an interesting theory that it might be might be astroturfing or a Bantown-style troll, deliberately pitting Amazon against the LGBT community to watch them fight each other for the lulz. A writer at Feministing asked her editor to call up Amazon and was told that it was not a glitch, but an automatic policy to hide “offensive” search results. Patrick Neilsen Hayden attributed it to bureaucratic incompetence.*

Now, some thoughts:

1. If this was intentional, on anyone’s part, it was both wrong (as discrimination) and stupid (as bad PR and as throwing away potential sales). If it was unintentional, it was still stupid.

2. Amazon really dropped the ball on PR. They should have responded much sooner (yes, it was a holiday weekend), and with something more detailed than “It was a glitch.” Something like, “We’re sorry, it was an unintentional error and we’re trying to fix it” would have gone a long way toward preventing the outrage from spiraling out of control. And we still don’t have anything more detailed than “ham-fisted cataloging error,” or (as has been pointed out) an apology to the authors and communities affected.

2a. And seriously, you’re an internet pioneer: use the Internet. You have email, you have official Twitter accounts, you have a space to put messages on your home page. Use them.

3. Twitter demonstrates that the internet is now fast enough and ubiquitous enough that people can develop a mob mentality without actually being in close proximity to one another. This includes not just people whipping each other into a frenzy, but people taking more permanent actions (deleting accounts) based on incomplete information.

4. No matter how many times something has been debunked (i.e. the “hacker” who claimed to have hacked the site), someone will see it who hasn’t seen the response and repost it as true. (You’d think I would have learned this from comics discussion forums by now.)

5. Canned responses from customer service are not authoritative statements of company policy. Half the time they’re not even answering the question you asked.

6. There are really two issues: (A) Adults-only books are being hidden from search results. (B) LGBT books were being misclassified as adults-only.

7. Combining #5 and #6, when a CSR monkey answers A, that’s not an official statement of policy on B.

8. Removing adults-only books from sales rankings is a dumb way to hide them from search results. Add a flag and let the user choose whether or not to include them like Google, Flickr, etc.

*The second-paragraph links were originally in a separate post, in the form of a collection of tweets. I’ve since combined the two into a single post.

Posted on
by

It looks like the campaign to reclaim BlogExplosion is working! The efforts to bury the forum spam have brought new members into the site, and earlier this week a new administrator appeared on the forums, banning over 55 accounts used by spammers and deleting 13,000 spam posts. This morning, the banner approval I’ve been waiting for since August finally went through.

Things are looking up!