Product Design Flaws
Since last year we've been hearing from users and having discussions about removing this setting—feedback indicated that it was useful but also created confusion. People would change the setting and then not understand why their timeline had fragments of conversations. From the tweet author perspective, there was an unclear expectation as to who would actually see messages ****which often lead to trepidation when it came to using replies.**** Finally, even folks who understood the setting would ****complain that they couldn't follow accounts with a high volume of replies because the replies overwhelmed their timeline.**** It was becoming apparent that we had an opportunity for improvement.
Technical Problems
Even though only 3% of all Twitter accounts ever changed this setting away from the default, it was causing a strain and impacting other parts of the system. Every time someone wrote a reply Twitter had to check and see what each of their followers' reply setting was and then manifest that tweet accordingly in their timeline— ****this was the most expensive work the database was doing and it was causing other features to degrade**** which lead to SMS delays, inconsistencies in following, fluctuations in direct message counts, and more. Ideally, we would redesign and rebuild this feature but there was no time, hence the sudden deploy.
Hopefully, this clears things up a bit...
My **** highlights.
My response in one word: baloney. This "less hasty", presumably more measured explanation by @Biz of the #fixreplies issue, is still just as Orwellian, if not more so (it's trying to kick the propaganda into another gear, since the first round was so pathetically obvious).
Something like, "we should have listened better, but let me give you a dozen (dubious yet plausible sounding) reasons for why we didn't listen, didn't elicit feedback beforehand, and still won't listen in a meaningful way."
The excerpt shows two things: The tortured logic of why the old option was "a flaw" (rather than an OPTION) continues, and I highlighted the two items that stand out to me as particularly ridiculous ("trepidation about visibility" and "volume complaints"):
While there may have been some feedback about these, no statistics on the number of such complaints was given vs. the number of users who were perfectly happy with the OPTION.
(BTW, since we are TOLD that a "mere" 3% of users ever had the option turned on, how do we know that this number is accurate? From the vocal response under the #fixreplies hashtag, I could easily see it be higher, but I guess we'll have to believe them. Their behavior in this doesn't exactly inspire confidence.)
Secondly, @Biz seems to make the case that it was the additional database lookups due to the setting that made abandoning the option necessary (without notice). Sounds plausible enough, except that the continued filtering based on the question "is XYZuser following both sender AND receiver of this tweet?" itself ads 50% more database lookups from the start.
Stands to reason that NOT filtering out any @ replies would save this extra step on each tweet (even though it would increase volume a bit, but only when people were actually requesting/looking at their "with friends" stream). Which would seem much more in keeping with the open architecture and spirit of Twitter.
Give us all of the data, and then we can filter down from there. My guess is of the default setting had been "show all @ replies", then 90%+ of users would have happily left it there. After following more than about 100 committed, active Tweeters, it generally becomes about serendipity and personal filtering methods anyway.
Why exclude a whole class of tweets, just because we weren't already following one side of the conversation (this isn't Facebook's Walled Garden after all). THAT is not what will somehow save one from "tweet overload" (letting go of the guilt around feeling like you have to read every single incoming tweet might however).
The original default setting never made much sense to me (we do already have DMs for private conversation), and the new half-baked compromise "solution" is no better.
The only decent workaround I see for now is to prefix @ replies you do want your followers to see with something, like "Hey @xyz..." or "#fix @xyz", while the addressee will still presumably get the tweet due to the (excellent) new @ "mentions" tab feature. Only thing is, the "in reply to" link and threading will be gone.
Rather than taking things away, Twitter should be adding more intelligent conversation threading right in the Twitter Web interface, e.g. the way it is already being handled in Twitter Search (if you haven't tried/seen it there, do a search on Search.twitter.com - the search integration on Twitter itself does not have this yet - and look for "Show Conversation" links on tweets).
Which brings up one last point: If conversations are (OK to be) visible on Twitter Search, why not on Twitter itself?
Comments [0]