I know you're probably getting sick of me posting about Twitter the last couple of days, but bear with me. This one is warranted. —The Mgmt.
Since I've been twittering as @slice, followers have seen the account go through a couple different phases.
Phase One began as my own personal account, which made sense to me at the time—after all, there was little separation between the personal and the pizza in my world. For many of my friends, longtime readers, and Twitter followers, Slice and "Adam Kuban" were pretty much synonymous.
But a few months ago, I realized that the personal stuff I was tweeting could be misconstrued as the viewpoints of Slice the Blog—and, more worrisome, of Slice's parent site, Serious Eats.
So I broke up with my @slice account and got my own. Thus began Phase Two: Strictly pizza and Slice news.
Today I'm proposing Phase Three, which I'll explain after the jump.
If you're a follower of @slice, how would you feel about me turning it into a sort of crowd-sourced pizza intel log?
How It Would Work
Eater already does something like this. So does shakeshack. I can set up a bot that basically retweets anything from anyone who includes "@slice" in their message.
So, say, if you wanted to report on the line at Co. and get the message out to other Slice followers, you'd do something like this:
"@slice There's no line at Co. right now! Got right in."
That message would then be retweeted by the Slice twitter account, giving subscribing slicehounds on-the-go intel.
Pros and Cons
The pro would be, obviously, on-the-fly information.
The con would be that, depending on number and quality of reports, you might just end up with a weird stream of stupid pizza-related updates.
I'm not going to put this into effect until I get some feedback from @slice followers. So let me know here in the comments, by @reply or dm on Twitter, or, if you're a dinosaur, by email (adam@sliceny.com).
Personally, I'm all about Web 2.0, Crowdsourcing, Social this, etc, New media yay.
But, there is a reason I read slice: you. You are the editor, you are who I trust to source my information and anything I read here I assume to be funny / reputable / what I need to read.
I agree that the tweets from you as opposed from random...not to mention lots of crowd tweets would be much more appealing. Sorry to put this on your shoulders, but you are the 'voice' of Slice.
Why not setup @SliceReaders or @SliceIntel or, better, a local @SliceNYC and so forth (@SliceATL, @SlicePhilly, @SliceSanFran...)? The possibilities are countless, and then we can retain the integrity of the mother tweet, @Slice while her wild children run amok of the web!
Thanks for commenting! Your comment has been accepted and will appear in a moment.
Add a comment:
Previewing your comment:
HTML Hints
Some HTML is OK: <a href="URL">link</a>, <strong>strong</strong>, <em>em</em>
Comment Guidelines
Post whatever you want, just keep it pleasant. We reserve the right to delete off-topic or inflammatory comments. Learn more at our Comment Policy page.
Print
5 Comments:
Personally, I'm all about Web 2.0, Crowdsourcing, Social this, etc, New media yay.
But, there is a reason I read slice: you. You are the editor, you are who I trust to source my information and anything I read here I assume to be funny / reputable / what I need to read.
Prairie at 10:23PM on 01/15/09
The wisdom of the crowd benefits from an editor, so I'd vote for more @slice tweeting from Slice readers but no automatic/bot retweeting.
Alaina Browne at 7:58AM on 01/16/09
Sounds good.
Prairie at 9:58AM on 01/16/09
I agree that the tweets from you as opposed from random...not to mention lots of crowd tweets would be much more appealing. Sorry to put this on your shoulders, but you are the 'voice' of Slice.
AlliOK at 10:30AM on 01/16/09
Why not setup @SliceReaders or @SliceIntel or, better, a local @SliceNYC and so forth (@SliceATL, @SlicePhilly, @SliceSanFran...)? The possibilities are countless, and then we can retain the integrity of the mother tweet, @Slice while her wild children run amok of the web!
LikesToEatJunk at 10:52AM on 01/16/09