| Issue 483: | Need a way to submit multiple follow requests in bulk | |
| 4 people starred this issue and may be notified of changes. | Back to list |
I can see the potential for abuse for this so perhaps an approval process would be necessary, but I am running into major headaches trying to set up auto-follow for some of the users on the Featured users list with near a million followers. I could process these much faster if we could submit all the people we need to follow for them in bulk, rather than one at a time. It would take much fewer hits to the Twitter servers, and overall be a much faster experience for all involved. If you want specific examples of whom I'm talking about please don't hesitate to talk to me. |
|
,
Apr 20, 2009
There are too many spam implications with mass following.
Status: WontFix
Labels: -Type-Enhancement -Priority-Medium Milestone-V2 Priority-Low |
|
,
Apr 20, 2009
That's why I suggest some sort of approval process. There are legitimate uses for it - surely you can come up with some way to make the legitimate uses work and keep out the bad ones. |
|
,
Apr 20, 2009
We can probably do this for selected, O-authorized apps.
Status: Accepted
Owner: alexfpayne |
|
,
Apr 20, 2009
Alex, you are my hero. :-) Thanks. |
|
,
Apr 20, 2009
I'm not sure from Jesse's description if he means following many people by one person or following one person by many people in one API call? |
|
,
Apr 20, 2009
arikfri, I mean follow many people with one person |
|
,
Apr 20, 2009
I see. Well, that can be useful too - I'm the guy behind Topify.com, so I guess if someone follows back more than person in a certain time frame I can save some processing time by using this method. |
|
,
Apr 21, 2009
Moved to http://apiwiki.twitter.com/V2-Roadmap. |
|
,
Apr 21, 2009
(No comment was entered for this change.)
Status: Moved
|
|
,
Apr 21, 2009
Marking "Invalid" so these issues don't clutter the main view of issues. All are tracked on http://apiwiki.twitter.com/V2-Roadmap
Status: Invalid
|
|
,
Apr 21, 2009
What is the "streaming API" listed on the V2 roadmap out of curiosity? |
|
,
Apr 21, 2009
It's not on V2 because it's already operational with select partners. Opening it up to more partners is an independent project. |
|
|
|