[twitter-dev] How can I tell if Tweet button is clicked?
Hi Is there a way to tell if the Tweet button on my webpage was clicked? If it was clicked I want to immediately enable Button2 (asp.net Button) on the same page so users can then click Button2. If the Tweet button wasn't clicked I want Button2 to remain disabled. TIA Mark -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Debugging 401 unauthorized errors
Hi, I'm getting some 401 unauthorized responses for reasons I can't figure out. On my local machine everything works fine. On my staging and production machines I get 401 errors for requests to account/ verify_credentials. All other requests work fine, such as statuses/ friends. The staging and production machines use different Twitter applications, so they have different keys and tokens, but as I say these are working fine for other oauth requests, it's just the account/ verify_credentials that consistently fails. Any other ideas for things to check. Is it possible to get more information from the API as to why a 401 has been returned? Thanks, Andy. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Consumer Key and Secret Bug
On Jun 5, 1:22 pm, Tom van der Woerdt i...@tvdw.eu wrote: Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Would you mind clearing that up a little? 350 request per hour? I have been reading about this but it does not make much sense to me. I am just creating application such as twitteriffic. I only call out for 100 tweets per timeline and as of right now I am the only one using this. So to clarify this...350 request per hour, would that include a NSLog? just logging the information to use to parse? I am quite confused to why their is a block or limit and what I can do to not hit that limit but still achieve retrieving data from twitter for an application that is estimated to have over 5,000 users when released? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] How can I tell if Tweet button is clicked?
Hey there, You can use our new Web Intents JavaScript Events. Take a look on the click event on https://dev.twitter.com/pages/intents-events hope that helps, Arnaud / @rno http://twitter.com/rno On Sun, Jun 5, 2011 at 9:53 PM, MarkB123 inbox.mirror.orbis...@gmail.comwrote: Hi Is there a way to tell if the Tweet button on my webpage was clicked? If it was clicked I want to immediately enable Button2 (asp.net Button) on the same page so users can then click Button2. If the Tweet button wasn't clicked I want Button2 to remain disabled. TIA Mark -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Checking whether a user has given permission to Private Messages
Hi, The doc says, “read-write-directmessages” (Read, Write, Direct Message) But actually I get read-write-privatemessages as you mentioned. It's a doc bug, right? Best, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On May 24, 2011, at 08:18 , Arnaud Meunier wrote: We just started to return the X-Access-Level header for authenticated API requests, that tells you what access level the user token has: - read (Read-only) - read-write (Read Write) - read-write-privatemessages (Read, Write, Private Message) The FAQ on http://dev.twitter.com/pages/application-permission-model-faq will be udpated in a minute :) Hope that helps, Arnaud / @rno On Mon, May 23, 2011 at 3:26 PM, Tyson Lowery tysonlow...@gmail.com wrote: I think I found the answer from themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Consumer Key and Secret Bug
API requests. Loading a page from https://api.twitter.com/1/ counts as 1 request. Of course, it goes per user per application, so the number of users isn't really relevant for iPhone applications. http://dev.twitter.com/pages/rate-limiting Tom On 6/5/11 10:39 PM, iDeviceDesigns wrote: On Jun 5, 1:22 pm, Tom van der Woerdti...@tvdw.eu wrote: Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Would you mind clearing that up a little? 350 request per hour? I have been reading about this but it does not make much sense to me. I am just creating application such as twitteriffic. I only call out for 100 tweets per timeline and as of right now I am the only one using this. So to clarify this...350 request per hour, would that include a NSLog? just logging the information to use to parse? I am quite confused to why their is a block or limit and what I can do to not hit that limit but still achieve retrieving data from twitter for an application that is estimated to have over 5,000 users when released? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Streaming API, Following just a couple of people
I I start following just 1 or 2 people using the streaming API I do not get any of their tweets. Is there a buffer that needs to be filled before I get these? Ray Slakinski -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Bug with oAuth headers supplied as querystring parameters for /users/lookup.json
On Jun 3, 4:58 pm, Jay Caines-Gooby jaygo...@gmail.com wrote:
I think I've found a bug when using the /users/lookup.json API call
and supplying the oAuth headers as querystring parameters.
OK, I've solved this. There seems to be different signature checking
applied to different API calls that require authentication.
I went back and re-read http://dev.twitter.com/pages/auth and
specifically noticed the line Query parameters in this case would
include both query parameters passed to the base_uri on the query
string or in URL-encoded post bodies, as well as all relevant OAuth
parameters pertinent to the request in motion
When generating the querystring version of my call, e.g.
curl -v -H 'Accept: application/json' 'https://api.twitter.com/1/users/
lookup.json?realm=https://api.twitter.com/1/users/
lookup.jsonoauth_consumer_key=KKKoauth_token=TTToauth_nonce=601731307364156oauth_timestamp=1307364156oauth_signature_method=HMAC-
SHA1oauth_version=1.0oauth_signature=SSS%3Duser_id=254723679'
I'd ommitted the 'realm' attribute during the signature generation.
Adding this causes the users/lookup.json call to function as expected.
However this still left the issue of why some authenticated calls
still worked when called without using the realm in the signature:
I double checked that a call to a user requiring authentication would
fail, when no authentication was provided:
curl -v -H 'Accept: application/json'
https://api.twitter.com/1/friends/ids.json?user_id=254723679
The response (as expected) was:
{error:Not authorized,request:\/1\/friends\/ids.json?
user_id=254723679}
I then used my code - that *omitted* the 'realm' attribute when
signing the authentication - to generate a request:
curl -v -H 'Accept: application/json' 'https://api.twitter.com/1/
friends/ids.json?realm=https://api.twitter.com/1/friends/
ids.jsonoauth_consumer_key=KKKoauth_token=TTToauth_nonce=601731307364817oauth_timestamp=1307364817oauth_signature_method=HMAC-
SHA1oauth_version=1.0oauth_signature=SSS%3Duser_id=254723679'
It *successfully* returns the list of friend ids for this protected
user, but in the returned HTTP headers, displays:
X-Warning: Invalid OAuth credentials detected
So it knows that the signature was incorrect, but returned the result
anyway. Using the same code that again, omits the realm attribute for
the requests results in the error I was seeing:
{error:Incorrect signature}
So it appears the actual bug in the API, is the inconsistency with the
way the signature is calculated when the oauth attributes are supplied
on the commandline. For friends/ids.json the realm attribute can be
omitted and you'll receive a warning, but get data back, but for users/
lookup.json you'll get the Incorrect signature error - which obeys
the letter of the law regarding oauth attributes in the querystring
parameters as per http://dev.twitter.com/pages/auth
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] New widgets.js
It seems that the widgets.js has been updated and I can no longer load tweet buttons dynamically with: var tweet_button = new twttr.TweetButton(element); tweet_button.render(); Does anyone know what the new syntax is? - Andrew -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
I'm not Arnaud, but I can assure you that it won't happen. Tom On 6/6/11 4:25 PM, Julien Larios wrote: Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
Completely agree with Tom on that one. On 6 Jun 2011, at 15:29, Tom van der Woerdt wrote: I'm not Arnaud, but I can assure you that it won't happen. Tom On 6/6/11 4:25 PM, Julien Larios wrote: Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Oauth Rate Limit 150 per hour?
Hi,
I am performing OAuth to sign my requests. I am not developing a web
app. I am trying to harvest some user data. Here's what I do :
import oauth2 as oauth
import time
CONSUMER_KEY = 'xx'
CONSUMER_SECRET = 'xx'
access_key = 'xx'
access_secret_key = 'xxx'
consumer = oauth.Consumer(CONSUMER_KEY, CONSUMER_SECRET)
token = oauth.Token(access_key, access_secret_key)
client = oauth.Client(consumer)
# Set the API end point
url = 'http://api.twitter.com/1'
params = {'oauth_version': 1.0,
'oauth_nonce': oauth.generate_nonce(),
'oauth_timestamp': int(time.time()),
'oauth_token': access_key,
'oauth_consumer_key': consumer.key,
'screen_name' : 'denzil_correa'
}
req = oauth.Request(method=GET, url=url, parameters=params)
# Sign the request.
signature_method = oauth.SignatureMethod_HMAC_SHA1()
req.sign_request(signature_method, consumer, token)
### Make the auth request ###
test = 'http://api.twitter.com/1/account/rate_limit_status.json'
resp, content = client.request(test, GET)
print resp
print content # prints 'ok'
Here's the output:
{reset_time:Mon Jun 06 14:54:50 +
2011,remaining_hits:132,hourly_limit:150,reset_time_in_seconds:1307372090}
Am I missing something?
--Regards,
Denzil
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Is that Python? Anyway, not relevant.
1. You aren't signing using the proper url.
2. You aren't using anything related to the signature on the request (req).
Tom
On 6/6/11 4:43 PM, Correa Denzil wrote:
Hi,
I am performing OAuth to sign my requests. I am not developing a web
app. I am trying to harvest some user data. Here's what I do :
import oauth2 as oauth
import time
CONSUMER_KEY = 'xx'
CONSUMER_SECRET = 'xx'
access_key = 'xx'
access_secret_key = 'xxx'
consumer = oauth.Consumer(CONSUMER_KEY, CONSUMER_SECRET)
token = oauth.Token(access_key, access_secret_key)
client = oauth.Client(consumer)
# Set the API end point
url = 'http://api.twitter.com/1'
params = {'oauth_version': 1.0,
'oauth_nonce': oauth.generate_nonce(),
'oauth_timestamp': int(time.time()),
'oauth_token': access_key,
'oauth_consumer_key': consumer.key,
'screen_name' : 'denzil_correa'
}
req = oauth.Request(method=GET, url=url, parameters=params)
# Sign the request.
signature_method = oauth.SignatureMethod_HMAC_SHA1()
req.sign_request(signature_method, consumer, token)
### Make the auth request ###
test = 'http://api.twitter.com/1/account/rate_limit_status.json'
resp, content = client.request(test, GET)
print resp
print content # prints 'ok'
Here's the output:
{reset_time:Mon Jun 06 14:54:50 +
2011,remaining_hits:132,hourly_limit:150,reset_time_in_seconds:1307372090}
Am I missing something?
--Regards,
Denzil
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Is that Python? : Yes 1. You aren't signing using the proper url. Is the end point URL wrong? 2. You aren't using anything related to the signature on the request (req) I am a newbie to Python. I am trying to dabble using OAuth. I understand the OAuth flow but somehow what I am doing seems a bit tangential to what OAuth is meant for. What should I do to rectify it ? --Regards, Denzil On Mon, Jun 6, 2011 at 8:16 PM, Tom van der Woerdt i...@tvdw.eu wrote: You aren't using anything related to the signature on the request (req). -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. Tom On 6/6/11 4:54 PM, Correa Denzil wrote: Is that Python? : Yes 1. You aren't signing using the proper url. Is the end point URL wrong? 2. You aren't using anything related to the signature on the request (req) I am a newbie to Python. I am trying to dabble using OAuth. I understand the OAuth flow but somehow what I am doing seems a bit tangential to what OAuth is meant for. What should I do to rectify it ? --Regards, Denzil On Mon, Jun 6, 2011 at 8:16 PM, Tom van der Woerdti...@tvdw.eu wrote: You aren't using anything related to the signature on the request (req). -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Tom : Thanks for the reply. 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. I have changed the same 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. I don't understand this point. What's the change am I supposed to make ? I have opened up a gist for easier editing : https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:30 PM, Tom van der Woerdt i...@tvdw.eu wrote: 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
In the Make the auth request part you make a request using client instead of the already prepared and signed req variable. You should use req to make the request. Tom On 6/6/11 5:10 PM, Correa Denzil wrote: Tom : Thanks for the reply. 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. I have changed the same 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. I don't understand this point. What's the change am I supposed to make ? I have opened up a gist for easier editing : https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:30 PM, Tom van der Woerdti...@tvdw.eu wrote: 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, in module resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Well, of course, don't literally replace the variables, but figure out a way to use the req object. I don't know anything about that object so I can't help you there. Tom On 6/6/11 5:28 PM, Correa Denzil wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzil mcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, in module resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
In that case, try removing everything related to the req variable. Seems it's all unrelated to the actual request (unless the oauth library is very badly designed, of course). Line 22 all the way up to 35. Tom On 6/6/11 5:38 PM, Correa Denzil wrote: Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzilmcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
Hey Julien, For now we're focusing on opening the Twitter Photo API endpoints to third party developers. These new API endpoints will be dedicated to Twitter media hosting, you won't be able to use them as a bridge/proxy for other media hosting services. Arnaud / @rno On Jun 6, 2011, at 7:25 AM, Julien Larios julien.lar...@gmail.com wrote: Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Streaming API, Following just a couple of people
Hey Ray, As soon as the connection is established, you start receiving public statuses that match your filter predicates. Are you sure these users were actually tweeting during the time you were consuming the stream? Arnaud / @rno http://twitter.com/rno On Mon, Jun 6, 2011 at 6:04 AM, Ray Slakinski ray.slakin...@gmail.comwrote: I I start following just 1 or 2 people using the streaming API I do not get any of their tweets. Is there a buffer that needs to be filled before I get these? Ray Slakinski -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Streaming API, Following just a couple of people
Hi Ray, There isn't a buffer that has to be filled before the Streaming API delivers tweets. Only public tweets created after you open a connection will be delivered. Have the users you are following Tweeted since you connected, and are they public accounts (not protected)? On Jun 6, 2011, at 6:04, Ray Slakinski ray.slakin...@gmail.com wrote: I I start following just 1 or 2 people using the streaming API I do not get any of their tweets. Is there a buffer that needs to be filled before I get these? Ray Slakinski -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Debugging 401 unauthorized errors
Hi Andy, The response body from API should contain a more descriptive message about the cause of the 401 error. Can you inspect the body of the API response and let us know what it says? @themattharris On Jun 4, 2011, at 19:20, Andy Hume andyh...@gmail.com wrote: Hi, I'm getting some 401 unauthorized responses for reasons I can't figure out. On my local machine everything works fine. On my staging and production machines I get 401 errors for requests to account/ verify_credentials. All other requests work fine, such as statuses/ friends. The staging and production machines use different Twitter applications, so they have different keys and tokens, but as I say these are working fine for other oauth requests, it's just the account/ verify_credentials that consistently fails. Any other ideas for things to check. Is it possible to get more information from the API as to why a 401 has been returned? Thanks, Andy. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Checking whether a user has given permission to Private Messages
Hi Yusuke, We are standardizing the phrasing to match the API requests so in this case the docs are correct. We have a fix to correct messages to 'direct' instead of 'private' on it's way. @themattharris On Jun 5, 2011, at 23:41, Yusuke Yamamoto yus...@mac.com wrote: Hi, The doc says, “read-write-directmessages” (Read, Write, Direct Message) But actually I get read-write-privatemessages as you mentioned. It's a doc bug, right? Best, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On May 24, 2011, at 08:18 , Arnaud Meunier wrote: We just started to return the X-Access-Level header for authenticated API requests, that tells you what access level the user token has: - read (Read-only) - read-write (Read Write) - read-write-privatemessages (Read, Write, Private Message) The FAQ on http://dev.twitter.com/pages/application-permission-model-faq will be udpated in a minute :) Hope that helps, Arnaud / @rno On Mon, May 23, 2011 at 3:26 PM, Tyson Lowery tysonlow...@gmail.com wrote: I think I found the answer from themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: t.co?
You can learn about what t.co is and what it is used for by visiting http://t.co . That page has a summary description and links to a help article with more detailed information. Best, @themattharris On Jun 5, 2011, at 14:02, Tim Meadowcroft meer...@gmail.com wrote: The point of t.co, as I understand it, is twitter's very different dynamic with regards to spam. Consider a scenario: someone creates a new account, sends one message with @mentions of 5 high profile people, almost no text, but an http ref (perhaps wrapped behind a shortener, maybe not). In the world of email, this would skew towards a spam rating, in the twitter world this may be someone in an oppressed regime getting a desperate message out - twitter's vision is to facilitate such messages without leaving the door open to abuse. So rather than block the message (unlike email, this is close-to-real-time) they wrap the href in a t.co reference that THEY control and publish the message. If the real link turns out to be spam or malice or gratuitous nonsense, they can, at any point after publishing the message, simply redirect the t.co reference they've allocated, otherwise they leave it in place. When you look at t.co from this point of view, I believe it makes sense - you may or may not agree with the technique but I believe it's not some kind of land-grab for complete control, but quite a smart and considered approach to the trade-offs inherent in their service. There are interviews with their spam people that explain this in more detail if you search for them -- T -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Yes, it works. Thanks :-) --Regards, Denzil On Mon, Jun 6, 2011 at 9:10 PM, Tom van der Woerdt i...@tvdw.eu wrote: In that case, try removing everything related to the req variable. Seems it's all unrelated to the actual request (unless the oauth library is very badly designed, of course). Line 22 all the way up to 35. Tom On 6/6/11 5:38 PM, Correa Denzil wrote: Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzilmcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter and iOS - an Integration Workshop
Hi everyone, We're incredibly excited about the announcement that Apple made at WWDC today. We believe that Twitter's deep integration with iOS is going to open up a lot of exciting opportunities for developers. For your apps, this includes: - single sign-on and lightweight identity - taking advantage of the tweet sheet feature - the ability to tweet a photo from your app - pulling down a user's following graph and a whole lot more. As part of the announcement, we're looking to host a workshop at Twitter's headquarters this Wednesday (6/8) from 6:30pm to 8:30pm at 795 Folsom Street. At this event, we'll cover what the integration hooks mean for developers. Loren Brichter will also be talking about ABUIKit, a UI framework specifically for Mac, which we'll be open-sourcing. In order to attend, you'll need to first be registered as an Apple Developer - you can register with Apple here: http://developer.apple.com/programs/register/ Please also RSVP at the link below (with your Apple Developer login): http://bit.ly/jBX5B6 We hope you'll be able to join us for the evening. --@jasoncosta -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter and iOS - an Integration Workshop
What about the rest of the iOS developers who can't be there? I'm registered as an Apple Developer but I'm not there... Tom On 6/6/11 8:29 PM, Jason Costa wrote: Hi everyone, We're incredibly excited about the announcement that Apple made at WWDC today. We believe that Twitter's deep integration with iOS is going to open up a lot of exciting opportunities for developers. For your apps, this includes: - single sign-on and lightweight identity - taking advantage of the tweet sheet feature - the ability to tweet a photo from your app - pulling down a user's following graph and a whole lot more. As part of the announcement, we're looking to host a workshop at Twitter's headquarters this Wednesday (6/8) from 6:30pm to 8:30pm at 795 Folsom Street. At this event, we'll cover what the integration hooks mean for developers. Loren Brichter will also be talking about ABUIKit, a UI framework specifically for Mac, which we'll be open-sourcing. In order to attend, you'll need to first be registered as an Apple Developer - you can register with Apple here: http://developer.apple.com/programs/register/ Please also RSVP at the link below (with your Apple Developer login): http://bit.ly/jBX5B6 We hope you'll be able to join us for the evening. --@jasoncosta -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] What is the correct way to get user permission to publish a tweet
I have a client who wants to print tweets on t-shirts and other products. The API TOS says to get the users' permission, but doesn't say how. Is it enough to send them a tweet asking to use one of their past tweets, and then get a tweeted permission from them? Or does this permission have to be in writing? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] What is the correct way to get user permission to publish a tweet
Hi Adam, This kind of permission can be granted in many ways -- it's ultimately your responsibility to ensure that you and the author of the tweet are on the same page before using their tweets on physical goods or otherwise. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 6, 2011 at 12:35 PM, Adam Green 140...@gmail.com wrote: I have a client who wants to print tweets on t-shirts and other products. The API TOS says to get the users' permission, but doesn't say how. Is it enough to send them a tweet asking to use one of their past tweets, and then get a tweeted permission from them? Or does this permission have to be in writing? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Limit to total direct messages able to be sent?
I had this app that would use c# and twitterizer to merrily send a user direct messages, it has since ceased to do so (it still can use twitpic which will send status updates all good but direct messages no more. It will receive direct messages and purge them just won't send them out. I used the web site interface of the account my app uses and tried to send a direct message and I get an error box there: Sorry! We did something wrong. Try sending your message again in a minute. Though from main timeline a d username myMessage works but still doesn't get through to receiver and they both are following each other. Is there some limit to direct Messages stored for a user and when they reach that limit they cannot send anymore? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] 500 Error using POST friendships/create
Hey, I'm trying to follow users using the POST friendships/create method on the API but I'm getting a 500 error. The error message told me to post to this group. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter's iOS integration and what this means for developers
Hey all, There have been a lot of questions about what the iOS announcement today means for developers. The integration points noted in Apple’s keynote create huge opportunities for both Twitter and iOS developers. There is single sign-on, which allows you to retrieve a user's identity, avatar, and other profile data. There's also a frictionless core signing service, allowing you to make and sign any call to the Twitter API. There is follow graph synchronization, which enables you to bootstrap a user's social graph for your app. Furthermore, there is the tweet sheet feature, giving your app distribution and reach across Twitter. These key integration points and more will be available to developers once the SDK goes live. We’re holding the event this Wednesday night (6:30pm to 8:30pm) to talk about these key integration points and more, and how you can use these hooks in greater detail. If you have questions - this is a great time to get them answered. The agenda will include: - Introduction by @rsarver - iOS integration overview by @raffi - Technical details of iOS integration by @sandofsky - ABUIKit presentation from @atebits - QA w/ @rsarver, @raffi, and @sandofsky - Tea Time (social) Please don’t forget to RSVP for the event: http://bit.ly/jBX5B6 --@jasoncosta -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter's iOS integration and what this means for developers
On Mon, Jun 6, 2011 at 8:05 PM, Jason Costa jasonco...@twitter.com wrote: There have been a lot of questions about what the iOS announcement today means for developers. The integration points noted in Apple’s keynote create huge opportunities for both Twitter and iOS developers. The first question that everyone should be asking is: Will you hold off the DM Oauth reauthorization requirement until iOS 5 is released, so people don't have to go through it again and again and again for each Twitter app? And if not, why not? (Other than not giving a whit about 3rd party Twitter client app developers, but being more interested in helping developers of other apps integrate Twitter into their apps.) TjL -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Twitter's iOS integration and what this means for developers
Ya. Integrate the supertweet API. On Jun 6, 8:17 pm, TJ Luoma luo...@gmail.com wrote: On Mon, Jun 6, 2011 at 8:05 PM, Jason Costa jasonco...@twitter.com wrote: There have been a lot of questions about what the iOS announcement today means for developers. The integration points noted in Apple’s keynote create huge opportunities for both Twitter and iOS developers. The first question that everyone should be asking is: Will you hold off the DM Oauth reauthorization requirement until iOS 5 is released, so people don't have to go through it again and again and again for each Twitter app? And if not, why not? (Other than not giving a whit about 3rd party Twitter client app developers, but being more interested in helping developers of other apps integrate Twitter into their apps.) TjL -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
