[twitter-dev] REST API entities enabled by default?
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 there is a problem with the API lately. Thanks! -- 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] I have one problem with from_user_id and id
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 english -- 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] I have one problem with from_user_id and id
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 from the actualy user id on Twitter.com. Applications will have to perform a screen name-based lookup with the users/show method to get the correct user id if necessary. -- 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] REST API entities enabled by default?
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: 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: REST API entities enabled by default?
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 include_rts=true (http:// api.twitter.com/1/statuses/user_timeline/TWU556.xml) and still get the entities, at least according to a dump with 'curl http://api.twitter.com/1/statuses/user_timeline/TWU556.xml'. On Sep 19, 7:33 am, CWorster cwors...@schlimmer.com wrote: http://api.twitter.com/1/statuses/user_timeline/transportworker.xml?i... 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: 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] “Failed to validate oauth signature and token
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 appreciated. Below are Request and Response Thanks, Ramesh -- request -- HTTP_OAuth_Consumer_Request Object ( [authType:protected] = 1 [secrets:protected] = Array ( [0] = Cxnk2e8Kbz8CLskAwzl7BBlCvkjPptSHcEIzXXvUAE [1] = ) [request:protected] = HTTP_Request2 Object ( [observers:protected] = Array ( ) [url:protected] = Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = /oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) [method:protected] = POST [auth:protected] = [headers:protected] = Array ( [user-agent] = HTTP_Request2/0.5.2 (http://pear.php.net/ package/http_request2) PHP/5.3.1 [authorization] = OAuth realm=http://twitter.com/;, oauth_consumer_key=*, oauth_nonce=*, oauth_signature=*, oauth_signature_method=HMAC- SHA1, oauth_timestamp=1284910240, oauth_version=1.0 ) [config:protected] = Array ( [adapter] = HTTP_Request2_Adapter_Socket [connect_timeout] = 10 [timeout] = 0 [use_brackets] = 1 [protocol_version] = 1.1 [buffer_size] = 16384 [store_body] = 1 [proxy_host] = [proxy_port] = [proxy_user] = [proxy_password] = [proxy_auth_scheme] = basic [ssl_verify_peer] = 1 [ssl_verify_host] = 1 [ssl_cafile] = [ssl_capath] = [ssl_local_cert] = [ssl_passphrase] = [digest_compat_ie] = [follow_redirects] = [max_redirects] = 5 [strict_redirects] = ) [lastEvent:protected] = Array ( [name] = disconnect [data] = ) [body:protected] = [postParams:protected] = Array ( ) [uploads:protected] = Array ( ) [adapter:protected] = HTTP_Request2_Adapter_Socket Object ( [serverChallenge:protected] = [proxyChallenge:protected] = [deadline:protected] = [chunkLength:protected] = 0 [redirectCountdown:protected] = [contentLength:protected] = 0 [socket:protected] = ) ) [parameters:protected] = Array ( [oauth_callback] = [oauth_consumer_key] = * [oauth_signature_method] = HMAC-SHA1 [oauth_timestamp] = 1284910240 [oauth_nonce] = * [oauth_version] = 1.0 [oauth_signature] = = ) ) -- response -- HTTP_OAuth_Consumer_Response Object ( [response:protected] = HTTP_Request2_Response Object ( [version:protected] = 1.1 [code:protected] = 401 [reasonPhrase:protected] = Unauthorized [headers:protected] = Array ( [date] = Sun, 19 Sep 2010 15:30:41 GMT [server] = hi [status] = 401 Unauthorized [x-transaction] = 1284910241-69054-62865 [last-modified] = Sun, 19 Sep 2010 15:30:41 GMT [x-runtime] = 0.01374 [content-type] = text/html; charset=utf-8 [pragma] = no-cache [x-revision] = DEV [expires] = Tue, 31 Mar 1981 05:00:00 GMT [cache-control] = no-cache, no-store, must-revalidate, pre-check=0, post-check=0 [x-xss-protection] = 1; mode=block [x-frame- options] = SAMEORIGIN [vary] = Accept-Encoding [content-encoding] = gzip [content-length] = 62 [connection] = close ) [cookies:protected] = Array ( [0] = Array ( [expires] = Sun, 26- Sep-10 15:30:41 GMT [domain] = .twitter.com [path] = / [secure] = [name] = k [value] = 98.180.203.164.1284910241513942 ) [1] = Array ( [expires] = Tue, 19 Oct 2010 15:30:41 GMT [domain] = [path] = / [secure] = [name] = guest_id [value] = 128491024151857994 ) [2] = Array ( [expires] = [domain] = .twitter.com [path] = / [secure] = [name] = _twitter_sess [value] = **d2f0b79c14dec4c9fe0ac026395fd6afc68a3c75 ) ) [lastHeader:protected] = connection [body:protected] = ‹ sKÌÌIMQ(ÉW(KÌÉLI,IUÈO,-ÉP(ÎLÏK,)-JUHÌ Ég§æ šÎë, [bodyEncoded:protected] = 1 ) [parameters:protected] = Array ( ) ) ERROR: Failed getting token and token secret from response -- 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: New twitter interface
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 On 9/15/10 9:56 PM, bobrik wrote: http://twitter.com/newtwitter- that's what I plan to talk about. I have a project that could be broken by this new feature, but may be not as well. Does there any way to test new interface outside common slow feature rollout? Maybe some form to request that for developers only? I don't think that common help request could help. What do you think in common about new interface and possibilities to get involved? -- 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] Re: New twitter interface
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 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 On 9/15/10 9:56 PM, bobrik wrote: http://twitter.com/newtwitter- that's what I plan to talk about. I have a project that could be broken by this new feature, but may be not as well. Does there any way to test new interface outside common slow feature rollout? Maybe some form to request that for developers only? I don't think that common help request could help. What do you think in common about new interface and possibilities to get involved? -- 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: iPhone::Incorrect oauth_signature for xAuth?
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
%26oauth_nonce%3D6AN2dKRzxyGhmIXUKSmp1JcB4pckM8rD3frKMTmVAo
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1284565601%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
%26x_auth_password%3Dtwitter-xauth%26x_auth_username
%3Doauth_test_exec;
NSString *k = @9z6157pUbOBqtbm0A0q4r29Y2EYzIHlUwbF4Cl9c;
Gives oauth_signature=1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D
On Sep 16, 12:21 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share the code you're using?
On Wed, Sep 15, 2010 at 8:02 PM, Nikolay Klimchuk klimc...@gmail.comwrote:
That's really puzzling for me. I've tried 5 different ways to get
oauth_signature, even extracted from libraries suggested by Twitter
All of them produce same result MUYmiobRdoK6s0ZVqo4xQNNO17w=
It's different from examplehttp://dev.twitter.com/pages/xauth
I'm looking for any logical explanation for this
Nikolay Klimchuk
On Sep 15, 12:03 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Everyone,
I've revised the xAuth examples athttp://dev.twitter.com/pages/xauth--
you'll find they should have signatures that are easier to reproduce and
was
confirmed functional at the time of execution.
Thanks for the nudge, Tom.
Thanks,
Taylor
On Mon, Sep 13, 2010 at 11:41 AM, Tom van der Woerdt i...@tvdw.eu
wrote:
2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: 3146268a
86d17682
bab34655 aa8e3140 d34ed7bc
2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
MUYmiobRdoK6s0ZVqo4xQNNO17w=
Looks like you're right :-)
@episod: You should fix that! :-)
Tom
On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
Still no luck
With your code I'm gettings exactly the same result
MUYmiobRdoK6s0ZVqo4xQNNO17w=
Something really strange in example here
http://dev.twitter.com/pages/xauth
Nikolay Klimchuk
On Sep 13, 7:19 am, Tom van der Woerdt i...@tvdw.eu wrote:
Oh, hehe, good point. That's because my Base String has one extra
urlencoded '' on the end, and that shouldn't be there.
Tom
On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
klimc...@gmail.com wrote:
Thank you Tom
I will try your algorithm and compare results.
Quick question: why you do this [str substringToIndex:[str
length]-3] ?
Nikolay Klimchuk
On Sep 13, 2:46 am, Tom van der Woerdt i...@tvdw.eu wrote:
Hi Nikolay,
The first part of your code looks fine. You may, however, like to
do
some debugging on the HMAC part - it looks a bit too simple to me.
This works :
NSString *compKey = [NSString stringWithFormat:@
%@%@,secret,userSecret];
const char *cKey = [compKey
cStringUsingEncoding:NSUTF8StringEncoding];
const char *cData = [[str substringToIndex:[str length]-3]
cStringUsingEncoding:NSUTF8StringEncoding];
unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData,
strlen(cData), cHMAC);
NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC
length:sizeof(cHMAC)];
(str being the Base String)
Hope it helps :-)
Tom
On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
I'm trying to understand why algorithm for calculation of
oauth_signature does not give me the same result as shown here:
http://dev.twitter.com/pages/xauth
In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
If I URL encode such result it's still very different from
yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
I've tried different implementations, all of them give the same
result. After few hours of exercises with all this stuff I
completely
run out of ideas, please help
// Test with input data taken from Twitter page
NSString *s= @POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
%26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
%26x_auth_password%3D%2525%2526123%2521aZ%252B
%2528%2529456242134%26x_auth_username%3DtpFriendlyGiant;
NSString *k = @5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk;
NSString *signedSK = [NetworkManager
base64forData:[NetworkManager
HMACSHA1withKey:k forString:s]];
// Source code
+ (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
*)string
{
NSData *clearTextData = [string
dataUsingEncoding:NSUTF8StringEncoding];
NSData *keyData = [key
dataUsingEncoding:NSUTF8StringEncoding];
[twitter-dev] Re: “Failed to validate oauth signat ure and token
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 Sep 19, 11:39 am, bill ramesh.billap...@gmail.com wrote: 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 appreciated. Below are Request and Response Thanks, Ramesh -- request -- HTTP_OAuth_Consumer_Request Object ( [authType:protected] = 1 [secrets:protected] = Array ( [0] = Cxnk2e8Kbz8CLskAwzl7BBlCvkjPptSHcEIzXXvUAE [1] = ) [request:protected] = HTTP_Request2 Object ( [observers:protected] = Array ( ) [url:protected] = Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = /oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) [method:protected] = POST [auth:protected] = [headers:protected] = Array ( [user-agent] = HTTP_Request2/0.5.2 (http://pear.php.net/ package/http_request2) PHP/5.3.1 [authorization] = OAuth realm=http://twitter.com/;, oauth_consumer_key=*, oauth_nonce=*, oauth_signature=*, oauth_signature_method=HMAC- SHA1, oauth_timestamp=1284910240, oauth_version=1.0 ) [config:protected] = Array ( [adapter] = HTTP_Request2_Adapter_Socket [connect_timeout] = 10 [timeout] = 0 [use_brackets] = 1 [protocol_version] = 1.1 [buffer_size] = 16384 [store_body] = 1 [proxy_host] = [proxy_port] = [proxy_user] = [proxy_password] = [proxy_auth_scheme] = basic [ssl_verify_peer] = 1 [ssl_verify_host] = 1 [ssl_cafile] = [ssl_capath] = [ssl_local_cert] = [ssl_passphrase] = [digest_compat_ie] = [follow_redirects] = [max_redirects] = 5 [strict_redirects] = ) [lastEvent:protected] = Array ( [name] = disconnect [data] = ) [body:protected] = [postParams:protected] = Array ( ) [uploads:protected] = Array ( ) [adapter:protected] = HTTP_Request2_Adapter_Socket Object ( [serverChallenge:protected] = [proxyChallenge:protected] = [deadline:protected] = [chunkLength:protected] = 0 [redirectCountdown:protected] = [contentLength:protected] = 0 [socket:protected] = ) ) [parameters:protected] = Array ( [oauth_callback] = [oauth_consumer_key] = * [oauth_signature_method] = HMAC-SHA1 [oauth_timestamp] = 1284910240 [oauth_nonce] = * [oauth_version] = 1.0 [oauth_signature] = = ) ) -- response -- HTTP_OAuth_Consumer_Response Object ( [response:protected] = HTTP_Request2_Response Object ( [version:protected] = 1.1 [code:protected] = 401 [reasonPhrase:protected] = Unauthorized [headers:protected] = Array ( [date] = Sun, 19 Sep 2010 15:30:41 GMT [server] = hi [status] = 401 Unauthorized [x-transaction] = 1284910241-69054-62865 [last-modified] = Sun, 19 Sep 2010 15:30:41 GMT [x-runtime] = 0.01374 [content-type] = text/html; charset=utf-8 [pragma] = no-cache [x-revision] = DEV [expires] = Tue, 31 Mar 1981 05:00:00 GMT [cache-control] = no-cache, no-store, must-revalidate, pre-check=0, post-check=0 [x-xss-protection] = 1; mode=block [x-frame- options] = SAMEORIGIN [vary] = Accept-Encoding [content-encoding] = gzip [content-length] = 62 [connection] = close ) [cookies:protected] = Array ( [0] = Array ( [expires] = Sun, 26- Sep-10 15:30:41 GMT [domain] = .twitter.com [path] = / [secure] = [name] = k [value] = 98.180.203.164.1284910241513942 ) [1] = Array ( [expires] = Tue, 19 Oct 2010 15:30:41 GMT [domain] = [path] = / [secure] = [name] = guest_id [value] = 128491024151857994 ) [2] = Array ( [expires] = [domain] = .twitter.com [path] = / [secure] = [name] = _twitter_sess [value] = **d2f0b79c14dec4c9fe0ac026395fd6afc 68a3c75 ) ) [lastHeader:protected] = connection [body:protected] = ‹ sKÌÌIMQ(ÉW(KÌÉLI,IUÈO,-ÉP(ÎLÏK,)-JUHÌ Ég§æ šÎë, [bodyEncoded:protected] = 1 ) [parameters:protected] = Array ( ) ) ERROR: Failed getting token and token secret from response -- 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] Grease Monkey and #NewTwitter
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 display I'm testing locally). I'm looking forward to seeing what other people do with Grease Monkey and #NewTwitter as well. Thanks; — Matt Sanford -- 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] Grease Monkey and #NewTwitter
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 of installing. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Matt Sanford matt+...@twitter.com: 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 display I'm testing locally). I'm looking forward to seeing what other people do with Grease Monkey and #NewTwitter as well. Thanks; — Matt Sanford -- 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
Re: [twitter-dev] Grease Monkey and #NewTwitter
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 first [ ] private. On Sun, Sep 19, 2010 at 17:25, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: 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 of installing. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Matt Sanford matt+...@twitter.com matt%2b...@twitter.com: 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 display I'm testing locally). I'm looking forward to seeing what other people do with Grease Monkey and #NewTwitter as well. Thanks; — Matt Sanford -- 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 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] Grease Monkey and #NewTwitter
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 #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 display I'm testing locally). I'm looking forward to seeing what other people do with Grease Monkey and #NewTwitter as well. Thanks; — Matt Sanford -- 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] who can share the tweet program(c++, liboauth)
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 authentication of the request token, direct token(Obtain User Authorization), access token code debug it fails, we can share, I can share my aouth under the authentication of the demo program. -- 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] Cursors remain same or do they change?
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 then use the cursor from the last cursor call to get the remaining 3000 friends? -- 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] Help for twitteroauth
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 automatically synced. Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Sep 15, 2010 at 01:42, kilotto kilo...@gmail.com wrote: Hi all, I'm trying use twitteroauth but I have some problems. When I use twitter twitteroauth in my webserver ( http://twitter.domain.net ) the script display the error: Could not connect to Twitter. Refresh the page or try again later.. If I use other script, it display: Woah there! This page is no longer valid. It looks like someone already used the token information you provided. Please return to the site that sent you to this page and try again ... it was probably an honest mistake. I've tried twitteroauth in local and it works fine. How I can fix this ? Tnx! -- 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
