Don't scrape our site. Seriously. Our operations staff will blackhole your IP.
On Fri, Jan 30, 2009 at 06:14, Daniel Kwiecinski <daniel.kwiecin...@gmail.com> wrote: > Thanks for pointing this one. > Does anybody can comment on using requests to the Twitter website (not the > API part) as a API. That would be a workaround to the issue. > Does it break the usage licence or any other Twitter's policy? > > Regards, > Daniel > > 2009/1/30 cjmartin <cjmar...@gmail.com> >> >> This api call has been requested and accepted (although with a low >> priority and milestone of V2, whenever that is) at >> >> http://code.google.com/p/twitter-api/issues/detail?id=8&q=label:Type-Enhancement&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Milestone >> >> Everyone else that wants it should go star it to remind them that it's >> important to us. >> >> On Jan 17, 1:03 am, Abraham Williams <4bra...@gmail.com> wrote: >> > Was the flow previously that by following someone you where approving >> > them >> > to follow you? Or has it always been the way it currently is? >> > On Thu, Jan 15, 2009 at 02:18, Daniel Kwiecinski < >> > >> > >> > >> > daniel.kwiecin...@gmail.com> wrote: >> > > OK, that's answers my question - it is not possible to establish a >> > > relation >> > > between 2 users via API in order to allow sending direct messages. >> > >> > > It arises question number two: >> > > Is it prohibited to pretend web GUI so my app will using pure HTTP >> > > will >> > > accept "follow request" ? >> > >> > > Thank you, >> > > Daniello >> > >> > > 2009/1/15 Damon Clinkscales <sca...@pobox.com> >> > >> > >> Until the "follow request" is approved by user A, B is not really >> > >> following A. Therefore A can't send a DM to B. >> > >> > >> AFAIK, there's not a way to do the follow approval process step via >> > >> the API. That step is done in the Twitter UI. >> > >> > >> -damon >> > >> > >> On Wed, Jan 14, 2009 at 10:40 AM, Daniel Kwiecinski >> > >> <daniel.kwiecin...@gmail.com> wrote: >> > >> > Following your advice I executed: >> > >> > >> > 3.) >> > >> > >> > curl -u user_a:pass_a -d "" >> > >> >http://twitter.com/friendships/create/user_b.json >> > >> > >> >> > >> {"description":"","screen_name":"user_b","url":null,"name":"user_b","protec >> > >> ted":false,"profile_image_url":"http:\/\/ >> > >> static.twitter.com >> > >> >> > >> \/images\/default_profile_normal.png","location":"","id":xxx,"followers_cou >> > >> nt":1} >> > >> > >> > but I can not send direct messages from user_a to user_b ;( >> > >> > >> > 4.) >> > >> > >> > curl -u user_a:pass_a -d "user=user_b&text=bla" >> > >> >http://twitter.com/direct_messages/new.json >> > >> > {"request":"\/direct_messages\/new.json","error":"You cannot send >> > >> messages >> > >> > to users who are not following you."} >> > >> > -- >> > | Abraham Williams |http://the.hackerconundrum.com >> > | Web608 | Community Evangelist |http://web608.org >> > | gg&d | betaGeek |http://girlsgeeksanddating.com >> > | Micro-email:http://userscripts.org/scripts/show/38822 >> > | This email is: [] blogable [x] ask first [] private > > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
