There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.
Not sure whether to file this under FUD, but the error isn't nearly as sensational as the title or summary seem to indicate. Certainly an issue if it turns out that presses are being fuzzed out to different locations than intended, but very possibly an issue of "fat fingers" on the part of customers. Either way, the Android team should take a look at it and either fix the touch firmware or increase the size individual entries in the notifications screen (make it adjustable?) to prevent miss-taps. The summary definitely makes it seem that the text subsystem is just shooting them to random contacts without the user knowing which is far from what's actually happening.
In the Iranian case, meanwhile, the people tweeting about the demonstrations were almost all in the West. "It is time to get Twitter's role in the events in Iran right," Golnaz Esfandiari wrote, this past summer, in Foreign Policy. "Simply put: There was no Twitter Revolution inside Iran." The cadre of prominent bloggers, like Andrew Sullivan, who championed the role of social media in Iran, Esfandiari continued, misunderstood the situation. "Western journalists who couldn't reach--or didn't bother reaching?--people on the ground in Iran simply scrolled through the English-language tweets post with tag #iranelection," she wrote. "Through it all, no one seemed to wonder why people trying to coordinate protests in Iran would be writing in any language other than Farsi."
HELP!!!! I'm being held prisoner in /usr/games/lib!
