As I mentioned on Twitter: only 3% of users had opted to see replies to
users they weren't following. Given that this setting was putting the hurt
on our servers, we decided to remove it in the interest of a faster, more
reliable Twitter experience for the vast majority of users. We have,
however, heard the feedback.

We have a conversation underway internally about bringing back this feature.
My impression is that if it's technically feasible to do so, we'll take the
user feedback we've received under consideration and bring it back. If it's
not, we'll try to deliver an experience that's similar but supportable in
the long term.
We're aware of this issue and the arguments involved. As this discussion
isn't directly related to the API, let's move on. Thanks.

On Wed, May 13, 2009 at 12:31, Kee Hinckley <[email protected]> wrote:

>
> On May 13, 2009, at 2:50 AM, voorwiel wrote:
>
>> Yeah, lots of protest out there, just watch the 'Links to this post:'
>> below the Twitter blog post. There also is a hashtag to protest
>> against this decision: #fixreplies . It is already in the 'Trending
>> Topics' sidebar.
>>
>> Let's see how this evolves...
>>
>
> I'm happy to say that I created that hashtag.
>
> @biz has posted and claimed that the reason for this change has to do with
> the underlying system architecture, which wasn't going to support viewing
> replies to unfollowed people much longer. (Personally, my mind boggles at
> that, filtering replies by a dynamically changing list of people is *easier*
> than not filtering them at all? Whatever.) Clearly this is a side effect of
> an architecture change in the past, since originally "@foo" didn't mean
> anything at all to the database. So somebody made an architecture decision
> sometime ago without considering the social ramifications. That sucks. My
> recommendation is to back the change out real quick to mollify folks, and
> then have an emergency meeting about how you're going to fix the
> architecture before whatever you did wrong breaks it--because you just took
> the viral out of Twitter. (And worse, made #followfriday a permanent
> fixture!)
>
> How major a change is this?
>
> Well, I wouldn't have my current job, house or girlfriend without being
> able to see other people's replies. I wouldn't have hired my virtual admin,
> or had a vacation this summer in Florida. I have two sets of friends who
> wouldn't be engaged without that feature. There are high-level analysts
> following me because I interjected something useful into a conversation they
> were having with a client--that wouldn't have happened. There are people I
> don't know, whose problems I solved because I saw a friend talking with
> them--that wouldn't have happened.
>
> On May 13, 2009, at 3:08 AM, Doug Williams wrote:
>
>> Secondly, where is the entrepreneurial spirit to turn this into an
>> opportunity? For the users of this option, think about the ways having
>> @replies to strangers in your timeline helped you find people. How can you
>> use the API make similar connections? The data is still there, present it in
>> a compelling way. I'd use a service that sent an occasional email digest
>> like: "The following 3 users were mentioned at least X number of times by
>> the people you follow, check 'em out".
>>
>
> Somewhere along the line, Twitter appears to have fallen for the "add
> 10,000 followers in one month" crap. This isn't about how many people you
> can follow. This isn't some grade school popularity competition. This is
> about conversations. It's about listening to people talk to each other,
> learning who you like, who you don't. It's about learning new things and
> helping other people. There *is* no replacement for this feature that will
> provide the same functionality, or even *close* to the functionality. This
> isn't an opportunity for a third-party to use the API, this is an
> opportunity for Google to eat your lunch.
>
> Were lots of people using the feature? I have no idea. Certainly your core
> early adopters were. Certainly the social media folks (who write most of
> your press) were. Are the new folks who come to follow celebs or just chat
> with their friends using it? No, probably not. The fact of the matter is the
> UI for that setting sucked rocks. First you have the fundamental confusion
> between "followers" (a noun) and "following" (a verb AND a noun). Put the
> two together and you can figure it out, have "following" by itself, and you
> have no idea. That you get used to, but it's confusing to new users. Add in
> that sometimes the site talks about "friends"--g*d knows what those are.
> Then you attempted to explain the settings in a menu item instead of using a
> simple English sentence, and finally you had the wrong default (don't see
> replies sent to people I don't follow) for new users. Every time I told
> someone about that setting, they were like "Oh! *That's* why I never saw
> anyone talking!" I *knew* what the settings did and I still found the text
> confusing. Whenever I told someone about it, I had to reread the site to
> make sure I got it right. Blaming lack of use on a bad UI is just lazy.
>
> Twitter is a transport. Different people use it very differently. What
> Twitter just did is like someone taking email and deciding that mailing
> lists aren't really very important, since they are used by very few people,
> so we'll just remove the ability to have a mailing list. After all, it
> simplifies authentication, and it reduces traffic. Unfortunately, a core set
> of very important people really, really need mailing lists. It's how they
> network, meet people, develop ideas, and improve software like... Twitter.
> Oops.
>
>
>
>


-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to