Commence Archives

Geekmum.com {Movable Cafe} blog is retiring and shall henceforth be solely an archival site. I had fun tweaking and hacking Movable Type back in the day, but much of the content here is deprecated now due to extensive and ongoing feature improvements in MT. (As it should be!) Some content might still be found useful, thus the archives. Completely obsolete content has been removed and commenting is disabled globally. Questions may be directed via email to kate at this domain.

Thank you to my enthusiastic readership (all three of you! {wink}) for the last 7+ years of MT fun and encouragement.

Kate
Movable Cafe {Movable Type Tricks, Tips, Tweaks and Hacks}

The Tweet Heard Round the World

| 4 Comments

Or... Never Underestimate the Backlash of a "Small Settings Update"

Yesterday Twitter made an unexpected, unwelcome and vastly unappreciated change to the way "@reply" tweets are delivered to users. Until yesterday, I could view my Twitter friends' replies to users we don't mutually follow. Until yesterday, I could turn that feature option on or off in my user settings. Today, however, I have no choice in the matter. Twitter killed the option, calling it "undesirable and confusing".

I find their reasoning curious, since (if I remember correctly) the user settings had this feature turned off by default. For those Twitter users who turned the option on, it was desirable and useful, and made perfect sense. Twitter has shot themselves, along with their claim to value the "importance of discovery", in the foot.

In a "real life" scenario, it would be like going to my favorite cafe for a meetup with a common-interest group, some folks with whom I am acquainted and others with whom I am not. Throughout the conversations are dead spots... any time someone I know replies to someone I don't know I find myself unable to hear my friend speak. I would love to get to know the friends of my friends, but I am not allowed to hear their conversations. Now that is what I would consider "undesirable and confusing"!

Many Twitter users have already discovered and implemented a (kludgy, but do-able) workaround by prepending a single character to the @reply in their tweets. This will work to allow @reply tweets to be seen by all friends, but the loss now will be for the users who once disabled @replies to non-friends. They will have to choose between enduring these tweets or unfollowing their friends. Not only that, these @replies will truly be "one-sided fragments" because there will be no refering link to the original tweet. Nobody wins.

The Value of Discovery

The ability to discover new Twitter users to follow is, for me, among the most highly valued Twitter features. Seeing my Twitter friends' interesting replies to users I have not yet met allows me the option of learning more about those users and potentially making new connections. This method of discovery has afforded me some wonderful Twitter friends and contacts I would surely have never met otherwise. The result is a richer community experience.

I am extremely disappointed in the decision of the Twitter powers that be to make this change without, it would seem, becoming better informed as to the potential impact on its users. Not only did they act in a short-sighted way, they acted with presumption that they know better than their users what their users want. I only hope they will hear and honor the many users who have made Twitter the great social media community that it is and return this feature quickly until they are ready to implement a better alternative that serves everyone.

Related Twitter Searches: #fixreplies #twitterfail

[Twitter Responds: Whoa, Feedback! / We Learned A Lot]

Update: Thank you, Twitter Team, for hearing your users' feedback. Even so, I would have liked to see you kick the integrity up a notch by foregoing the CYA campaign and just being transparent from the start. While I am not completely thrilled with your interim solution, I am grateful for it and looking forward to your promised feature improvements which will hopefully satisfy everyone.

Pink for October 2008

| 1 Comment

I thank God that my mom is a breast cancer survivor. In honor of her and so many other women (and men) who have experienced breast cancer, I've gone Pink for October!!

Please visit PinkforOctober.org, American Cancer Society, Susan G Komen for the Cure, or other sites to learn about breast cancer symptoms, early detection, and treatments. AND please consider a donation to a reputable organization to support much needed breast cancer research!

Twitter Search Command for Ubiquity

Ubiquity is an amazing and extremely useful command line tool/UI for Firefox, currently in alpha. Since it didn't come packaged with a command to search Twitter and I couldn't find one elsewhere, I tweaked a simple command together that does the job... "twittersearch". You can copy the code below and add it to Ubiquity's command editor yourself (and have it instantly usable) or you can subscribe directly to the command on my Ubiquity page (subscribing will require FF restart). If you haven't tried Ubiquity for Firefox, check it out at Mozilla Labs. No need for me to blog about it; enough is already being said here, there and everywhere.

As always, your mileage may vary, use at your own risk, the usual suspects. Enjoy!

makeSearchCommand({
  name: "twittersearch",
  url: "http://search.twitter.com/search?q={QUERY}",
  icon: "http://assets3.twitter.com/images/favicon.ico",
  description: "Searches <a href=\"http://search.twitter.com\">Twitter</a> for tweets matching your words.",
  preview: function(pBlock, directObj) {
    if (directObj.text)
      pBlock.innerHtml = "Searches Twitter for " + directObj.text;
    else
      pBlock.innerHTML = "Searches Twitter for tweets matching yourwords.";
  }
});

Recent Comments

  • Kate: testing comments and db status read more
  • binaryblues: testing via google auth (google connect?) read more
  • pixelicious: testing from twitter again read more
  • kate ingram: testing TwitterCommenter plugin... sign in is returning errors but it read more
  • pelf: Thank you for going pink in support of the Breast read more
  • Kate: testing comments in 4.2 read more
  • G Oliveira: Hi there. I just updated MT 4 and was looking read more
  • Kate: Movable Type also created a comment for me as well read more
  • katherine: testing comment speed, which pretty much sux read more
  • Matt Moore: I did, in fact, have the same problem with MTSimpleCommentCount read more

Pages

Powered by Movable Type 5.01