I agree with much of the advice that’s given here about Twitter etiquette. Some of it more than others, but this part in particular stuck out at me as being something I disagree with quite strongly:
8. Avoid automation if possible. Scheduling tweets is tricky. It’s not the worst thing in the world, as long as the tweets still sound human and there’s someone to engage with people once the tweets are sent, but something about it just feels icky.
This is part of the same mindset that says all social media comments from customers deserve – nay, necessitate! – a response from the brand they’re directed toward. But that overlooks the reality that neither of these pieces of advice are really achievable at any sort of scale, at least not as part of a core, multi-pronged program.
See corporate publishing programs need to be fed. They need to be fed around the clock. And there’s content – blog post links, photos, videos and more – that needs to be distributed on Twitter and Facebook and elsewhere inbetween all those idyllic responses and conversations.
This sort of advice assumes that every program has a 10+ person team that can cover all aspects of publishing, with a full team on duty 24 hours a day to push out links as soon as they pop, instead of being scheduled for an optimal time and in the context of everything else that’s going on.
So I’m sorry if some people think this “feels icky” but tools that allow for scheduled publishing (and the managed ed cals where such publishing is planned) are largely necessary for any program that operates at scale.
(I realize I’m kind of picking on a fairly innocuous comment, but this sort of thinking really raises my hackles.)
And so next week we will begin rolling out Digg Reader, version 1. We’re doing the launch in phases because, as you might have guessed, RSS aggregation is a hard thing to do at scale, and we want to make sure the experience is as fast and reliable as possible. Everyone will have access by June 26th. With all this in mind, we thought now would be a good moment to come up for air and share a little bit about the product you’ll see next week, and what else we’ll be adding over the next few months.
via Digg Blog, Digg Reader Update!.
Digg’s reader is one I’m really excited about kicking the tires on. I’m pretty solidly on board with Feedly right now as my Google Reader replacement but I’m 1) Always looking for a second app to handle other reading and 2) Just super curious about what this team has in mind. I like the redesigned Digg app for mobile reading a lot – it’s a neat, quirky magazine of sorts – and so am looking forward to what this winds up looking and feeling like.
This looks interesting and I dig what Shelton is going for here. Though I have to admit the look and feel of Seattle here makes me think this is a pseudo-sequel to Singles.
I really enjoyed the first movie – including the bits that were made up for it and did not appear in the source book – and so am greatly looking forward to this second installment, though I am worried this is where the stretching of the material is going to start to become more evident.
Say what you will about this band, they write a hook like nobody’s business.
Dave Coustan reminded me today was the anniversary of the Miranda ruling, which immediately made me think of this scene.
I know I should go deeper into his catalog, but I have the Capital Years and Reprise Collection boxsets and they, in and of themselves, are fantastic. Love the early stuff as much as anyone, but this one in particular gets me moving more than anything else.