<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mashable - The Social Media Guide - Latest Comments in Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.disqus.com/</link><description>Internet and Technology News - Mashable is the world’s largest blog focused exclusively on Web 2.0 and Social Networking news. With more than 5 million monthly pageviews, Mashable is the most prolific blog reviewing new Web sites and services, publishing breaking news on what’s new on the web.</description><atom:link href="https://mashable.disqus.com/twitter_8220we_screwed_up8221_on_fixreplies/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 22 May 2009 01:39:41 -0000</lastBuildDate><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9783706</link><description>&lt;p&gt;THE TWITTER WHAT ARE YOU DOING SITE IS FUCKED UP IN SEVERAL WAYS!I SENT A COMMENT LAST NIGHT.IT ABVYOSLY BIDDENT GO THREW. THIS ONE HAD BETTER!I DONT WANT AN APPOLLIGY OR 2 CENTS.JUST FIX IT!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Georgette Banker</dc:creator><pubDate>Fri, 22 May 2009 01:39:41 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9489833</link><description>&lt;p&gt;I've read 2% of users, now 3%- I think the tech issue explanation was a quick excuse to cover the mistake they know they made. If the technical aspects of the coding were in such disarray, that should have been the first point addressed. Even as a blogger, if something technical causes delays for my readers, I address it first and foremost. Not to mention, if "only 3%" used the option, why such an outrage by the Twitter community?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beth</dc:creator><pubDate>Mon, 18 May 2009 07:20:45 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9443402</link><description>&lt;p&gt;great point. i'm still pissed. my timeline is basically a ghosttown. argh!! i don't appreciate this "apology" or "explanation." &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ibwoke</dc:creator><pubDate>Sat, 16 May 2009 13:07:39 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9401427</link><description>&lt;p&gt;I think what they should have said was: the @reply was taking too much of a performance hit when it had to check all of the followers for the user and if many people were doing this at the same time I can see it brings the network and web server to it's knees.. As a QA engineer who has tested performance problems with web applications, I feel this is the issue. What is important to customers and end-users is 1) Performance and 2) UI. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">@DonnaMolinari</dc:creator><pubDate>Sat, 16 May 2009 02:29:07 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9371746</link><description>&lt;p&gt;I guess I'm one of the 3%. I just want to reiterate that it makes it almost moot to follow "celeb" tweeters now bc followers will no longer be able to read answers to questions from fans posted by celebs (unless they RT). It's been great being able to follow conversations between people and this is no longer possible. I have defintely expanded my twitter networks by reading a reply and thinking "oh! I didn't know he/she tweeted!" I hope a solution is found soon. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bizmeister</dc:creator><pubDate>Fri, 15 May 2009 16:07:10 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9368175</link><description>&lt;p&gt;Being one of the 3% who used the feature, I miss it a lot. I miss seeing the tweets of various celebrities I follow that aren't directed to me, and it's going to be very annoying having to check all of their pages daily now for updates I've missed because they didn't show up on my time line.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lemland</dc:creator><pubDate>Fri, 15 May 2009 14:13:04 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9367844</link><description>&lt;p&gt;&lt;br&gt;Twitter is like a breath of fresh air on the Social Media scene. I have been on it for just a few weeks now and I have met several interesting people. It is a platform to network with people you would like to meet in real life.&lt;/p&gt;&lt;p&gt;KZ&lt;br&gt;&lt;a href="http://www.epostmailer.com/" rel="nofollow noopener" target="_blank" title="http://www.epostmailer.com/"&gt; http://ePostMailer.com &lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">spryka</dc:creator><pubDate>Fri, 15 May 2009 14:03:54 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9367835</link><description>&lt;p&gt;I think all you TWEETHEADS are people that believe you are smarter than everyone else.  Your arrogance is appalling!  You guys have no real value add to society as a whole.  The company screwed up and did what most companies do not do...and that is state they screwed up and are actively fixing the problem.&lt;/p&gt;&lt;p&gt;Who cares what the issue was; they are fixing it.  So get off all of your tweet boxes and get real jobs!!&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Micah</dc:creator><pubDate>Fri, 15 May 2009 14:03:42 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9367696</link><description>&lt;p&gt;I highly doubt twitter will lose many people over this.  This latest post rings very true to me as an IT person.&lt;/p&gt;&lt;p&gt;The thing that jumps out at me is their continued insistence that this was confusing.  maybe it was, but reworking Help and Settings pages certainly could have fixed that, so I just don't buy it as a legitimate reason to make the change.  Specifically, they said&lt;/p&gt;&lt;p&gt;"People would change the setting and then not understand why their timeline had fragments of conversations."&lt;br&gt;I think this is very misleading.  I think it's a lot more likely that new users to twitter didn't understand the fragments.  I know it took me a week or two to start understanding the flow.  I have serious trouble buying that twitter users other than new/infrequent users went to the trouble of changing the setting AND then were confused.  So this seems to me to be a new user help/introduction problem.&lt;/p&gt;&lt;p&gt;" 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."&lt;br&gt;Twitter users need to be totally clear that unless their updates are protected or they are sending a DM, ANYONE can see them.  Period. That includes non-twitter users. Operating under any other assumption is ridiculous and twitter could rectify this by making this clear.  Don't put anything into your stream that you wouldn't want broadcast everywhere.&lt;/p&gt;&lt;p&gt;" 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."&lt;br&gt;This is the most ridiculous one.  They could have changed the setting!  You're saying they understood it, so they would know what to do.  Now maybe they're upset because they only want to see @replies for some people but not others?  Ok, well the solution didn't fix that and probably pissed them off as well.&lt;/p&gt;&lt;p&gt;I love twitter.  I have no plans to stop using it even if they kept the change.  and I certainly don't have any vitriol towards the people who made the decisions.  But I hope they understand that the "design" reasons for the change simply don't hold up to any kind of scrutiny as justification.  Better to just stop citing them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edward G. Talbot</dc:creator><pubDate>Fri, 15 May 2009 13:58:37 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9366232</link><description>&lt;p&gt;How many software developers think filtering replies vs. NOT filtering replies SHOULD be exponentially simpler.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason A. Nunnelley</dc:creator><pubDate>Fri, 15 May 2009 13:06:31 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9364595</link><description>&lt;p&gt;&lt;br&gt;I just got a copy of &lt;a href="http://www.epostmailer.com/" rel="nofollow noopener" target="_blank" title="http://www.epostmailer.com/"&gt; http://ePostMailer.com &lt;/a&gt; and I would recommend to anyone who needs to send out an opt-in email mailshot. Its the best free desktop based email marketing software I have used so far.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">spryka</dc:creator><pubDate>Fri, 15 May 2009 12:07:43 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9363737</link><description>&lt;p&gt;While I find it hard to believe that only 3% of users utilize the @reply feature, perhaps that number is so small because of the ridiculous influx of celebrity Twitter followers, what isn't clear is if it will be put back or not. As almost every one of us early and power Twitter users has told Twitter, this particular feature is how our networks have grown, which in turn is how Twitter has grown. If Twitter is not going to give back the feature, then our networks will become stagnant as we won't grow them without knowing who to Follow. #followfriday and #newbietuesday help, but it's really about finding interesting people from seeing part of an interesting conversation, not just being told someone is cool. That's fine for Ellen, Oprah, @aplusk, and @mrskutcher, but how about those whose conversations are the real value of Twitter? Once more: it's about the content, but this change in functionality is now hiding that content.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael</dc:creator><pubDate>Fri, 15 May 2009 11:37:47 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9362290</link><description>&lt;p&gt;Wow lots of YouTube-level commentary here. This explanation seems perfectly reasonable, and the fact that they're working to restore the functionality means we'll have back what we're all wanting.&lt;/p&gt;&lt;p&gt;It's understandable that Twitter's explosive growth would uncover kinks in the way things were implemented when the service was much smaller, and implementing new hacks to fix it as some of you have suggested is a laughable solution. I have more faith in the Twitter team to come up with workable, scalable solution than all of the armchair programmers who say it should be an easy fix.&lt;/p&gt;&lt;p&gt;And for those of you are giving up on Twitter and switching over to Facebook, good riddance.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Todd H</dc:creator><pubDate>Fri, 15 May 2009 10:46:09 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9361841</link><description>&lt;p&gt;A logical person would have understood that the part of transaction with the highest server cost isn't based on the &lt;i&gt;number of active users&lt;/i&gt;, it's based on &lt;b&gt;the number of follower accounts&lt;/b&gt;.  Every time somebody posed an @reply, Twitter had to check all of the poster's followers to see if they were an all-reply-enabled account, &lt;i&gt;whether or not that account is "active"&lt;/i&gt;. In the cost/benefit analysis, active and inactive users &lt;i&gt;have the same cost&lt;/i&gt;. Therefore, the number of accounts &lt;i&gt;is&lt;/i&gt; the more important number.&lt;/p&gt;&lt;p&gt;(Obscure irony: A lot of Twitter's inactive accounts are probably created by people who were invited by their nerd friends, followed their nerd friend, then stopped using Twitter. Twitter's most ardent evangelists may have contributed heavily to this problem.)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Bauser</dc:creator><pubDate>Fri, 15 May 2009 10:31:17 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9361025</link><description>&lt;p&gt;You humble opinion betrays a deep ignorance about how captialisim works. Also, it shows that &lt;b&gt;you still don't understand this is an engineering problem.&lt;/b&gt;&lt;/p&gt;&lt;p&gt;Sometimes, tech companies have to look at features of their products and decide if the return is worth the investment. Twitter had a feature that an overwhelming majority of its users don't use, that was taking up a disproportionate amount of engineering resources. They had to drop the feature, or reivent their architecture (apparently). They did a cost/benefit analysis, and decided dropping the feature was the smart thing to do.&lt;/p&gt;&lt;p&gt;That's life at a tech company. Sometimes you try an idea that sounds cool, it doesn't work out, and you drop it. If companies felt obligated to provide enternal support for features that on 2-3% users ended up using, it would &lt;b&gt;discourage&lt;/b&gt; innovation, because management wouldn't want to greenlight as many new ideas. There has to be room for failure to encourage innovation.&lt;/p&gt;&lt;p&gt;Listen, I agree that it sucks when a website loses a feature you like. (Facebook does it to me a lot.) But I understand why it happens, and I see why Twitter did what it did. At this point, everybody who uses an assinine phrase like "in my opinion" and "even if only 2% used it" is just being oblivious, or throwing a tantrum.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Bauser</dc:creator><pubDate>Fri, 15 May 2009 10:01:33 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9360945</link><description>&lt;p&gt;I'm late to the conversation, but it's absolutely amazing to me that tech investors and administrators don't take a page from this history book and change their behavior patterns... well, I say amazing. What I mean is to say it's amazing that I know this won't change anything.&lt;/p&gt;&lt;p&gt;In order for Twitter's architecture to have an inability to store a single YES/NO feature with relatively cheap overhead it's got to be absolutely broken. Twitter's volume of text messaging is huge, but the tasks are relatively simple. And, this particular task is extremely simple. If it is in fact crippling, and I take Twitter at their word, this is mindbogglingly bad. Only, it's a trend.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason A. Nunnelley</dc:creator><pubDate>Fri, 15 May 2009 09:57:08 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9359810</link><description>&lt;p&gt;My sentiments exactly, Farnham.  They owe us nothing.  They provide an awesome, free service.  The entitlement mindset is rampant, though.  Maybe Twitter can get bailout money, too.  Look how it helped Chrysler. Uh, nevermind.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott</dc:creator><pubDate>Fri, 15 May 2009 09:04:13 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9359746</link><description>&lt;p&gt;I'm really glad they posted this explanation. However, I'm uncertain about the future: I like seeing "all the tweets" those I'm following send out, just because I use twitter to see what's going on in their world. I really hope Twitter will offer that option, but I'm afraid they might not, because they're so focused on "@replies to non-followees as a means of discovery of new people".&lt;/p&gt;&lt;p&gt;To me, "show me @replies only if I follow the person they're sent to" is artificial, and I don't like it at all.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stephanie Booth</dc:creator><pubDate>Fri, 15 May 2009 09:01:57 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9357063</link><description>&lt;p&gt;Now you disappoint me, Scott Stratten (@unmarketing). You didn't want to see what your closest 25k friends were writing to others? :)&lt;/p&gt;&lt;p&gt;(Ironically the larger your following/follower set gets for someone such as yourself, the larger the % of @ reply tweets that will surface in your timeline even with the default setting.)&lt;/p&gt;&lt;p&gt;I am now seeing A LOT less of you, is that truly what you are arguing for? See, I used to click through a lot of your little "Well played Sir!" and "...and by XYZ, I mean..." type @ reply banter with peeps. Most of it is GONE now... If anything, Twitter should be integrating MORE conversation threading/visibility into the platform, not less. It already works on &lt;a href="http://Search.twitter.com" rel="nofollow noopener" target="_blank" title="Search.twitter.com"&gt;Search.twitter.com&lt;/a&gt;, so what gives?&lt;/p&gt;&lt;p&gt;The point is, it's better to have access to the full data set (which should also be less expensive database lookup-wise), and then filter down from there as you see fit. Twitter's spirit is openness (maybe a lot more open than its founders foresaw), why deny access to an entire class of Tweets out of hand?&lt;/p&gt;&lt;p&gt;BTW, I find Mashable's lauding here of Twitter's apology as "frank and honest" almost as Orwellian as Twitter's language in all of this from the get-go. They (Biz, et al.) still continue to try (rather clumsily) to tell us what to think. Propaganda that can easily be spotted is... 2nd rate propaganda.&lt;/p&gt;&lt;p&gt;Also agree with people further down that the 3% of users number feels "massaged". If it were % of active users it should be a good bit higher. Don't trust any statistic you haven't forged yourself...&lt;/p&gt;&lt;p&gt;(Wrote a longer retort here:&lt;/p&gt;&lt;p&gt;&lt;a href="http://alexschleber.posterous.com/my-comment-on-this-excerpt-from-twitter-blog" rel="nofollow noopener" target="_blank" title="http://alexschleber.posterous.com/my-comment-on-this-excerpt-from-twitter-blog"&gt;http://alexschleber.postero...&lt;/a&gt;&lt;br&gt;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Fri, 15 May 2009 05:22:20 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9355690</link><description>&lt;p&gt;Nevertheless, it was &lt;em&gt;an option&lt;/em&gt;, IMO if only &lt;b&gt;1%&lt;/b&gt; of the users were using it they &lt;em&gt;should've left it&lt;/em&gt;, I don't see how they help the community by removing something that is totally optional and not default - even if only the 'power' users would make use of this (which is not totally true in this situation)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Miladinoski</dc:creator><pubDate>Fri, 15 May 2009 04:25:34 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9351940</link><description>&lt;p&gt;While I appreciate the "effort" made to mollify the "power users" by Mr. Stone, I still am reading that the twitter we knew, is gone... and still suggest folks go to the GetSatisfaction website to continue the discussion - &lt;a href="http://gsfn.us/t/6g7y" rel="nofollow noopener" target="_blank" title="http://gsfn.us/t/6g7y"&gt;http://gsfn.us/t/6g7y&lt;/a&gt; and retweet the url to their followers...&lt;/p&gt;&lt;p&gt;Be Well!&lt;br&gt;ECS Dave - &lt;a href="http://twitter.com/ECS_Dave" rel="nofollow noopener" target="_blank" title="http://twitter.com/ECS_Dave"&gt;http://twitter.com/ECS_Dave&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ECS Dave</dc:creator><pubDate>Fri, 15 May 2009 00:47:53 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9351778</link><description>&lt;p&gt;"This is a smart and necessary move by Twitter() that will no doubt ease tensions in the community." This statement is patently false and non-realistic. Just look at the posts pertaining to #fixreplies and try to repeat the statement truthfully. As to having discussions with users that made them think it was a good thing to do? Again, check out how many people are upset over it. I think that leaves a very, very small percentage who it was discussed with. I do, however, agree that the information on the feature was sketchy so not everyone could understand which option to use. If it was placing a burden on the system, it was being implemented incorrectly.&lt;/p&gt;&lt;p&gt;So, thanks, Twitter developers, for successfuly pissing off MOST of your users while making your program boring. You also succeeded in following in Facebook's footsteps: taking a highly successful site, arbitrarily changing successful features and annoying people. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">LadyWrites</dc:creator><pubDate>Fri, 15 May 2009 00:35:37 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9351702</link><description>&lt;p&gt;I'm still flabbergasted that they&lt;/p&gt;&lt;p&gt;1. Changed something without consulting people, dissing it as being "small" and "undesirable" even if 100,000 people explicitly decided to use it&lt;br&gt;2. Tried to cover it up with excuses&lt;br&gt;3. Provided no real answer to what they'll do next. Notice they say 'the use case...will return' but not that we'll actually *be able to read what people write* plain and simple. Sounds like a cop-out for the "contact discovery" feature they want to introduce.&lt;/p&gt;&lt;p&gt;An excuse is the least I expect. This is not what they've supplied. It's just a compilation of their non-replies and more, basically calling me an idiot by using the feature, as if I "didn't understand" what was it about.&lt;/p&gt;&lt;p&gt;Call me a jaded user complaining about something that's free, but up until now they had my utmost respect and trust, something I don't easily 'give' to a startup. That has been lost.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zimzum</dc:creator><pubDate>Fri, 15 May 2009 00:30:40 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9351604</link><description>&lt;p&gt;you took the words right out of my mouth. there are soooooooooo many inactive accounts due to people who sign up just to see what twitter is about or because they hear oprah is on it, but never tweet. and then there are the spammers who don't actually read the tweets of the 10,000 people they follow.&lt;/p&gt;&lt;p&gt;if twitter could query their db based on a minimum # of tweets sent to determine "active" users, the number who use the all @replies setting would likely be much higher than 3%. not exactly scientific but it would tell them more about how valuable the feature has become.&lt;/p&gt;&lt;p&gt;also, even if only 3% of your users are your "most active" users, do you really want to abruptly change the way they use your service? that 3% has likely made twitter into much of what it is today. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dwag</dc:creator><pubDate>Fri, 15 May 2009 00:23:56 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.com/2009/05/14/twitter-screwed-up/#comment-9351594</link><description>&lt;p&gt;What do I think? I think removing the feature is pretty idiotic ... watching other peoples' conversations is an important part of what is useful about Twitter.&lt;br&gt;Really, showing @replies should be the default. Make it show for everybody if they want to get rid of the option, rather than showing nobody.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steve</dc:creator><pubDate>Fri, 15 May 2009 00:23:02 -0000</pubDate></item></channel></rss>