All posts tagged twitter
All posts tagged twitter
This is why:
We’ve been building something new! Come see: fly.twitter.com #letsfly
— Twitter (@twitter) December 8, 2011
Pro tip: Download the new Twitter for iPhone or Android and unlock the new Twitter on web. fly.twitter.com
— Dave Gamache (@dhg) December 8, 2011
I would like your strongest coffee served in a mug made out of your strongest coffee.
— Brian (@Truebe) December 8, 2011
(Additionally, I urge you to view this on blog.benward.me, not just on the Tumblr Dashboard if that’s your jam.)
For my money, Techcrunch is doing the best it can to be open and it’s laudable they’ve decided to only publish the “newsworthy stories.” They’re not being slimy, but they’re certainly being treated as if they are. People really like to hate Techcrunch.
I disagree with the suggestion that TechCrunch is “doing the best it can to be open”. Michael Arrington is doing exactly the same he always does. To explain that, what follows is a fairly complete explanation of how I interpret his TechCrunch operation, methods and writing style. I hope to get across why I feel it’s important to vocally call him out, oppose him and his blog, and why I’m seriously asking that people shun TechCrunch and drive their negativity out of our industry.
So, people absolutely do hate on TechCrunch. Some people actually, passionately hate Michael Arrington. At all levels of severity, Michael Arrington has earned that criticism. TechCrunch is a host for his personal attacks and vendetta, and publicity stunts, yet presented under the guise of being influential ‘Technology News’, even syndicated into The Washington Post. There is anger, certainly, but it does deserves ridicule. After years and years of egotistical behaviour and abuse of influence, I’m pleased to see more people speak out vocally when Arrington flares up. Sooner or later, I do hope that it gets through and causes TechCrunch to fail.
On the issue at hand, John Gruber has it fundamentally right: When you acquire information that you know to be stolen, there is no ethical dilemma. A decent, honest person does not publish, end of. Arrington however is not just electing to publish, but to ensure the incident translates into maximum exposure for him and TechCrunch.
As ever, a decent number of people who don’t actually read TechCrunch—myself of course included—are vocally appalled by the ethical vacuum that Michael Arrington operates in.
Arrington’s manipulation of the situation is actually not so complicated, and serves a number of very specific purposes, necessary to maximise the response to the story. This faux ethical dilemma is an important strategic prerequisite to drag the report out. It’s about both increasing the drama of the incident and getting certain groups of people playing off each other. Of course, it’s completely insincere.
The stolen documents are apparently going to be made public by the person that stole them, but they provided them to TechCrunch early, as some sort of exclusive to break the story. It’s very important for TechCrunch to capitalise on getting first access and move the story on so that it’s no-longer reported as ‘documents were stolen from Twitter’, but as ‘documents were leaked to TechCrunch’.
By putting themselves at the centre, this becomes story about TechCrunch, too. So having said that all of the stolen documents are going to be available from another source, TechCrunch have implied their selectivity in reporting makes a difference to the story. It doesn’t.
As stated above, publishing any document that you fully know to be stolen crosses an ethical line. Deriving a story from a stolen document that is kept private is a bit grey. So by adding a tale of personal dilemma Arrington adopts a false air of decency to deflect from the crux, that is publishing any of this is repulsively indecent. He highlights that some ‘embarrassing’ content will be graciously withheld. The reporter that ambled eagerly over the ethical boundary is operating a separate, entirely irrelevant ethics microcosm on the other side.
These few self-indulgent paragraphs about how considered and responsible Michael Arrington is being with these stolen documents provides fuel for an import half of the active TechCrunch community: Fanboys. Fanboys are those who blindly follow Arrington’s lead and ego. He’s famous, and maybe on the internet act under the illusion that you can be close to the famous by participating in their presence. He’s a good, manipulative writer, too, and for those who buy into his style they rally around his humour and baiting. Sometimes, they’re just struggling businessmen desperate to pimp their start-up.
In the comments pages, Fanboys jump on Michael’s self-professed demonstration of ethical decency with complements and applause. In doing so they provide important pivots for follow-up posturing, and citable support for continuing the stories. More importantly, their supportive contributions dilute the torrent of abuse that will inevitably be posted by TechCrunch’s other faction; trolls.
Trolls are self-explanatory and exist in all communities. TechCrunch hosts a concentrated, especially bitter kind of troll, though, stemming from the attitude and style of the TechCrunch blog itself; TechCrunch is itself a troll, and you reap what you sow.
Stories like these, the Last.FM saga, and the personal attacks on Blaine Cook are all based on abuse, negativity and scandal. These are the only kinds of story that get TechCrunch special attention. The people that involve themselves in the TechCrunch community are those that respond to this abuse and negativity. It’s no surprise then that they dish it out themselves. Some are trolling back in disgust, others hope to imitate the cutting cruelty of Arrington’s own writing. None of them really care whether they’re trolling with TechCrunch, or at TechCrunch. It’s just an exercise in juvenile bullying.
Michael Arrington’s talent as a writer is that of manipulation. His cynical passages in this story and others exist to distract from contentious, amoral aspects of his reporting, and to associate himself and his brand with a breaking story.
In the Last.FM coverage vast passages of text and a completely meaningless email screenshot were used to disguise that they had no real evidence. In the instance of Twitter’s stolen documents, he’s posturing to make the subsequent publication of some stolen material seem acceptable on the grounds that it isn’t the publication of some other stolen material.
It’s a bit intricate, but it’s not about being open or honest. Arrington is supremely good at what he does and at playing his community on the big stories. I happen to find what he does vile.
An open door at TechCrunch leads only to a hall of mirrors.
The reason you’re giving up and using tables is not because it is easier. It is because you don’t know CSS. Hmph.
There is no ‘CSS vs. Tables’ debate. What’s going on is this: CSS evangelism happened. It went as far as it could in that form. It educated an entire generation of developers. It helped the profession of web development become truly professional. It opened peoples eyes to the power of a the web beyond visuals and propelled them to value accessibility, interoperability, semantics, microformats and much more that makes the web rich.
That CSS evangelism ceased. It’s ceased because everyone who’s going to get it, has got it; learned it; knows it. Other audiences need different kinds of education. That leaves a vacuum. A vacuum free of that passion, expertise and talent that drove initial CSS adoption. On the internet, vacuums get filled with noise. Noise from the cynics, also-rans and can’t-be-arseds of the web. People like 37signals, with a habit of ignoring well qualified advice in favour of link-bait posturing. People who are simply missing the skills they need to do this job, but who spy an opportunity to rebel against education, rather than seek out new knowledge. They preach that the world is flat, because they haven’t yet travelled around it.
There is no resurgence in ‘table based design’. All we’re hearing are the unsupressed wails of those those left behind, because everybody else moved on.
I’m afraid if I add a post to twitter feature on my side project !adactio / @adactio will freak out because I NEED to ask for a password. — Leah Culver
The ideological route is to reject Twitter for not providing a suitable API.
Alternatively, could you leave password authentication out altogether and leave it to the browser to prompt users for the username and password when the API gets called? I think I’ve seen HTTP authentication prompts come from Twitter in the past (Natimon’s Twitter http://tweetersation.com/ does when you try to view a protected stream, I think). At least that way people can choose to use the ‘Remember This Password’ feature of their browser, rather than it being stored unencrypted on your server.
Or, just have a ‘Post to Pownce’ button instead…
In response to Jeremy Keith on Pownce:
Here’s a textbook example of why the password anti-pattern is so dodgy. Because we’ve all been taught that it’s okay to hand over passwords for third-party sites, a service called MyNameIsE feels that is perfectly acceptable to use that sensitive information to post a Twitter message from your account!
If you’re one of the people who signed up to this service, I’d love to hear how you felt when you saw this message (ostensibly from you) show up on Twitter.
I know I was ragging on Pownce for still using the password anti- pattern in parts of the “find friends” feature but man, they would never do anything like this!
You’re mostly correct, although I think you put the emphasis of this argument in the wrong place.
Even if Twitter used OAuth, a service you link would still be able to nefariously post spam to your account. The vital difference, and the part that should be emphasised, is not that they’re prevented from doing it, it’s that you’re able to revoke their ability to do it, without changing your password, and without having to update your other third party applications.
Cyril Doussin posted on Pownce:
I am increasingly frustrated by Twitter’s 140 character limit. It rarely let’s me fully express what I’d like to say. Not that I want to write Bible-like comments, but a couple more sentences would be great sometimes.
So it’s probably time to start using Pownce more frequently, for these personal, not blog article worthy, thoughts.
Link has been added to the bookmark toolbar, iPhone app is installed, let’s see where this takes us over the next few weeks…
http://ben-ward.co.uk/journal/snippets/
— I had a similar thought about Pownce. Though I come at it from the other side. My problem is that my blog has become a place more for longer articles and I don’t want short snippets of ideas end up there.
I pondered getting working on my Tumblr account, but that fell down pretty quick when I realised Pownce has everything Tumblr has, but better, and with social integration and desktop/iPhone tools. For me, it’s much easier to post to Pownce. And whilst I still feel that OEmbed should have built on Atom rather than invent a new vocabulary from scratch, it’s used to excellent effect in posts too.
Which is to say, it’s taken me ages, but I’ve figured out what Pownce is for. ‘Share stuff with your friends’ isn’t the best tagline for it, but really it’s right there at the birth of micro-blogging, which turns out to be a really good idea.