Streamlining the blocking/denying process

First let me state that I have a protected account. Given the uptick of mass followers (borderline link spammers IMHO), I've been blocking a lot of users recently. When you're following 58K people, I'm not interested in being one of them. :-)

I notice however that blocking a user leaves their follower request active. If I failed to open the twitter user's updates page in a new window, it's a whole lot of clicking involved. Here's the process:

1. Go to friend requests page
2. Click on twitter users to see who they are and/or if I'm interested in following them back (because currently, that's required
3. Find out that in fact, I'm definitely NOT now nor ever. Hence, I click Block this user
4. Page refreshes to my own home page
5. Click on friend requests again
6. See still active request from the user and click deny

Again, LOTS of clicks. What I'd like to see is a workflow like the following:

1. Go to friend requests page
2. Click on twitter users to see who they are and/or if I'm interested in following them back (because currently, that's required
3. Find out that in fact, I'm definitely NOT now nor ever. Hence, I click Block this user
4. Page refreshes, still on that user's page (for contextual consistency) and shows me a message that says "You have blocked this users and denied their request. Would you like to see __your other friend requests__"? (With the underscored linked back to my friend's request page). I click back to my friend request

Other than the fewer number of steps, this also provides contextual consistency that is currently lacking where when I block a user, I'm transported back to my home page which is neither my origin nor current destination.

This sort of streamlined process would be greatly appreciated. Thanks Twitter team!
 
happy I’m thankful
Inappropriate?
3 people have this question

User_default_medium