Tag: Twitter

Posted on
by

I’ve been having trouble trying to find a good Twitter app for my Android phone.

Actually, that’s not entirely true. I’m extremely happy with Twidroid, which I’ve been using since I got the phone. The problem is that I need a good second app, because I have two accounts I want to use. Update: This is no longer a problem (see end).

I ♥ Twidroid

I keep going back to Twidroid for two main reasons:

  • It lets me do everything I want to do with Twitter on my phone.
  • It makes the most common tasks as streamlined as possible.

That second item is really the key. Most other Twitter apps I’ve tried tend to get in the way. Want to post something new? Hit the menu button, then choose an item from a pop-up toolbar. Want to open a link? Press and hold, then select from a big long menu.

With Twidroid, buttons for posting a new tweet, showing replies, posting/viewing direct messages, and refreshing the view are right there at the bottom of the screen. One tap and you’re posting. One tap and you’re pulling in new messages. One tap and you’re looking at replies. And you open links by tapping a message, not pressing and holding.

It’s like the “easy button” from the Staples commercials.

Twidroid also ties in to the Android OS, making it easy to share a link directly from the browser, or share a photo directly from the image gallery.

Another nice feature is that it can break down background notifications by category. If I want it to check for replies and direct messages and sound an alert, but not worry about general posts until I look, I can tell it to do so.

I Tweet

I Tweet ($2.99) is very close, and I’ve been using it as my secondary app for several months. It ties into the OS, does photo uploads and URL shortening, lets me customize notifications, etc… but it has a tendency to get in the way. The user interface is pretty, but cluttered. The things I want to do most often require multiple taps (or worse, press-and-hold, like opening a link).

The worst part is that if I don’t let it check periodically for new messages, I can’t tell it to pull in new ones when I launch it… and it won’t always retrieve older posts. If I post something before hitting refresh (which is hidden behind the menu button), it won’t pull in anything further back than the post I just made.

Trial and Error

At this point, I’ve got my personal account @KelsonV set up on Twidroid. That’s the one I have linked to this blog and to Facebook. I’ve got @SpeedForceOrg running on I Tweet. I’ve been using it a lot lately with the lead-up to Comic-Con International, and those few problems have started really bothering me.

So I tried a bunch of others this weekend.

  • Twitli – I used this one for a while a few months ago, but it was kind of buggy. The last straw came when I was trying to upload a photo during WonderCon, and I switched the account to Twidroid for the duration of the con. I only gave it a glance this time around.
  • Loquacious – nice w/ multiple accounts & photo integration, but incomplete. No notifications, can’t share a link from browser — heck, no settings at all other than login+password and filters. Either that or the demo is crippleware in addition to being time-limited. Also, suffers from press-n-hold syndrome like I Tweet.
  • Twitta – too basic.
  • Twit2go – Photo uploads worked decently, and it was able to do notifications the way I wanted, but it didn’t hook into the OS as well as Twidroid or I Tweet. And it was yet another case of press-and-hold to open a menu that includes opening links. I decided to stick with it for a few days, though, and was pleasantly surprised to see that it did pull new messages automatically when opened, so I wouldn’t have to worry about missing anything. Gave up on it when I tried to retweet a post that ended up being too long, and rather than let me edit it down to size it just cut off the end…which happened to be the link.

So I’m back to Twidroid and I Tweet for now. I’ll probably end up swapping the accounts again and putting SpeedForceOrg on Twidroid, since that’s the one I’m likely to be using most during the con. *sigh* Why do I have to make things more complicated for myself than they have to be?

Update: A few months after I wrote this, Twidroid released Twidroid Pro, which adds several features on top of the free version…including multiple accounts!

Posted on
by

It’s a trending topic, but there’s a lot of misunderstanding about the Twitpocalypse. Here’s what’s going on, in layman’s terms (I hope).

What’s happening?

  1. Every Twitter post has an ID number that goes up by 1 each time.
  2. When a computer program stores a number, it sets aside a certain amount of space for it. Bigger numbers take more space because they have more digits.
  3. One common format is called a “signed integer.” It has 32 binary digits (1 or 0 only) with one digit set aside to indicate a minus sign. The biggest number it can store is 2,147,483,647.
  4. Twitter’s status IDs are approaching that number.

So what’s the likely impact?

  • Twitter itself can handle bigger numbers and will be fine.
  • Third-party apps that store the ID in a bigger format will be fine.
  • Third-party apps that store the ID as text instead of a number will be fine.
  • Third-party apps that store the ID in this particular format will end up with bad IDs as they try to cram a big number into a small space.

If I were to guess, the most likely breakage would be that replies might be attached to the wrong previous post — but again, only with apps that use this particular format for numbers.

Twitter itself will probably sail through cleanly (and has been planning to move up the schedule so that affected app developers don’t have to fix things in the middle of the night), so don’t expect any fail whales. Unless so many clients have problems that lots of people switch to the website.

Update: Not surprisingly, most Twitter clients are unaffected by the Twitpocalypse. I’ve used both Twidroid and Twhirl with no problems since Twitter passed the mark. I figured a few would get tripped up, but the real surprise is that it hit Twitterrific. One of the most popular clients on the iPhone? They do have an update, but a lot of people are unable to connect.

Posted on
by

Forget Ashton Kutcher and Oprah, forget #unfollowfriday, forget 25 Random Evil Things about Twitter — the key problems with the social media / microblogging / broadcast IM / whatever you want to call it service boil down to two problems:

  1. It asks the wrong question
  2. It was designed around limitations of cell phone text messaging

The Wrong Question

Twitter’s prompt is not something general like “What’s on your mind?” It’s “What are you doing?” That encourages people to post things like “I’m eating lunch” or “Just got into work,” or “Posting on Twitter.” Presumably what they mean is “What are you doing that you think people would find interesting?” but of course that’s too long a prompt from a usability standpoint.

The thing is, there’s no reason to broadcast the mundane to the world. Don’t tell me “I’m eating soup.” Tell me, “Just learned that gazpacho soup is best served cold. I wonder if they eat it in space?”

Unfortunately, that means the signal-to-noise ratio can get pretty bad at times.

Outgrowing its Limitations

Twitter posts are limited to 140 characters of plain text so that the your name and comments can fit in a standard SMS message. Now, this is great if you use Twitter via text messages on your mobile phone. It’s not so great if you use Twitter on the web, or through a smartphone app like Twitterific on iPhone or Twidroid on Android, or through any of the zillions of desktop apps.

I don’t have a problem with the 140-character limit itself (it can actually be liberating in a way), though it would be nice to have some formatting options beyond all-caps and *asterisk bolding*.

The real problem is that links have to share that limit. URL-shortening services have exploded lately as people try to squeeze links into the tiniest space possible to save room for their precious text. Even if you use something as short as is.gd, just including one link means you’re down to 122 characters.

Plus URL shorteners come with a host of problems, in particular the fact that they hide the destination. That’s no big deal if the target matches the description, or if it’s a harmless prank like a Rick Roll, but it’s all too easy to disguise something malicious.

Seriously, if you got an email that said something like this:

Look at this! http://example.com/asdjh

Would you click on that link? Even if it appeared to be from someone you know? That’s just asking to get your computer infected by a virus, trojan horse or other piece of malware. Or to see something you wish you could unsee.

Better Link Sharing: Facebook

I hesitate to bring up Facebook as a good example of anything, and I know the current layout is largely reviled by its users, but they really got posting links right.

When you want to post a link to your Facebook profile, you paste in the full URL. Facebook reads the page and extracts the title, a short summary, and possible thumbnail images. Then you have the normal amount of space to write your comment. Continue reading →

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.