The utility of various use cases has to be balanced with the overall Twitter experience that affects every Twitter user. I'd guess that the product team is generally going to bias away from exposing unfollows to the population at large, while not restricting unfollow discovery from motivated parties. Also, the product team will, just as in any company, always bias towards building features that affect the population at large. So, these features fall into the null intersection of these two disjoint sets. Given competing priorities, little is likely to be done here unless there was a huge efficiency gain to be had somewhere...
-John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 23, 2010 at 8:39 AM, Orian Marx (@orian) <or...@orianmarx.com> wrote: > Being able to retrieve a list of unfollows a user performed since some > point in time would be hugely valuable for anyone trying to maintain > an up-to-date record of a user's connections without regularly having > to refetch all the ids. Is there any way this could be accomplished, > perhaps as a REST endpoint? > > On Apr 21, 5:00 pm, Mark McBride <mmcbr...@twitter.com> wrote: >> We likely won't send down the unfollows in the short term, for reasons >> outlined previously. It's not that we won't *ever* do it, but it's >> delicate. >> >> On the user profile changes, that does seem like a good idea. No >> promises, but I'll look at what we can do. The highest priorities we >> have right now are >> >> 1) Getting the formatting of messages locked down >> 2) Getting list activity in (lists created/deleted/modified, users >> added to lists, etc.) >> >> ---Mark >> >> http://twitter.com/mccv >> >> >> >> On Wed, Apr 21, 2010 at 1:30 PM, Cameron Kaiser <spec...@floodgap.com> wrote: >> >> Also, unfollows should be treated the same as follows. I know its sad >> >> when an unfollow happens, but this is important information too. >> >> > I disagree. I think unfollows should be totally without penalty, and making >> > them visible/exposed could depending on the situation assign them a very >> > heavy social penalty. Qwitter comes to mind. >> >> > -- >> > ------------------------------------ >> > personal:http://www.cameronkaiser.com/-- >> > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com >> > -- "EH! STEVE!" >> > --------------------------------------------------------------- >> >> > -- >> > Subscription >> > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
