[twitter-dev] Rate limits for whitelisted IPs using user credentials
Is it possible to use a whitelisted IP to fetch data using a user's OAuth credentials without utilizing the user's 350/hr rate limit? For example, if I'm building a DM backup service, I'd like to be able to back up the user's DMs on their behalf without draining their rate limit. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Character limits on Direct Messages
I had always been under the impression that everything had a 140 character limit. -Dustin On 8/29/2010 9:20 PM, Orian Marx (@orian) wrote: It would appear that today Twitter began enforcing a 140 character limit on DMs. To my knowledge their was never a limit enforced before, and even Twitter.com would show up to 255 characters of a DM. Some Twitter clients, including mine, supported>140 char DMs and now I'm seeing people really upset that they can't send longer messages any more. To me this was a significant change and should have been announced to the developer community prior to being made. -Orian -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Character limits on Direct Messages
It would appear that today Twitter began enforcing a 140 character limit on DMs. To my knowledge their was never a limit enforced before, and even Twitter.com would show up to 255 characters of a DM. Some Twitter clients, including mine, supported >140 char DMs and now I'm seeing people really upset that they can't send longer messages any more. To me this was a significant change and should have been announced to the developer community prior to being made. -Orian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Change in error response objects
Raffi, Will the new error construct always be: [errors][code] [errors][message] Or can it be sometimes: [errors][0][code] [errors][0][message] [errors][1][code] [errors][1][message] -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Need help in using Twurl console
Can you send the exact command line you're using? bin/twurl /1/users/show.xml?screen_name=sujit_g Works for me ---Mark http://twitter.com/mccv On Sat, Aug 28, 2010 at 7:13 AM, Sujit wrote: > Hi, > > I have started development using Twitter API recently. > I really like the Twurl console which makes sending HTTP requests to > Twitter API very easy. > > I registered an app and coded a bare-bones structure of the app. > I was able to update my status message by running the app on my > desktop and also using the Twurl console. > > But, when I try to make a "users/show" request my app is returning me > an error user is "Not Found." > I get the same error using Twurl console also. > Can anyone guide me in this issue? This is a very basic question, but, > this got me blocked as of now. > > Here is the error message that I make a "users/show" request with > screen_name parameter as sujit_g (my screen name). > > > /1/users/show.xml > Not found > > > Thanks, > Sujit > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Twitter API ME 1.4: New release!!!
Hi all,
I would like to inform that *Twitter API ME 1.4* has just been released.
This new version comes with new features and the correction of a bug that
was preventing it to work on Blackberry devices. So Blackberry developers,
you all are now welcome back to Twitter API ME.
The new features available on version 1.4 are:
- Single Access Token auth
- Geo-located tweets
- Friends/Followers list
- Update user profile
See below how easy is to use Single Access token and send a geo-located
tweet.
*Token = new Token("token_access", "token_secret");*
*Credential c = new Credential("user_name", "consumer_key",
"consumer_secret", token);*
*
*
*UserAccountManager m = UserAccountManager.getInstance(c);*
*
*
*if (m.verifyCredential()) {*
* GeoLocation loc = new GeoLocation("+37.5", "+26.7");*
* Tweet t = new Tweet("Cool! Geo-located tweet via Twitter API ME. \o/",
loc);*
*
*
* TweetER ter = TweetER.getInstance(m);*
*
*
* t = ter.post(t);*
*}*
Easy, huh?
For further information on Twitter API ME, please visit us at
www.twitterapime.com.
Regards,
--
Ernandes Jr.
-
"ALL programs are poems. However,
NOT all programmers are poets."
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Getting 401 in the past 2 days
Never mind, the bug was in my own script. It was setting empty values
of oauth_token, and oauth_secret.
I corrected the problem and all works fine again.
On Aug 27, 4:36 pm, "D. Smith" wrote:
> Hello! I started getting 401 'count not authenticate' errors starting
> about 2 days ago when I try to send tweet via API.
> I use OAuth, use php pecl OAuth for that, just like I did before. The
> last tweet was successfully posted from my website was 2 days ago
>
> Here are the headers from the debug (I changed the values of my token/
> secret here for security)
>
> [headers_sent] => POST /1/statuses/update.json HTTP/1.1
>
> User-Agent: PECL-OAuth/1.0-dev
>
> Host: api.twitter.com
>
> Accept: */*
>
> Content-Length: 249
>
> Content-Type: application/x-www-form-urlencoded
>
> status=%20Hey
> %20everyone&oauth_consumer_key=gdsfgdsfgdfgdf&oauth_signature_method=HMAC-
> SHA1&oauth_nonce=12299221034c78207659bdc5.73793953&oauth_timestamp=12829410
> 46&oauth_version=1.0&oauth_token=&oauth_signature=1s8wiINcB9FKX0UjY c
> %3D
>
> And this is the received headers from API:
>
> [headers_recv] => HTTP/1.1 401 Unauthorized
>
> Date: Fri, 27 Aug 2010 20:30:46 GMT
>
> Server: hi
>
> Status: 401 Unauthorized
>
> WWW-Authenticate: Basic realm="Twitter API"
>
> X-Runtime: 0.00273
>
> Content-Type: application/json; charset=utf-8
>
> Content-Length: 75
>
> Cache-Control: no-cache, max-age=300
>
> Set-Cookie: k=67.19.114.2.1282941046438939; path=/; expires=Fri, 03-
> Sep-10 20:30:46 GMT; domain=.twitter.com
>
> Set-Cookie: guest_id=128294104644479603; path=/; expires=Sun, 26 Sep
> 2010 20:30:46 GMT
>
> Set-Cookie:
> _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCK3OPrUqAToHaWQiJWVhNjkyYjRiMTJlM2Uw
> %250AMzUwOWYyNDQxNWI1MThmNzk5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--428e590fbfbf78ddef85c177fb4f
> 958444ef969c;
> domain=.twitter.com; path=/
>
> Expires: Fri, 27 Aug 2010 20:35:46 GMT
>
> Vary: Accept-Encoding
>
> Connection: close
> [body_recv] => {"request":"/1/statuses/
> update.json","error":"Could not authenticate you."}
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Change in error response objects
* Raffi Krikorian [100827 06:03]:
> hi all.
>
> this is most certainly a mistake on our part - we'll be reverting this
> change.
Raffi, we're still seeing these unexpected error structures. When will
the change be reverted?
-Marc
> On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser wrote:
>
> > > It looks like error responses have changed, at least for users/show.
> > >
> > > I used to get:
> > > {"error":"User has been suspended"}
> > >
> > > Now, I get:
> > > {"errors":[{"code":63,"message":"User has been suspended"}]}
> >
> > I'm seeing that too. When did this change?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] What's the normal response of oauth/access_token?
Hi everyone, I'm writing an API proxy to work with twitter for iphone. When adding acount, twitter for iphone will send an request to oauth/ access_token. I tried to fake the response by returning a fake access token, but failed. Twitter for iphone always tell me that "Could not authenticate you. (XAuth migration failed - no token/secret handed back)". Can anyone give me a hint? P.S. API proxy works between client and twitter.com, and redirect requests from client to twitter.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
