[twitter-dev] REST API entities enabled by default?

2010-09-19 Thread SkyLifeLabs
I was under the impression that entities were opt-in for XML payloads in timeline API methods. I have been getting entities returned from user_timeline calls (e.g., http://api.twitter.com/1/statuses/user_timeline/transportworker.xml?include_rts=true) and was wondering if I missed something or if

[twitter-dev] I have one problem with from_user_id and id

2010-09-19 Thread Artem Kovardin
when i use http://search.twitter.com/search.json?q=%23Kharkov, from_user_id well say 2792464 and from_user : 'e0ne' in first twitt in result , but when i use http://api.twitter.com/1/users/show.json?user_id=2792464 - this is not user. from_user_id(in search) != id(in user)? P.S. sorry for my bad

Re: [twitter-dev] I have one problem with from_user_id and id

2010-09-19 Thread CWorster
That's a known defect. Quote from API documentation: http://dev.twitter.com/doc/get/search Warning: The user ids in the Search API are different from those in the REST API (about the two APIs). This defect is being tracked by Issue 214. This means that the to_user_id and from_user_id field vary

Re: [twitter-dev] REST API entities enabled by default?

2010-09-19 Thread CWorster
http://api.twitter.com/1/statuses/user_timeline/transportworker.xml?include_rts=true You're appending include_rts=true, that is the opt-in parameter to get the retweets inline. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:

[twitter-dev] Re: REST API entities enabled by default?

2010-09-19 Thread SkyLifeLabs
Thanks, you are correct. I should have been more specific: I would like the retweets but not the entity data for the 'entities' node which I thought was opt-in only using include_entities=true as per the API docs (http://dev.twitter.com/doc/get/statuses/user_timeline). I have also tried it without

[twitter-dev] “Failed to validate oauth signature and token

2010-09-19 Thread bill
Hi, I am trying a do twitter authentication using oAuth. I am getting error in first step itself (i.e while getting RequestToken itself). I am trying this from a php page running on my machin (twitter application registered as desktop application). I am new to php development, any inputs are

[twitter-dev] Re: New twitter interface

2010-09-19 Thread engel...@gmail.com
What about the width screen design? is it changing? that is important for the twitter background design market. Engel On Sep 15, 4:49 pm, Tom van der Woerdt i...@tvdw.eu wrote: There are no changes to the API so your project should not be broken (unless you are breaking Twitter's TOS). Tom

Re: [twitter-dev] Re: New twitter interface

2010-09-19 Thread Tom van der Woerdt
Assuming that you don't have access to the #newtwitter yet: * There are still backgrounds * The width did indeed change Tom On 9/19/10 7:49 PM, engel...@gmail.com wrote: What about the width screen design? is it changing? that is important for the twitter background design market. Engel

[twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

2010-09-19 Thread Nikolay Klimchuk
Good news everyone Twitter changed example at http://dev.twitter.com/pages/xauth Now my code gives the same result as in example NSString *s= @POSThttps%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA

[twitter-dev] Re: “Failed to validate oauth signat ure and token

2010-09-19 Thread Nikolay Klimchuk
Sorry I don't know answer on your question but in general would be nice to have more informative error messages from Twitter I'm tired of Failed to validate oauth signature and token, if there is a problem with timestamp just let me know! It will also reduce amount of messages in this group On

[twitter-dev] Grease Monkey and #NewTwitter

2010-09-19 Thread Matt Sanford
Hi all, Not sure who has #NewTwitter so far, and who has interest in Grease Monkey, but I threw together a quick blog post on adding content to the new Detail Pane at http://bit.ly/gm-newtwitter. I'm planning to do a second post on more complicated scripts soon (like the bit.ly click counter

Re: [twitter-dev] Grease Monkey and #NewTwitter

2010-09-19 Thread M. Edward (Ed) Borasky
1. Still waiting for #newtwitter 2. Don't know Greasemonkey - don't even use Firefox any more except as a last resort. I'm a Chromium / Chrome guy now. Anybody working on Chrome apps for #newtwitter? I've seen a couple in the app store for the current Twitter, but nothing I thought worthy

Re: [twitter-dev] Grease Monkey and #NewTwitter

2010-09-19 Thread Abraham Williams
Chrome supports userscripts minus a few custom GM APIs nativly http://blog.chromium.org/2010/02/4-more-extensions.html Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask

Re: [twitter-dev] Grease Monkey and #NewTwitter

2010-09-19 Thread Peter Denton
Matt, Awesome! I can't wait to see the cool things to be developed. Do you think there will be a showcase on dev.twitter for people to find scripts? Regards Peter Sent from my iPhone On Sep 19, 2010, at 4:59 PM, Matt Sanford matt+...@twitter.com wrote: Hi all, Not sure who has

[twitter-dev] who can share the tweet program(c++, liboauth)

2010-09-19 Thread yuzhujiutian
hi, all who can share the next tweet program(c++, liboauth)? I have achieved to obtain access token of the code(c++, liboauth), but in achieving the tweet, always prompt failure, who can send a demo program to me, the best is based on the liboauth, c++. And if someone on the oauth

[twitter-dev] Cursors remain same or do they change?

2010-09-19 Thread nischalshetty
Say, I need to retrieve friend ids of a user who has 50,000 friends. I do a get, then the subsequent gets are using the cursor returned. Now, are these cursor values the same? I mean, next time, if the users friends have increased to say 53000, can I get all the 50,000 using the old cursors and

Re: [twitter-dev] Help for twitteroauth

2010-09-19 Thread Abraham Williams
Could not connect to Twitter. Refresh the page or try again later. with TwitterOAuth generally means one of several things. You don't have a valid consumer key/secret being used, there is a firewall blocking access from your server to https://api.twitter.com, or your servers time is not being