[twitter-dev] I cannot see CAPTCHA image in the Register Application page.
I am trying to register a new application at https://dev.twitter.com/apps/new. But the CAPTCHA image is not seen in my browser. I have tried with Chrome, IE6, IE7, FF4... What should I do? -- 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] inconsistent data when fetching the stream using location boxes
hi all I am developing a data mining application for telecom italia (the biggest tlc company in italy) and we're still refining the algorithms using a spritzer account. in order to maximize the streams around a few interesting locations (uk, spain, france, italy), our setup is using location boxes, as detailed here: http://dev.twitter.com/pages/streaming_api_methods#locations but something weird happens: we are receiving status updates out of the specified location boxes (fair enough...) from places that have the same names as others inside our location boxes. e.g. our box coordinates focused on UK obviously do not include US, but we are receiving tweets from 37.1289787 -84.0832596 (namely: london, KY) is there some reverse geo-coding going on? many thanks thomas -- 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] Brand Confusion
Hi Jerry, I think you're looking for this form for reporting brand/trademark issues: https://support.twitter.com/forms/trademark @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 20, 2011 at 7:06 PM, Jerry Thompson jerrycando...@gmail.comwrote: Who's the best person to reach out to at Twitter if there is a twitter account that is causing confusion with our brand and users? -- 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] 500 errors from the search api on specific queries, related to geocode parameter.
Hi Eric, For now you should be able to overcome this issue by requesting a much smaller amount of results per page -- you might find a sweeter spot with some of these queries at 20 to 40 rpp -- it's simply timing out building a result set for you at that quantity. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 20, 2011 at 8:34 AM, Eric Mueller nevin...@gmail.com wrote: I noticed some 500 responses to our search api requests this morning that were oddly consistent - specific queries that would always error, when most queries never (rarely) do. I started trying to reproduce with smaller queries, and arrived at a few examples. This search fails with a 500 error: http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.75,-84.37,12.35mi It probably should be returning an empty results list (notice the 12 mile radius). The same search with the decimals chopped off the latitude woks fine (empty results as expected): http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33,-84.77,12.35mi Removing the decimals from the longitude instead doesn't work: http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.25,-84,12.35mi *Changing* the value of the decimal digits on the latitude sometimes works, and sometimes doesn't: http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84,12.35mi http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.44,-84,12.35mi Changing the value of the decimal digits on the longitude doesn't seem to produce failures no matter what I put in. http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.01,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.44,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=biebergeocode=33.44,-84.99,12.35mi fails, but http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentgeocode=33.44,-84.99,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=palingeocode=33.44,-84.99,12.35mi (geocode only) works fine. I tested a few of these without rpp, lang, and result_type params with identical results, so you can probably disregard those. These aren't random failures - every time I try one of the failing queries, it continues to fail (though that may change as the result set changes over time). Are there any known bugs with the geocode handling in the search api? - Eric -- 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] 500 errors from the search api on specific queries, related to geocode parameter.
I considered that, but this fails too: http://search.twitter.com/search.json?rpp=4q=biebergeocode=33.25,-84,12.35mi -- 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] A few updates about the permission model change
I believe I am using the PHP Twitter libraries because I see Oauth.php and TwitterOauth.php being included in the script. I recently took this project over from the other developer and I am new to twitter programming, which is why I am unsure on how to grab that access level for the users in my database. On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote: Are you using any libraries? On 21 Jun 2011, at 18:59, Gene wrote: Hi Matt, Can you please give a quick example on how to get the X-Access-Level value. My application runs on PHP and I would like to get the X-Access- Level for all of the users in my application and store it into a database. I have all the keys, and tokens and everything. I am just getting tripped up on getting that value. Thanks for your help. Regards, Gene On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported onhttps://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in a simpler format * the language on all the screens is standardized to say direct message * there is a Return to App URL on the Deny and Cancel screens that redirects the user to the oauth_callback url with a 'denied' parameter instead of oauth_token. This next parameter isn't needed by everybody but we will be adding screen_name support to the authorize and authenticate pages in the next few days. If you want to add this to your code ready for when we release the feature you can, but please know the screen_name parameter will be ignored unless you also provide the force_login parameter. The screen_name parameter pre-fills the username field of the OAuth screen when force_login is true. The user is still able to edit the field, even if it is prefilled. Lastly, these are the main points discussed in previous emails and Tweets: * The new permission level will be enforced on 30th June. * If you don't need to read or delete direct messages you do not need to update the permission level of your application. * Read/Write applications will still be able to send direct messages, even after the enforcement date. * Existing oauth_tokens will not be invalidated, even if the application permission level is altered. * You can find out the current permission level of an oauth_token by inspecting the headers of an authenticated request to the API. Look for the X-Access-Level header. -- 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 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: User Search API
Thanks for answering. Now I know it isn't something I did. Doesn't look like a bug. The in-site search is now also limited to 20 results. Waiting for somebody **http://www.google.co.in/search?hl=enclient=firefox-arls=org.mozilla:en-US:officialsa=Xei=fd0AToufO8WIrAe65qH8DAved=0CCQQvwUoAQq=knowledgeablespell=1to shed some light on this. Thanks, Amit -- 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] A few updates about the permission model change
I can't test to confirm at the moment but I think I set up TwitterOAuth to include headers in the TwitterOAuth object. If you create a TwitterOAuth object like this: $connection = new TwitterOAuth($x, $y, $z, $a); Then you should be able to get the headers from the most recent request like this: $connection-http_info; Abraham - Abraham Williams | InboxQ http://inboxq.com/ | abrah.am @abraham https://twitter.com/intent/follow?screen_name=abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote: I believe I am using the PHP Twitter libraries because I see Oauth.php and TwitterOauth.php being included in the script. I recently took this project over from the other developer and I am new to twitter programming, which is why I am unsure on how to grab that access level for the users in my database. On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote: Are you using any libraries? On 21 Jun 2011, at 18:59, Gene wrote: Hi Matt, Can you please give a quick example on how to get the X-Access-Level value. My application runs on PHP and I would like to get the X-Access- Level for all of the users in my application and store it into a database. I have all the keys, and tokens and everything. I am just getting tripped up on getting that value. Thanks for your help. Regards, Gene On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported onhttps://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in a simpler format * the language on all the screens is standardized to say direct message * there is a Return to App URL on the Deny and Cancel screens that redirects the user to the oauth_callback url with a 'denied' parameter instead of oauth_token. This next parameter isn't needed by everybody but we will be adding screen_name support to the authorize and authenticate pages in the next few days. If you want to add this to your code ready for when we release the feature you can, but please know the screen_name parameter will be ignored unless you also provide the force_login parameter. The screen_name parameter pre-fills the username field of the OAuth screen when force_login is true. The user is still able to edit the field, even if it is prefilled. Lastly, these are the main points discussed in previous emails and Tweets: * The new permission level will be enforced on 30th June. * If you don't need to read or delete direct messages you do not need to update the permission level of your application. * Read/Write applications will still be able to send direct messages, even after the enforcement date. * Existing oauth_tokens will not be invalidated, even if the application permission level is altered. * You can find out the current permission level of an oauth_token by inspecting the headers of an authenticated request to the API. Look for the X-Access-Level header. -- 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 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] A few updates about the permission model change
Hmmmgetting closer but I don't see the http headers in there. I even did a var dump, but didn't see anything related to http_info. Know where else I could look? On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.com wrote: I can't test to confirm at the moment but I think I set up TwitterOAuth to include headers in the TwitterOAuth object. If you create a TwitterOAuth object like this: $connection = new TwitterOAuth($x, $y, $z, $a); Then you should be able to get the headers from the most recent request like this: $connection-http_info; Abraham - Abraham Williams | InboxQ http://inboxq.com/ | abrah.am @abraham https://twitter.com/intent/follow?screen_name=abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote: I believe I am using the PHP Twitter libraries because I see Oauth.php and TwitterOauth.php being included in the script. I recently took this project over from the other developer and I am new to twitter programming, which is why I am unsure on how to grab that access level for the users in my database. On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote: Are you using any libraries? On 21 Jun 2011, at 18:59, Gene wrote: Hi Matt, Can you please give a quick example on how to get the X-Access-Level value. My application runs on PHP and I would like to get the X-Access- Level for all of the users in my application and store it into a database. I have all the keys, and tokens and everything. I am just getting tripped up on getting that value. Thanks for your help. Regards, Gene On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported onhttps://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in a simpler format * the language on all the screens is standardized to say direct message * there is a Return to App URL on the Deny and Cancel screens that redirects the user to the oauth_callback url with a 'denied' parameter instead of oauth_token. This next parameter isn't needed by everybody but we will be adding screen_name support to the authorize and authenticate pages in the next few days. If you want to add this to your code ready for when we release the feature you can, but please know the screen_name parameter will be ignored unless you also provide the force_login parameter. The screen_name parameter pre-fills the username field of the OAuth screen when force_login is true. The user is still able to edit the field, even if it is prefilled. Lastly, these are the main points discussed in previous emails and Tweets: * The new permission level will be enforced on 30th June. * If you don't need to read or delete direct messages you do not need to update the permission level of your application. * Read/Write applications will still be able to send direct messages, even after the enforcement date. * Existing oauth_tokens will not be invalidated, even if the application permission level is altered. * You can find out the current permission level of an oauth_token by inspecting the headers of an authenticated request to the API. Look for the X-Access-Level header. -- 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 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] A few updates about the permission model change
var_dump the $connection object and find it in there. On 21 Jun 2011, at 19:55, Gene Ellis wrote: Hmmmgetting closer but I don't see the http headers in there. I even did a var dump, but didn't see anything related to http_info. Know where else I could look? On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.com wrote: I can't test to confirm at the moment but I think I set up TwitterOAuth to include headers in the TwitterOAuth object. If you create a TwitterOAuth object like this: $connection = new TwitterOAuth($x, $y, $z, $a); Then you should be able to get the headers from the most recent request like this: $connection-http_info; Abraham - Abraham Williams | InboxQ | abrah.am @abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote: I believe I am using the PHP Twitter libraries because I see Oauth.php and TwitterOauth.php being included in the script. I recently took this project over from the other developer and I am new to twitter programming, which is why I am unsure on how to grab that access level for the users in my database. On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote: Are you using any libraries? On 21 Jun 2011, at 18:59, Gene wrote: Hi Matt, Can you please give a quick example on how to get the X-Access-Level value. My application runs on PHP and I would like to get the X-Access- Level for all of the users in my application and store it into a database. I have all the keys, and tokens and everything. I am just getting tripped up on getting that value. Thanks for your help. Regards, Gene On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported onhttps://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in a simpler format * the language on all the screens is standardized to say direct message * there is a Return to App URL on the Deny and Cancel screens that redirects the user to the oauth_callback url with a 'denied' parameter instead of oauth_token. This next parameter isn't needed by everybody but we will be adding screen_name support to the authorize and authenticate pages in the next few days. If you want to add this to your code ready for when we release the feature you can, but please know the screen_name parameter will be ignored unless you also provide the force_login parameter. The screen_name parameter pre-fills the username field of the OAuth screen when force_login is true. The user is still able to edit the field, even if it is prefilled. Lastly, these are the main points discussed in previous emails and Tweets: * The new permission level will be enforced on 30th June. * If you don't need to read or delete direct messages you do not need to update the permission level of your application. * Read/Write applications will still be able to send direct messages, even after the enforcement date. * Existing oauth_tokens will not be invalidated, even if the application permission level is altered. * You can find out the current permission level of an oauth_token by inspecting the headers of an authenticated request to the API. Look for the X-Access-Level header. -- 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 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 -- Scott Wilcox
Re: [twitter-dev] A few updates about the permission model change
yep...that is what I did. This is what I received back:
object(TwitterOAuth)#1 (5) { [http_status:private]= NULL
[last_api_call:private]= NULL [sha1_method]=
object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]=
object(OAuthConsumer)#3 (3) { [key]= string(22)
Oa8K2pY7L19CLwerewVzJ5eES1A [secret]= string(42)
INoKYGcqbQqOrwerwhWuR2qUntjHx8xMDJaofc9dRkomRow [callback_url]= NULL }
[token]= object(OAuthConsumer)#4 (3) { [key]= string(50)
253725180-K6WHcDeILj3O6bikV1yC8zgYZqsrwerwdovyAJaTfyZ73 [secret]=
string(43) ENnvceX4JNbLTzTuVrwerwduATxXnFm0VRZkyNkc [callback_url]=
NULL } }
The values have been changed, but I don't see the header info. Am I missing
something?
On Tue, Jun 21, 2011 at 1:57 PM, Scott Wilcox sc...@dor.ky wrote:
var_dump the $connection object and find it in there.
On 21 Jun 2011, at 19:55, Gene Ellis wrote:
Hmmmgetting closer but I don't see the http headers in there. I even
did a var dump, but didn't see anything related to http_info. Know where
else I could look?
On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.comwrote:
I can't test to confirm at the moment but I think I set up TwitterOAuth to
include headers in the TwitterOAuth object.
If you create a TwitterOAuth object like this:
$connection = new TwitterOAuth($x, $y, $z, $a);
Then you should be able to get the headers from the most recent request
like this:
$connection-http_info;
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote:
I believe I am using the PHP Twitter libraries because I see Oauth.php
and TwitterOauth.php being included in the script. I recently took this
project over from the other developer and I am new to twitter programming,
which is why I am unsure on how to grab that access level for the users in
my database.
On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote:
Are you using any libraries?
On 21 Jun 2011, at 18:59, Gene wrote:
Hi Matt,
Can you please give a quick example on how to get the X-Access-Level
value. My application runs on PHP and I would like to get the X-Access-
Level for all of the users in my application and store it into a
database. I have all the keys, and tokens and everything. I am just
getting tripped up on getting that value. Thanks for your help.
Regards,
Gene
On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
A number of updates were made to the Direct Message methods and OAuth
screens at the end of last week. Here's what went out:
* force_login is now supported
onhttps://api.twitter.com/oauth/authorize
* the OAuth screens now support a feature phone tier of handsets and
render
them in a simpler format
* the language on all the screens is standardized to say direct
message
* there is a Return to App URL on the Deny and Cancel screens that
redirects the user to the oauth_callback url with a 'denied' parameter
instead of oauth_token.
This next parameter isn't needed by everybody but we will be adding
screen_name support to the authorize and authenticate pages in the next
few
days. If you want to add this to your code ready for when we release the
feature you can, but please know the screen_name parameter will be
ignored
unless you also provide the force_login parameter. The screen_name
parameter
pre-fills the username field of the OAuth screen when force_login is
true.
The user is still able to edit the field, even if it is prefilled.
Lastly, these are the main points discussed in previous emails and
Tweets:
* The new permission level will be enforced on 30th June.
* If you don't need to read or delete direct messages you do not need to
update the permission level of your application.
* Read/Write applications will still be able to send direct messages,
even
after the enforcement date.
* Existing oauth_tokens will not be invalidated, even if the application
permission level is altered.
* You can find out the current permission level of an oauth_token by
inspecting the headers of an authenticated request to the API. Look for
the X-Access-Level header.
--
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 developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
Re: [twitter-dev] A few updates about the permission model change
And this is the code I used to dump this:
$connection = new TwitterOAuth(OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
$account['access_token_key'], $account['access_token_secret']);
var_dump($connection);
On Tue, Jun 21, 2011 at 2:00 PM, Gene Ellis gene.el...@gmail.com wrote:
yep...that is what I did. This is what I received back:
object(TwitterOAuth)#1 (5) { [http_status:private]= NULL
[last_api_call:private]= NULL [sha1_method]=
object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]=
object(OAuthConsumer)#3 (3) { [key]= string(22)
Oa8K2pY7L19CLwerewVzJ5eES1A [secret]= string(42)
INoKYGcqbQqOrwerwhWuR2qUntjHx8xMDJaofc9dRkomRow [callback_url]= NULL }
[token]= object(OAuthConsumer)#4 (3) { [key]= string(50)
253725180-K6WHcDeILj3O6bikV1yC8zgYZqsrwerwdovyAJaTfyZ73 [secret]=
string(43) ENnvceX4JNbLTzTuVrwerwduATxXnFm0VRZkyNkc [callback_url]=
NULL } }
The values have been changed, but I don't see the header info. Am I missing
something?
On Tue, Jun 21, 2011 at 1:57 PM, Scott Wilcox sc...@dor.ky wrote:
var_dump the $connection object and find it in there.
On 21 Jun 2011, at 19:55, Gene Ellis wrote:
Hmmmgetting closer but I don't see the http headers in there. I even
did a var dump, but didn't see anything related to http_info. Know where
else I could look?
On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.comwrote:
I can't test to confirm at the moment but I think I set up TwitterOAuth
to include headers in the TwitterOAuth object.
If you create a TwitterOAuth object like this:
$connection = new TwitterOAuth($x, $y, $z, $a);
Then you should be able to get the headers from the most recent request
like this:
$connection-http_info;
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote:
I believe I am using the PHP Twitter libraries because I see Oauth.php
and TwitterOauth.php being included in the script. I recently took this
project over from the other developer and I am new to twitter programming,
which is why I am unsure on how to grab that access level for the users in
my database.
On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote:
Are you using any libraries?
On 21 Jun 2011, at 18:59, Gene wrote:
Hi Matt,
Can you please give a quick example on how to get the X-Access-Level
value. My application runs on PHP and I would like to get the X-Access-
Level for all of the users in my application and store it into a
database. I have all the keys, and tokens and everything. I am just
getting tripped up on getting that value. Thanks for your help.
Regards,
Gene
On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
A number of updates were made to the Direct Message methods and OAuth
screens at the end of last week. Here's what went out:
* force_login is now supported
onhttps://api.twitter.com/oauth/authorize
* the OAuth screens now support a feature phone tier of handsets and
render
them in a simpler format
* the language on all the screens is standardized to say direct
message
* there is a Return to App URL on the Deny and Cancel screens that
redirects the user to the oauth_callback url with a 'denied' parameter
instead of oauth_token.
This next parameter isn't needed by everybody but we will be adding
screen_name support to the authorize and authenticate pages in the next
few
days. If you want to add this to your code ready for when we release
the
feature you can, but please know the screen_name parameter will be
ignored
unless you also provide the force_login parameter. The screen_name
parameter
pre-fills the username field of the OAuth screen when force_login is
true.
The user is still able to edit the field, even if it is prefilled.
Lastly, these are the main points discussed in previous emails and
Tweets:
* The new permission level will be enforced on 30th June.
* If you don't need to read or delete direct messages you do not need
to
update the permission level of your application.
* Read/Write applications will still be able to send direct messages,
even
after the enforcement date.
* Existing oauth_tokens will not be invalidated, even if the
application
permission level is altered.
* You can find out the current permission level of an oauth_token by
inspecting the headers of an authenticated request to the API. Look for
the X-Access-Level header.
--
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:
Re: [twitter-dev] A few updates about the permission model change
Hi Gene,
I've added support for this into my library which I hope helps show you how
to read this information. My library is on Github:
https://github.com/themattharris/tmhOAuth
and the example with the X-Access-Level is the verify credentials one here:
https://github.com/themattharris/tmhOAuth/blob/master/examples/verify.php
Hope that helps,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Tue, Jun 21, 2011 at 12:01 PM, Gene Ellis gene.el...@gmail.com wrote:
And this is the code I used to dump this:
$connection = new TwitterOAuth(OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
$account['access_token_key'], $account['access_token_secret']);
var_dump($connection);
On Tue, Jun 21, 2011 at 2:00 PM, Gene Ellis gene.el...@gmail.com wrote:
yep...that is what I did. This is what I received back:
object(TwitterOAuth)#1 (5) { [http_status:private]= NULL
[last_api_call:private]= NULL [sha1_method]=
object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]=
object(OAuthConsumer)#3 (3) { [key]= string(22)
Oa8K2pY7L19CLwerewVzJ5eES1A [secret]= string(42)
INoKYGcqbQqOrwerwhWuR2qUntjHx8xMDJaofc9dRkomRow [callback_url]= NULL }
[token]= object(OAuthConsumer)#4 (3) { [key]= string(50)
253725180-K6WHcDeILj3O6bikV1yC8zgYZqsrwerwdovyAJaTfyZ73 [secret]=
string(43) ENnvceX4JNbLTzTuVrwerwduATxXnFm0VRZkyNkc [callback_url]=
NULL } }
The values have been changed, but I don't see the header info. Am I
missing something?
On Tue, Jun 21, 2011 at 1:57 PM, Scott Wilcox sc...@dor.ky wrote:
var_dump the $connection object and find it in there.
On 21 Jun 2011, at 19:55, Gene Ellis wrote:
Hmmmgetting closer but I don't see the http headers in there. I even
did a var dump, but didn't see anything related to http_info. Know where
else I could look?
On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.comwrote:
I can't test to confirm at the moment but I think I set up TwitterOAuth
to include headers in the TwitterOAuth object.
If you create a TwitterOAuth object like this:
$connection = new TwitterOAuth($x, $y, $z, $a);
Then you should be able to get the headers from the most recent request
like this:
$connection-http_info;
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote:
I believe I am using the PHP Twitter libraries because I see Oauth.php
and TwitterOauth.php being included in the script. I recently took this
project over from the other developer and I am new to twitter programming,
which is why I am unsure on how to grab that access level for the users in
my database.
On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote:
Are you using any libraries?
On 21 Jun 2011, at 18:59, Gene wrote:
Hi Matt,
Can you please give a quick example on how to get the X-Access-Level
value. My application runs on PHP and I would like to get the
X-Access-
Level for all of the users in my application and store it into a
database. I have all the keys, and tokens and everything. I am just
getting tripped up on getting that value. Thanks for your help.
Regards,
Gene
On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
A number of updates were made to the Direct Message methods and OAuth
screens at the end of last week. Here's what went out:
* force_login is now supported
onhttps://api.twitter.com/oauth/authorize
* the OAuth screens now support a feature phone tier of handsets and
render
them in a simpler format
* the language on all the screens is standardized to say direct
message
* there is a Return to App URL on the Deny and Cancel screens that
redirects the user to the oauth_callback url with a 'denied' parameter
instead of oauth_token.
This next parameter isn't needed by everybody but we will be adding
screen_name support to the authorize and authenticate pages in the
next few
days. If you want to add this to your code ready for when we release
the
feature you can, but please know the screen_name parameter will be
ignored
unless you also provide the force_login parameter. The screen_name
parameter
pre-fills the username field of the OAuth screen when force_login is
true.
The user is still able to edit the field, even if it is prefilled.
Lastly, these are the main points discussed in previous emails and
Tweets:
* The new permission level will be enforced on 30th June.
* If you don't need to read or delete direct messages you do not need
to
update the permission level of your application.
* Read/Write applications will still be able to send direct messages,
even
after the enforcement date.
* Existing oauth_tokens will not be invalidated,
Re: [twitter-dev] Re: User Search API
We're looking into this, thanks for the report. On Tue, Jun 21, 2011 at 11:07 AM, Amit Debnath amitdebnath...@gmail.comwrote: Thanks for answering. Now I know it isn't something I did. Doesn't look like a bug. The in-site search is now also limited to 20 results. Waiting for somebody **http://www.google.co.in/search?hl=enclient=firefox-arls=org.mozilla:en-US:officialsa=Xei=fd0AToufO8WIrAe65qH8DAved=0CCQQvwUoAQq=knowledgeablespell=1to shed some light on this. Thanks, Amit -- 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] A few updates about the permission model change
You have to make an API request first. There is no header info if a request
has not been made.
Also you need to reset your consumer key/secret.
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 12:01, Gene Ellis gene.el...@gmail.com wrote:
And this is the code I used to dump this:
$connection = new TwitterOAuth(OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
$account['access_token_key'], $account['access_token_secret']);
var_dump($connection);
On Tue, Jun 21, 2011 at 2:00 PM, Gene Ellis gene.el...@gmail.com wrote:
yep...that is what I did. This is what I received back:
object(TwitterOAuth)#1 (5) { [http_status:private]= NULL
[last_api_call:private]= NULL [sha1_method]=
object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]=
object(OAuthConsumer)#3 (3) { [key]= string(22)
Oa8K2pY7L19CLwerewVzJ5eES1A [secret]= string(42)
INoKYGcqbQqOrwerwhWuR2qUntjHx8xMDJaofc9dRkomRow [callback_url]= NULL }
[token]= object(OAuthConsumer)#4 (3) { [key]= string(50)
253725180-K6WHcDeILj3O6bikV1yC8zgYZqsrwerwdovyAJaTfyZ73 [secret]=
string(43) ENnvceX4JNbLTzTuVrwerwduATxXnFm0VRZkyNkc [callback_url]=
NULL } }
The values have been changed, but I don't see the header info. Am I
missing something?
On Tue, Jun 21, 2011 at 1:57 PM, Scott Wilcox sc...@dor.ky wrote:
var_dump the $connection object and find it in there.
On 21 Jun 2011, at 19:55, Gene Ellis wrote:
Hmmmgetting closer but I don't see the http headers in there. I even
did a var dump, but didn't see anything related to http_info. Know where
else I could look?
On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.comwrote:
I can't test to confirm at the moment but I think I set up TwitterOAuth
to include headers in the TwitterOAuth object.
If you create a TwitterOAuth object like this:
$connection = new TwitterOAuth($x, $y, $z, $a);
Then you should be able to get the headers from the most recent request
like this:
$connection-http_info;
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.com wrote:
I believe I am using the PHP Twitter libraries because I see Oauth.php
and TwitterOauth.php being included in the script. I recently took this
project over from the other developer and I am new to twitter programming,
which is why I am unsure on how to grab that access level for the users in
my database.
On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote:
Are you using any libraries?
On 21 Jun 2011, at 18:59, Gene wrote:
Hi Matt,
Can you please give a quick example on how to get the X-Access-Level
value. My application runs on PHP and I would like to get the
X-Access-
Level for all of the users in my application and store it into a
database. I have all the keys, and tokens and everything. I am just
getting tripped up on getting that value. Thanks for your help.
Regards,
Gene
On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
A number of updates were made to the Direct Message methods and OAuth
screens at the end of last week. Here's what went out:
* force_login is now supported
onhttps://api.twitter.com/oauth/authorize
* the OAuth screens now support a feature phone tier of handsets and
render
them in a simpler format
* the language on all the screens is standardized to say direct
message
* there is a Return to App URL on the Deny and Cancel screens that
redirects the user to the oauth_callback url with a 'denied' parameter
instead of oauth_token.
This next parameter isn't needed by everybody but we will be adding
screen_name support to the authorize and authenticate pages in the
next few
days. If you want to add this to your code ready for when we release
the
feature you can, but please know the screen_name parameter will be
ignored
unless you also provide the force_login parameter. The screen_name
parameter
pre-fills the username field of the OAuth screen when force_login is
true.
The user is still able to edit the field, even if it is prefilled.
Lastly, these are the main points discussed in previous emails and
Tweets:
* The new permission level will be enforced on 30th June.
* If you don't need to read or delete direct messages you do not need
to
update the permission level of your application.
* Read/Write applications will still be able to send direct messages,
even
after the enforcement date.
* Existing oauth_tokens will not be invalidated, even if the
application
permission level is altered.
* You can find out
Re: [twitter-dev] A few updates about the permission model change
boom! That was it. Thanks so much guys!
On Tue, Jun 21, 2011 at 2:27 PM, Abraham Williams 4bra...@gmail.com wrote:
You have to make an API request first. There is no header info if a request
has not been made.
Also you need to reset your consumer key/secret.
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 12:01, Gene Ellis gene.el...@gmail.com wrote:
And this is the code I used to dump this:
$connection = new TwitterOAuth(OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
$account['access_token_key'], $account['access_token_secret']);
var_dump($connection);
On Tue, Jun 21, 2011 at 2:00 PM, Gene Ellis gene.el...@gmail.com wrote:
yep...that is what I did. This is what I received back:
object(TwitterOAuth)#1 (5) { [http_status:private]= NULL
[last_api_call:private]= NULL [sha1_method]=
object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]=
object(OAuthConsumer)#3 (3) { [key]= string(22)
Oa8K2pY7L19CLwerewVzJ5eES1A [secret]= string(42)
INoKYGcqbQqOrwerwhWuR2qUntjHx8xMDJaofc9dRkomRow [callback_url]= NULL }
[token]= object(OAuthConsumer)#4 (3) { [key]= string(50)
253725180-K6WHcDeILj3O6bikV1yC8zgYZqsrwerwdovyAJaTfyZ73 [secret]=
string(43) ENnvceX4JNbLTzTuVrwerwduATxXnFm0VRZkyNkc [callback_url]=
NULL } }
The values have been changed, but I don't see the header info. Am I
missing something?
On Tue, Jun 21, 2011 at 1:57 PM, Scott Wilcox sc...@dor.ky wrote:
var_dump the $connection object and find it in there.
On 21 Jun 2011, at 19:55, Gene Ellis wrote:
Hmmmgetting closer but I don't see the http headers in there. I even
did a var dump, but didn't see anything related to http_info. Know where
else I could look?
On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.comwrote:
I can't test to confirm at the moment but I think I set up TwitterOAuth
to include headers in the TwitterOAuth object.
If you create a TwitterOAuth object like this:
$connection = new TwitterOAuth($x, $y, $z, $a);
Then you should be able to get the headers from the most recent request
like this:
$connection-http_info;
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/ | abrah.am
@abraham https://twitter.com/intent/follow?screen_name=abraham |
github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Jun 21, 2011 at 11:05, Gene Ellis gene.el...@gmail.comwrote:
I believe I am using the PHP Twitter libraries because I see Oauth.php
and TwitterOauth.php being included in the script. I recently took this
project over from the other developer and I am new to twitter
programming,
which is why I am unsure on how to grab that access level for the users
in
my database.
On Tue, Jun 21, 2011 at 1:03 PM, Scott Wilcox sc...@dor.ky wrote:
Are you using any libraries?
On 21 Jun 2011, at 18:59, Gene wrote:
Hi Matt,
Can you please give a quick example on how to get the X-Access-Level
value. My application runs on PHP and I would like to get the
X-Access-
Level for all of the users in my application and store it into a
database. I have all the keys, and tokens and everything. I am just
getting tripped up on getting that value. Thanks for your help.
Regards,
Gene
On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
A number of updates were made to the Direct Message methods and OAuth
screens at the end of last week. Here's what went out:
* force_login is now supported
onhttps://api.twitter.com/oauth/authorize
* the OAuth screens now support a feature phone tier of handsets and
render
them in a simpler format
* the language on all the screens is standardized to say direct
message
* there is a Return to App URL on the Deny and Cancel screens that
redirects the user to the oauth_callback url with a 'denied'
parameter
instead of oauth_token.
This next parameter isn't needed by everybody but we will be adding
screen_name support to the authorize and authenticate pages in the
next few
days. If you want to add this to your code ready for when we release
the
feature you can, but please know the screen_name parameter will be
ignored
unless you also provide the force_login parameter. The screen_name
parameter
pre-fills the username field of the OAuth screen when force_login is
true.
The user is still able to edit the field, even if it is prefilled.
Lastly, these are the main points discussed in previous emails and
Tweets:
* The new permission level will be enforced on 30th June.
* If you don't need to read or delete direct messages you do not need
to
update the permission level of your application.
* Read/Write applications will still be able to send direct messages,
even
after the enforcement
Re: [twitter-dev] I cannot see CAPTCHA image in the Register Application page.
Are you still seeing this behavior? If so, what geographic region are you located in? I notice you tried in several browsers but I still feel compelled to ask: do you have any plugins or browser extensions in those browsers that may be preventing the content from displaying? We're unable to reproduce this at the moment. Thanks, @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 20, 2011 at 4:28 PM, HBPark kra...@gmail.com wrote: I am trying to register a new application at https://dev.twitter.com/apps/new. But the CAPTCHA image is not seen in my browser. I have tried with Chrome, IE6, IE7, FF4... What should I do? -- 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] I cannot see CAPTCHA image in the Register Application page.
Also displays fine for me in the UK, Norway, Australia and the US. Does adblock prevent captcha's, or a similar plugin? On 21 Jun 2011, at 22:37, Taylor Singletary wrote: Are you still seeing this behavior? If so, what geographic region are you located in? I notice you tried in several browsers but I still feel compelled to ask: do you have any plugins or browser extensions in those browsers that may be preventing the content from displaying? We're unable to reproduce this at the moment. Thanks, @episod - Taylor Singletary On Mon, Jun 20, 2011 at 4:28 PM, HBPark kra...@gmail.com wrote: I am trying to register a new application at https://dev.twitter.com/apps/new. But the CAPTCHA image is not seen in my browser. I have tried with Chrome, IE6, IE7, FF4... What should I do? -- 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] Best practice for notifying users they need to re-authenticate before June 30th?
I operate a Twitter web app (GroupTweet) that effectively runs in the background once users activate it for the first time. The only reason they would need to log back into our site is to change their settings or configuration. Our app directly relies on the ability to read Direct Messages, so its crucial users re-authenticate otherwise the service will be useless until they do. We don't collect email addresses. So my question is, how are other people notifying their users about the need to re-authenticate before June 30th? Is there a way to create a script that sends @mentions to each of my authenticated users or would this be blocked due to potential for spam abuse? -- 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] Placing follow us and tweet buttons together just impossible
Hello I'm trying to put together one beside the other the new follow us button and tweet button. I simply can't. They just can't stick together. The parameter show screen name false is not hiding the @username in text, thus causing the button for follow us, to be very wide and making the other button go down one line. Tried with css, no joy. Any help please! I do have 2 twitter buttons on my page: !-- twitter --a href=http://twitter.com/share; class=twitter- share-button data-count=none data-via=example data-lang=es data- width=64 show_screen_name=falseTweet/a script type=text/javascript src=http://platform.twitter.com/ widgets.js/scripta href=http://twitter.com/example; class=twitter-follow-button show_screen_name=false data-show- count=false data-width=64 data-lang=es/a!-- fin twitter -- The problem is I don't want to show the @username because when I do, those 2 buttons doesn't fit in my nav bar. The code above works ok in Internet Explorer, but in Firefox 4, I still see the @username in text beside the image button, causing the buttons to show in 2 different lines and spoiling my layout. The data-width=64 parameter should do the trick, but is not working in firefox. How do I get only the image button? BTW I couldn't find a way to show only small custon icons instead, thus I'm trying at least to get rid the text part of username Please help! -- 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] geo_place writeable container for Indonesia
@themattharris When will I be able to geo_place places in my region (Indonesia)? Do you have time estimate on this matter? Thanks Aldian -- 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: Best practice for notifying users they need to re-authenticate before June 30th?
I think this has the potential to end up getting you blocked for spamming. You've identified a real problem with the impending OAuth change I think. Would be good to hear a recommendation directly from Twitter as to how to handle your type of situation. On Jun 21, 7:12 pm, Ryan craft.r...@gmail.com wrote: I operate a Twitter web app (GroupTweet) that effectively runs in the background once users activate it for the first time. The only reason they would need to log back into our site is to change their settings or configuration. Our app directly relies on the ability to read Direct Messages, so its crucial users re-authenticate otherwise the service will be useless until they do. We don't collect email addresses. So my question is, how are other people notifying their users about the need to re-authenticate before June 30th? Is there a way to create a script that sends @mentions to each of my authenticated users or would this be blocked due to potential for spam abuse? -- 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 to get secret key for twitter api?
Hai Shreya, u can create a dummy site in sites.google.com...and u can give this name while registering u r application... u are developing application for iphone...so u can find the libs for iphone //kamesh On Tue, Jun 21, 2011 at 11:48 AM, shreya shreya.virtuei...@gmail.comwrote: hi... i want use Twitter API in my iphone application.. but for that as i read in some discussion, first of all i need to have its secret key, and consumer key.. in that they are asking for the application website.. my iphone application is under development and it doesnot have a website.. so how can i get it? Thanks in advance.. Regards Shreya Shah -- 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] how to get secret key for twitter api?
hi kamesh, thanx for yr reply..it helped me in getting keys..thanx a lot.. Regards Shreya On Wed, Jun 22, 2011 at 10:33 AM, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Hai Shreya, u can create a dummy site in sites.google.com...and u can give this name while registering u r application... u are developing application for iphone...so u can find the libs for iphone //kamesh On Tue, Jun 21, 2011 at 11:48 AM, shreya shreya.virtuei...@gmail.comwrote: hi... i want use Twitter API in my iphone application.. but for that as i read in some discussion, first of all i need to have its secret key, and consumer key.. in that they are asking for the application website.. my iphone application is under development and it doesnot have a website.. so how can i get it? Thanks in advance.. Regards Shreya Shah -- 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
