On Sun, Mar 1, 2009 at 11:57 AM, Paul Kinlan <paul.kin...@gmail.com> wrote:
> Thanks Chad, that is what I am trying to get across, we will definitely > need to drastically alter our workflows. > > I am definitely not trying to spread FUD, the problem is there is > definitely uncertainty about the process as a whole which I would like us > all to talk about and ways to work with (around) it. Seem to me that the mindset required is to think of yourself as creating something that isn't just a new front end for Twitter, but a site that has other value. E.g., if you're Facebook, the OAuth paradigm makes perfect sense. All the extra work only seems like trouble when you're building something whose whole purpose is to be some sort of value-added Twitter interface. Speaking of extra work... I hope that everybody is starting to store user data by Twitter ID, not by user name. I've been frustrated by losing all my preferences in TweetDeck, for example, because it apparently relies on user name, not ID. When I took an underscore out of my user name, TweetDeck no longer knew who I was. This undoubtedly will confuse users who would expect their TweetDeck user name to change when when they change their user name in Twitter. Again, this is the difference between a Twitter front end and a site that has other purposes - nobody would expect their Facebook user name to change just because they changed their Twitter user name, no matter how the accounts were linked. Nick
