This week, Jen Zingsheim was joined by co-host Bryan Person for a discussion about South by Southwest (SXSW), Facebook’s new commenting system–is it “killing authenticity?”–and two corporate Twitter incidents that remind us all to pay attention when we’re broadcasting on behalf of a company.
This week’s program is 30 minutes in length.
First, Jen and Bryan talk about the upcoming South By Southwest event, in particular the interactive portion. (Film and music are awesome, but not really the raison d’etre of Media Bullseye.) Bryan is attending, and provides insight as to what might be big this year–including debates around app design, QR codes, and location-based services. Bonus! Bryan will be hosting a panel discussion on the last day of SXSW, Tuesday–discussing how brands respond to Facebook attacks.
Speaking of Facebook, next, the two discuss Facebook’s new commenting system, focusing on the question of whether it, in the words of Steve Cheney, will “kill authenticity” on the web. Paraphrasing Cheney’s argument, Facebook causes people to dilute their responses because so many different groups of people encompass one’s “friends.” Jen somewhat agrees with this notion, point out that she’s made this point previously on the Roundtable: that the exposure to multiple groups makes many share only the most “vanilla,” least offensive, updates. Bryan points out that there are options, that you can choose not to use the Facebook commenting system, or elect not to have it broadcast to your Facebook page–noting that Dave Fleet has an excellent post that examines the pros and cons of the system. (By the way, we’re giving it a test whirl here on Media Bullseye. Like it? Let us know. Loathe it? Tell us that too!)
Finally, Jen and Bryan talk about the major Twitter “oops” that befell the Chrysler brand yesterday. A Tweet using what is colloquially referred to as an “F-bomb” was posted to Twitter, coming from the official Twitter account of the car company (the Tweet allegedly originated from an employee of an agency used by Chrysler). The Tweet was quickly pulled, but it’s yet another reminder that it’s important to be mindful and careful when using Twitter. United Airlines’ corporate Twitter account also had an “oops” moment this week–a Twitter user who experienced multiple aggravations surrounding her United Flight received no response from the corporate account after multiple tweets. Until the next day, when she sarcastically thanked the airline for allowing her to catch an old episode of Fraiser–then the airline responded, with a “not funny when you look at the history here” Tweet back. Jen wonders why they didn’t at least acknowledge her initial Tweets–it’s odd to monitor and respond, but only to certain posts. Bryan points out we don’t know how United is set up, but it does seem strange to not have some system in place by this point.