Comments on: Twitter’s new Retweet Feature: I found a flaw (finally)

By: adamjackson

adamjackson — Thu, 19 Nov 2009 22:03:54 +0000

Thank you for the reply. So I've heard another person who said that as well over email so I'm not sure what the difference was. I did just doublecheck and it worked for me. Not sure what is different.

Regarding the blocked list, I wanted to add that it's not an official feature that's included in Twitter's Web Interface. Meaning, I can't go to settings and see who I'm blocking. An XML or API call isn't the same cause most users can't do that. A web developer did contact me and said we should build a site that shows you who you're blocking but at t his time, normal users can't get the info easily unless they know this tip you added.

By: vitanga

vitanga — Thu, 19 Nov 2009 22:01:29 +0000

I actually tried your "solution" and it didn't work for me. For testing purposes, I blocked both @aflacduck (RTed by @drew) and @mattcutts (RTed by @Scobleizer) and the RTs still showed up on my stream.

BTW, you CAN get a list of people you've blocked by going to http://twitter.com/blocks/blocking.xml and using your Twitter username and password.

By: calvinlotz

calvinlotz — Thu, 19 Nov 2009 20:25:47 +0000

It's a clever idea, but I find myself not checking out the browser version much anymore because it's like the public timeline at this point. I think retweets are being given too much power, in a way. It's just filling my screen with shit I don't care about, so I'm losing interest.

By: Navarr

Navarr — Thu, 19 Nov 2009 20:20:04 +0000

I agree. If blocking is supposed to be the way around this; then the block feature has a way to go itself before all is right. Of course, the problem with this is – even if you may not want to see this person's tweets in your streams, if you block them and they reply to you (which you might not have a problem with) you won't see those either.

Of course, this is a small flaw, and I do hope that twitter finds a way around it soon.