Let me boil it down to the simplest case.
I have a protected account that I want to use to provide notifications
to my users (but only my users). I have oauth completely set up to
let my users authorize me to their twitter accounts. I can then make
their twitter account follow me. Except, since I'm protected, that
following request isn't honored until I accept the pending follow
requests. Currently there is no 'friendships/accept' type API method
so I have effectively done nothing until a human presses the accept
So since this isn't going to work any time soon via the api, am I
likely to get myself banned if I write a bot that periodically logs in
and 'clicks' the accept all pending follower requests link that I as a
human can see? And by periodically I think I mean once an hour or
On Tue, Jun 15, 2010 at 6:22 PM, Taylor Singletary
> The breadth of functionality we have right now is, unfortunately:
> GET friendships/incoming http://dev.twitter.com/doc/get/friendships/incoming
> GET friendships/outgoing http://dev.twitter.com/doc/get/friendships/outgoing
> and the rest of the friendship methods on the API.
> Now, there may be a way to use these methods in combination with each other
> to accomplish your goals, but I haven't yet connected the dots to ascertain
> that. I can take a close look, or if someone else on the list has more
> experience in this arena, they might have a suggestion.
> Otherwise, I'd recommend going on with your workaround. The v1 API is going
> to be around for awhile, and I don't think we have this feature on our
> immediate roadmap; that said, sometimes a new feature that's been requested
> like this "just pops up." We'll announce when/if that happens.
> On Tue, Jun 15, 2010 at 3:03 PM, Robert Van Dam <rvanda...@gmail.com> wrote:
>> Then perhaps I should ask my real question. I'm working on a system
>> for broadcasting messages to subsets of our users and we have set up
>> separate accounts for each subset. However, the company I work for
>> does not want these tweets to be fully public (they are not overly
>> sensitive but nonetheless...) but if I make the accounts protected,
>> then I can not automatically have our customers follow us since there
>> is no function in the api for accepting pending friend requests.
>> So my two options are to make a human login and periodically click the
>> 'Accept all' link on several different accounts or I can write a bot
>> to do it (which I'm sure someone will tell me is a bad idea). I
>> noticed that there were a couple bug reports about this issue but they
>> were closed with links to the now apparently defunct V2-Roadmap page
>> and obviously no solution in the last two years since the first bug
>> was filed.
>> Is there any chance this functionality will be coming to the api any
>> time soon or will I be forced to code around it indefinitely?
>> On Tue, Jun 15, 2010 at 1:05 PM, Taylor Singletary
>> <taylorsinglet...@twitter.com> wrote:
>> > Hi Rob,
>> > Over time the v2 Roadmap became less and less relevant. We're currently
>> > rethinking what V2 might look like with fresh eyes.
>> > Taylor
>> > On Tue, Jun 15, 2010 at 9:28 AM, Rob <rvanda...@gmail.com> wrote:
>> >> I've seen many references to http://apiwiki.twitter.com/V2-Roadmap,
>> >> particularly with regards to a current api issue I have (accepting
>> >> pending follow requests on protected accounts) but when I go to that
>> >> page I get a mostly empty page that just says "You don't have
>> >> permission to look at V2 Roadmap." Is that intentional and if so is
>> >> there some place I can go to request access? I don't see any obvious
>> >> way to signup and login into the necessary workspace on pbwiki.