Re: [twitter-dev] Re: rate limiting due to invalid oauth credentials
Hey Mike, Sorry to hear you were having problems there. If the credentials were being rejected we would have returned an X-Warning header in the response letting you know. There is more information about this in our rate limiting documentation: https://dev.twitter.com/docs/rate-limiting#rest Hope that helps, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Twitter, Inc. On Wed, Aug 10, 2011 at 8:50 AM, mike3s mike.3.sulli...@gmail.com wrote: Read the docs...thought the call was authenticated, but discovered that the library I was using had a bug for situations where the call included certain characters. The authentication failed, but the query continued as an unauthenticated call. No error message. Bitch of a time figuring out what was happening; had to reverse engineer the library and step through it. On Jul 4, 2:09 pm, Mo'b Mo'b mobingapapi...@gmail.com wrote: Authenticated Rate Limit --- 350 Calls per hour. Unauthenticated Rate Limit --- 150 Calls per hour. Please read the docs. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] twitter libraries
Hi Ozgur, Our list of libraries is curated from those provided to us by developers but we haven't had any OAuth compatible ASP libraries recommended to us yet. If you know of any ASP libraries let me know so we can check them out. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Twitter On Tue, Jul 12, 2011 at 1:56 AM, ozgur iamoz...@gmail.com wrote: Why not classic ASP library for oauth? -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Changed to authorizeURL; get the proper permission, but now get 401, 401 after one call
Hey oosswwaalldd,
The code you pasted above is the example auth.php file which shows how to do
each form of OAuth with the Twitter API. The method it uses when performing
the OAuth flow depends on which option you choose from the page. If you use
any of the Sign in with Twitter links you won't be able to get the direct
message permission. Instead you need to use the Allow Application options.
In a full application you would reduce all of this code to just one of those
flows.
I've added an example to my library which shows a really cut down version of
the oauth authorize flow:
https://github.com/themattharris/tmhOAuth/blob/master/examples/oauth_flow.php
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Twitter
On Tue, Jul 5, 2011 at 1:18 PM, oosswwaalldd oosswwaal...@gmail.com wrote:
Turns out I use themattharris lib to get the login credentials (token
and token_secret) which I store on my db, and Abraham lib (yours) to
interact with Twitter once I am authenticated. I know this is not you
lib but Matt Harris's, but can you help me please to know where in the
mattharris lib should I change this method? I think it would be in the
line with the -- below. Because Twitter every two days (more than
less) gives me this error when I try to get DMs with an authenticated
user [error] - no permission to access to DMS (or some like that)
when I check the users Token and Secret in my app (dev.twitter.com/
apps) they are different than the ones stored on my db. I appreciate
you help a lot.
// start the OAuth dance
} elseif ( isset($_REQUEST['signin']) || isset($_REQUEST['allow']) ) {
$callback = isset($_REQUEST['oob']) ? 'oob' : $here;
$code = $tmhOAuth-request('POST', $tmhOAuth-url('oauth/
request_token', ''), array(
'oauth_callback' = $callback
));
if ($code == 200) {
$_SESSION['oauth'] = $tmhOAuth-extract_params($tmhOAuth-
response['response']);
$method = isset($_REQUEST['signin']) ? 'authenticate' :
'authorize'; -- HERE SHOULD I WRITE $METHOD='authorize'; RIGHT?
$force = isset($_REQUEST['force']) ? 'force_login=1' : '';
$forcewrite = isset($_REQUEST['force_write']) ?
'oauth_access_type=write' : '';
$forceread = isset($_REQUEST['force_read']) ?
'oauth_access_type=read' : '';
header(Location: . $tmhOAuth-url(oauth/{$method}, '') . ?
oauth_token={$_SESSION['oauth']['oauth_token']}{$force}{$forcewrite}
{$forceread});
}
On Jul 5, 3:55 pm, Abraham Williams 4bra...@gmail.com wrote:
You don't need to change the TRUE to FALSE in twitteroauth.php you pass
FALSE as the second parameter when you call the getAuthorizeURL method.
This
is only used when a (generally) unauthenticated user gets redirected to
twitter.com with a request token to allow access to their account. For
all
existing users they will have to do this again before the access tokens
will
have DM access.
In the example code this is done in line 22 of redirect.phphttps://
github.com/abraham/twitteroauth/blob/master/redirect.php#L22
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, Jul 5, 2011 at 14:58, oosswwaalldd oosswwaal...@gmail.com
wrote:
I am little bit confused, I understood that the problem was solved by
changing to FALSE in this line
function getAuthorizeURL($token, $sign_in_with_twitter = TRUE) {
in twitteroauth.php, but I am reading from you that the change is not
in this file.
In my code the only call I have to authorize/authenticate is this
(main file where I process the DMs, this file requires
twitteroauth.php)
/* Create a TwitterOauth object with consumer/user tokens. */
$connection = new TwitterOAuth($consumer_key,$consumer_secret,
$oauth_token,$oauth_token_secret);
where am I supposed to change this FALSE?
Thanks for the help
On Jul 5, 12:45 pm, Abraham Williams 4bra...@gmail.com wrote:
You don't need to change the code in twitteroauth.php. You just use
$connection-getAuthorizeURL($token, false) to get the authorize URL
instead
of the authenticate URL.
If you are having other issues it is likely unrelated to this change
as
the
only difference is sending users to
api.twitter.com/oauth/authorizeinstead
of api.twitter.com/oauth/authenticate. If you can make one call then
you
are
likely either not properly saving the access token in sessions/db or
you
are
overwriting it with a new request token at some point.
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 Mon, Jul 4, 2011 at 19:59,
Re: [twitter-dev] lists.json API call ignoring the callback parameter as of the last few hours
Hey Tim, This should now be fixed. Let us know if you find it isn't. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Twitter On Tue, Jul 5, 2011 at 12:59 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Harshad, We hope to have a fix for this bug out next week, sorry for the inconvenience in the meantime. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 5, 2011 at 10:44 AM, Harshad RJ harshad...@gmail.com wrote: Hi Taylor, Any updates on this issue? tDash users are not able to read their lists because of this. thanks, Harshad On Sat, Jul 2, 2011 at 12:24 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks everyone, I'll report this to the team -- not quite sure what's happening. Just to set expectations, I also don't have an ETA on a fix. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary -- 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-dev] New permission level enforcement happens this Thursday (30th June)
Hey everyone,
Just a quick reminder that we'll be enforcing the new permission level this
Thursday, 30th June.
When we enforce the new permission level Read (R) and Read Write (RW)
access tokens will be unable to use the following API methods:
/1/direct_messages.{format}
/1/direct_messages/sent.{format}
/1/direct_messages/show.{format}
/1/direct_messages/destroy.{format}
Any requests made to those endpoints with R or RW tokens will receive an
HTTP 403 Forbidden error with the response body:
{errors:[{code:93,message:This application is not allowed to
access or delete your direct messages}]}
Some key points
* If you do not need to read or delete a user's direct messages you do not
need to do anything. You can always ask a user to reauthorize at a greater
permission level.
* Existing tokens will still work but only those with Read, Write, and
Direct Messages access will be able to read and delete direct messages.
* Read Write access tokens can still send direct messages.
* You can verify the permission level of the token you are using by
inspecting the X-Access-Level header. This header is included when a
successful OAuth request is made to the API.
* When a user reauthorizes your application at the Read, Write, and Direct
Messages (RWD) level, the oauth_token returned by the
https://api.twitter.com/oauth/access_tokenrequest will be different than the
one you already have. This is because we issue new tokens whenever the
permission level is changed. If the permission level is the same the token
is not recreated, e.g. you have an RWD token and you ask the user to
reauthorize at RWD level, you will get the existing token back. If you have
an RW token and you ask the user to reauthorize at RWD level, you will get a
new token back.
Recently there was a question on the mailing list about how to inform users
of the new permission level. Ultimately the method you choose is up to you
and the opportunities and information your application or service provides.
Some applications would prefer to be proactive, whilst others can be
reactive. Which your preferred approach below are a a few suggestions we
have seen or heard other developers will do:
* On your first attempt to read direct messages that responds with an error,
display a helpful message indicating the application cannot read the direct
messages until the user has reauthorized.
* On their first use of your updated application or service, prompt them to
reauthorize.
* If you know the email address of the users of your app send a message
about the new permission and link to our blog post (
http://blog.twitter.com/2011/05/mission-permission.html)
* Send a Tweet as the account that represents your application. This Tweet
can let users know an update is available for the application to accomodate
the new permission level on Twitter.
* Add a blog post on your application or services homepage about the new
permission level and what it means for your applications.
* Prepare a support response or FAQ entry that you can give to users if they
contact you saying they cannot access their direct messages anymore
In case you missed any of the previous emails or questions we've compiled an
overview page and FAQ on our developer resources site:
* https://dev.twitter.com/pages/application-permission-model
* https://dev.twitter.com/pages/application-permission-model-faq
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
--
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] Pixelated Avatar and Twitter Logo
Hi Robert,
You website stylesheet includes this rule:
#home_main_right img {
width: 150px;
height: 150px;
}
This rule is telling the webpage to render the img's at the 150x150
resolution and is the reason for the images in the widgets being pixelated.
To resolve the issue you should restrict the scope of that CSS rule by
adding something like a class on the img you want to be 150x150
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Tue, Jun 28, 2011 at 11:58 AM, Robert Winnett winnett2...@gmail.comwrote:
Hello,
Does anyone know why I am getting pixelation on my website with the
integrated Twitter Feed?
www.bucycling.com
Please help.
-Robert
--
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] Can't Get OAuth To Work On My Site
Hi David, Can you explain a little more about your setup and what you mean when you say it isn't working. For example: * What language are you using? * Are you using a library? * How far in the process does the OAuth flow get? * Are you seeing any error messages in your code or logs? If you can share this information we'll be able to provide some guidance on what to do. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 3:35 PM, David glk.da...@gmail.com wrote: Hi, I was wondering if anyone could help me? If you go to jesusay.com and click login you'll see the Twitter Oauth button... Can someone test it and maybe tell me what I'm doing wrong? It doesn't work. 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] Search API for getting tweet counts by date?
Hi, The Search API only keeps it's index for about a week so searches older than that are not possible. To perform analysis of Tweets like you ask you will can monitor them as they happen through the Streaming API. Alternatively some third party services maybe able to offer this information. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 7:45 PM, jburke jmbu...@gmail.com wrote: If I want to get tweet counts (for a particular query) by date over a particular date range, does the search API support? Is the date range limited to the tight range that is in place for search that returns tweets? -- 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: SOLVED Re: [twitter-dev] Needs object from desktop application ?
Hey Ari, It's great to hear you worked this out and got it working. Also, thank you for sharing the solution that worked for you. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter 2011/6/23 Ari Endo arien...@gmail.com ** Dear Matt, Your question solved my problem. Actually, the signature itself and signature part in authorization header were different! I have urlencoded the signature and again urlencoded the authorization header. As a result, signature was urlencoded twice which came different from once urlencoded signature. I have been thinking it makes no harm urlencoding many times, but it was not. By urlencoding authorization header except the signature part, I have got 200 OK. Thank you so much for your kind support. Say thank you to Tom as well. As I am a newcomer to twitter application development, please help me again when I might come across other troubles ahead. Sincely, Ari Endo Matt Harris wrote (2011/06/24 9:21): Hi Ari, I'm not familiar with VBA enough to comment on the code, but if you could provide an example of the basestring created, authorization header and signature (remember to exclude any secrets) then we can take a look at what could be going wrong. Best, @themattharrishttps://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter 2011/6/23 Ari Endo arien...@gmail.com Dear Tom, Here is my vba code, just for your information. It returns 401 Unauthorized, Failed to validate oauth signature and token I appreciate if you give me a hint. - Private Sub cbRequestToken_Click() Const urlRequestToken As String = https://api.twitter.com/oauth/request_token; Const oauth_consumer_secret As String = (my consumer secret) Dim timestamp As Long Dim strBase As String timestamp = DateDiff(s, #1/1/1970#, DateAdd(h, -9, Now)) Dim param As New Scripting.Dictionary (hash array) param(oauth_callback) = oob param(oauth_consumer_key) = (my consumer key) param(oauth_nonce) = CStr(timestamp + 1) param(oauth_signature_method) = HMAC-SHA1 param(oauth_timestamp) = CStr(timestamp) param(oauth_version) = 1.0 strBase = POST urlEncode(urlRequestToken) urlEncode(sortedParamConnected(param)) param(oauth_signature) = urlEncode(hmac_sha1(oauth_consumer_secret , strBase)) Dim strHeader As String strHeader = OAuth Dim i As Integer For i = 0 To param.Count - 1 strHeader = strHeader param.Keys(i) = urlEncode(param.Items(i)) If i param.Count - 1 Then strHeader = strHeader , Next Dim xmlhttp As New MSXML2.xmlhttp xmlhttp.Open POST, urlRequestToken, False xmlhttp.setRequestHeader Authorization, strHeader xmlhttp.send If xmlhttp.statusText OK Then Exit Sub End Sub There are several Excel VBA application which can be authenticated. The point is they make a twitter class and make an object to access. I am developing without using class (object-oriented). 1. my time is correct (UTC) 2. my signature is correct (compared with the sample in twitter documentation) 3. when URL is https://api.twitter.com/1/, 404 Not found came back Thank you in advance, Ari Tom van der Woerdt schrieb (2011/06/11 9:21): A desktop authentication flow usually includes a callback with a custom scheme (myapp://redirect) or xAuth, while a server application will usually use a normal callback (http://example.com/callback) with the normal OAuth flow. However, this won't cause the Woah there! error you get. Just like anything else related to the programming itself: Twitter doesn't discriminate by programming language. As long as you are using the API correctly, it's fine. To answer your initial question: you can use C (non-object oriented language) and C++ (object-oriented language) and many other languages to interface with Twitter. It's an API, so it's all the same, as long as you can make a HTTP request. Tom On 6/11/11 2:17 AM, Ari Endo wrote: Dear Tom, Thank you for your quick support. I have checked all the items you listed below. What I would like to know is information for desktop application different from server application. I would appreciate if you tell me any. Thank you in advance, Ari Tom van der Woerdt さんは書きました (2011/06/10 17:50): I just checked and I was wrong - Woah there! can mean a lot of thnigs. 1. Make sure that your time is right 2. Make sure that the signature you make is right 3. Make sure that your endpoint starts with https://api.twitter.com/1/ 4. Make sure that you use valid credentials 5. Make sure that you are supplying all the required parameters 6. Make sure that your nonce is correct 7. Make sure everything else
Re: [twitter-dev] Tweets not appearing properly from our app.
Hi, It sounds like you are seeing the effects of our caches updating. This can sometimes happen but shouldn't be as apparent. Are you request xml, json or both when you are performing these checks. I'm not familiar with the platform your application is working on but if the short caching propagation window is an issue for you I recommend looking at the Streaming API. The Streaming API will deliver the Tweet to you in the quickest time possible. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 1:13 PM, 900 900secondsoff...@gmail.com wrote: Hi, We are having a problem with our application. When I tweet, the function statuses/user_timeline does not fetch tweets accurately. For instance, if I tweet something, the tweet won't appear for approximately one minute. It then intermittently appears and disappears. After a few minutes it appears properly. Any suggestions, links, or advice? 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] How to autologin to twitter by providing the username and password using API?
Hi Karthikeyan, In our Terms of Service ( http://dev.twitter.com/pages/api_terms ) we say that a Service should not replicate, frame, or mirror the Twitter website or its design. In addition, automating the login to twitter.com isn't something you should be doing or are allowed to do. Instead you should use the Twitter APIs to provide interactivity with Twitter. What actions would like people to be able to do inside you application? If you can provide some examples of what you would like users to be able to do, we can make recommendations on the API methods to use. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 9:40 PM, Karthikeyan P karthivis...@gmail.comwrote: For example i have custom twitter icon in my application and when i am adding this icon to the application, i have also added the www.twitter.com, username,password. So when i am clicking the icon it takes me to the twitter site and auto fills the username and password. and logins and shows me the home page on my AIR HTML browser. This is the content to show in the application. -- 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] all xauth access token revoke after oauth
Hi Shinichi, I don't quite follow your question but I think the following information is close to what you are asking about. When you take a user through the OAuth flow we do one of three things. 1. If the user has not authorized your application before a token at the requested permission level will be granted. 2. If the user has already authorized your application, and the permission level being requested has not changed, the existing token will be left unchanged and returned. 3. If the user has already authorized your application, but the permission level being requested is different to the one they already allowed, we will destroy the old token and create a new one at the new permission level. For xAuth and applications with Read, Write, Direct Messages (RWD) this means a couple of things. 1. Performing xAuth before the user has been through the OAuth flow will mean the original RW token will be destroyed and a new RWD one will be created. 2. Performing xAuth after the user has been through the OAuth flow will mean the RWD token is maintained. We do this to ensure applications which use xAuth do not bounce between RW and RWD tokens. To illustrate this consider a Read, Write, Direct Messages application which uses both xAuth and OAuth. In this example assume the user hasn't used the application before. 1. The application prompts the user to login with xAuth. 2. The application performs xAuth and receives a Read Write token and secret (RW). 3. The application now asks the user to update their authorization to allow reading of direct messages. 4. The application starts the OAuth flow and takes the user to https://api.twitter.com/oauth/authorize?oauth_token=abc123 5. The user accepts the RWD request and is redirected to the callback URL. 6. The application receives the callback and completes the OAuth flow to receive a new RWD token and secret. This token is different to the one issued during the xAuth flow. 7. Now the user goes to a secondary device to authorize their account on the same application 8. The application prompts the user to login with xAuth. 9. The application performs xAuth and receives the same RWD token and secret issued in step 6. This is because the user has already authorised the application for RWD access to their account. I hope that answers your question and explains what is going on when you mix xAuth with OAuth. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 9:58 PM, Shinichi Fujikawa fshin2...@gmail.comwrote: Hello! Was the problem that all access token of the xauth does revoke with the same consumer key after re-login oauth corrected today? It is different from yesterday's operation. -- Shinichi Fujikawa http://movatwi.jp -- 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] Poor documentation. For example, regarding lists. Suggestions for improvement.
Hi Denzil,
Thanks for the suggestion. Do you think that would help or would it be
better to try and link to the console? Just curious about alternative ideas.
The reason I say this is POST and DELETE requests are difficult to write as
single example URLs. When we had them in the past they led to confusion with
OAuth signing.
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Fri, Jun 24, 2011 at 1:42 AM, Correa Denzil mcen...@gmail.com wrote:
Matt :
I suggest in the Example Requests you add the URL for the call. It will
prevent much of the What URL to call? queries.
--Regards,
Denzil
On Fri, Jun 24, 2011 at 4:55 AM, Matt Harris thematthar...@twitter.comwrote:
Hi Dave,
Thanks for your feedback, it's important for us to know when developers
are not finding the information they are looking for.
I have responded to your specific points inline:
Issue #1: Valid version numbers
I was unable to locate valid values for version. I tried 1.1.14,
which I understand the current version to be from searching the site,
but that causes a 404. It was only after digging around for examples
that I noticed people using 1. A page describing valid version
numbers should be linked from the word version.
In the API documentation there is a version place marker in the example
request URL. Currently only one version of the API exists, that version is
1. This means any REST API queries will be of the format:
https://api.twitter.com/1/statuses/user_timeline.json
I've updated the API FAQ and Things Every Developer Should Know pages
to include this information.
http://dev.twitter.com/pages/every_developer
https://dev.twitter.com/pages/api_faq
Issue #2: Extremely unclear parameter passing
As this call uses GET, and the documentation lists parameters you
should include, this implies to me that you should use a query string.
The docs list the following required parameters:
* list_id - The numerical id of the list.
* slug - You can identify a list by its slug instead of its numerical
id. If you decide to do so, note that you'll also have to specify the
list owner using the owner_id or owner_screen_name parameters.
As it is not at all obvious how you discover the list_id or
owner_id, I opted to use slug and owner_screen_name. However, if
you
$ curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
you get
{error:You must specify either a list ID or a slug and
owner,request:\/1\/lists\/statuses.json?owner_screen_name=cnn}
Notice that the response json lists the request with only the
owner_screen_name parameter. I imagine that 1 or more things went
wrong, possibly including:
1. The API has a bug that is stripping the second parameter
2. The documentation is incorrect, and you may not use slug and
owner_screen_name to retrieve results.
3. The documentation does not properly describe how you pass the
arguments in the query string. Perhaps you're supposed to encode the
entire string. I was not able to discern this.
4. The documentation is incorrect about the url format.
The request you are making is correct. The error is instead being caused
by the way in which you are using your terminal. When using a terminal like
this you need to remember to either quote your URL or escape the 's.
This would make your request look like this:
curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
Issue #3: No obvious way to discover list_id or owner_id
user_ids are provided in all API responses which include a user object.
The most common way of getting information about a user is through the
users/show method or users/lookup method:
http://dev.twitter.com/doc/get/users/show
http://dev.twitter.com/doc/get/users/lookup
list_id is available from the index of lists for a user. This request is
the /1/lists request:
http://dev.twitter.com/doc/get/lists
Alternatively, if those values are unknown or you don't wish to look them
up, you can provide the slug and screen_name as you have done in your
example.
Issue #4: Undocumented, un-obvious correct url
I was finally able to retrieve the results using this url, pieced
together from scattered examples.
$ curl http://api.twitter.com/1/cnn/lists/cnnnews/statuses.json
So far as I could tell, the documentation in no way implies that you
could use such a url.
This is the deprecated way of making lists requests. It is documented on
this page of the developer resources site:
http://dev.twitter.com/doc/get/:user/lists/:id/statuses
I hope that helps explain a little bit more about the API. Let me know if
this information is useful or what you would change and we'll see how we can
incorporate it into the docs.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
--
Twitter developer
Re: [twitter-dev] User suggestions and User Suggestions Twitter
Hi Denzil, The suggested user methods return a list of @names which we think users interested in a topic may be interested in following. As the name implies, these are just suggestions. Example calls for both: http://api.twitter.com/1/users/suggestions.json Returns all of the suggested user categories, including slugs. An example response and more information about the method is here: https://dev.twitter.com/doc/get/users/suggestions http://api.twitter.com/1/users/suggestions/twitter.json Returns some suggested accounts to follow related to the twitter category. twitter in this case is the :slug referred to in the documented URL on this page: https://dev.twitter.com/doc/get/users/suggestions/:slug Hope that answers your questions, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 1:50 AM, Correa Denzil mcen...@gmail.com wrote: Hi, I am unable to understand the API for user/suggestionshttp://dev.twitter.com/doc/get/users/suggestionsand user/suggestions/twitterhttp://dev.twitter.com/doc/get/users/suggestions/:slug resources. It would be great if you highlight two particular aspects : 1. What do these API calls signify? 2. Example calls for both of these API resources Thanks, --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 -- 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 widgets not using entities to present t.co links
Great, thanks Tim. @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 3:08 AM, Tim Meadowcroft meer...@gmail.com wrote: Thanks Matt, filed as a feature request rather than a defect http://code.google.com/p/twitter-api/issues/detail?id=2250 -- 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 error
Hi Sreejata,
Thanks for providing this information. Are you able to find out what the
server is actually sending to the Twitter API. The code you've provided
shows where the error is happening but not what information is being sent to
the API.
Without knowing what is being sent by your code it is hard to suggest
possible causes for the problem.
Do you know which OAuth library are you using?
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Fri, Jun 24, 2011 at 5:51 AM, Sreejata Chatterjee gundad...@gmail.comwrote:
Matt! Thank you SO much for the reply... I will try and explain what else I
found out. A test example is:
?php
define( CONSUMER_KEY,* );
define( CONSUMER_SECRET, );
$oauth = new
OAuth(CONSUMER_KEY,CONSUMER_SECRET,OAUTH_SIG_METHOD_HMACSHA1);
$access_token = file_get_contents(access_token);
$access_token_secret = file_get_contents(access_token_secret);
$oauth-setToken($access_token, $access_token_secret);
$url = http://api.twitter.com/1/statuses/home_timeline.xml;;
$oauth-fetch($url);
$json = json_decode($oauth-getLastResponse(),true);
print_r($json);
?
Now, I tried this script and the same user (@Research4SML) from 3 different
servers. The results are:
CentOS, PHP 5.2.17, and Ubuntu, PHP 5.3.2:
PHP Fatal error: Uncaught exception 'OAuthException' with message
'Invalid auth/bad request (got a 400, expected HTTP/1.1 20X or a redirect)'
in /var/www/vhosts/default/iresearch/Scholar/oauth/test.php:14
Stack trace:
#0 /var/www/vhosts/default/iresearch/Scholar/oauth/test.php(14):
OAuth-fetch('http://api.twit...')
#1 {main}
thrown in /var/www/vhosts/default/iresearch/Scholar/oauth/test.php on
line 14
From another CentOS machine, PHP 5.2.10, IT WORKS! (Of course I had to
generate new tokens for every server).
I did the curl http://api.twitter.com/1/account/rate_limit_status.xml;
call from all the servers and there is no rate limiting affecting the
results. I need it to work from the CentOS, PHP 5.2.17 machine.
What might be the reason behind this behavior and how can I fix it?
On Thu, Jun 23, 2011 at 6:06 PM, Matt Harris thematthar...@twitter.comwrote:
Hi,
A 400 error indicates something in the request you are making is
malformed. Are you using a library to make requests or did you create your
own wrapper?
If you created your own library for making requests you may instead want
to try one of the libraries listed on our developer resources site:
http://dev.twitter.com/pages/libraries
Moving forward, to help identify the cause of the 400 could you share the
the request header and URL you are sending and the API headers and response
body returned. Remember to remove any OAuth secrets from the code you share.
Best
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Mon, Jun 20, 2011 at 12:39 PM, antiphobe gundad...@gmail.com wrote:
The time was in sync and I still used ntpd to reset it. No use.
I tried to use the same script on different server, same user - 400
error (bad request)
Tried on new server, different user, same script - it works!
So I'm lead to believe something might be wrong with the twitter user
a/c? Is that known to happen?
--
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
--
Sreejata
~~
MagicLamp Software Solutions Inc.
Halifax, Nova Scotia
902-482-7103, 902-448-6357
http://www.magiclampsoft.com
--
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] Search Api limit
Hi Alessandro,
We've produced a small guide on using search that explains the search rate
limits a little more.
You can find the page here:
https://dev.twitter.com/pages/using_search
In it we say:
The Rate Limits for the Search API are not the same as for the REST API.
When using the Search API you are not restricted by a certain number of API
requests per hour, but instead by the complexity and frequency.
As requests to the Search API are anonymous, the rate limit is measured
against the requesting client IP.
To prevent abuse the rate limit for Search is not published. If you are rate
limited, the Search API will respond with an HTTP 420 Error. {error:You
have been rate limited. Enhance your calm.}.
I hope that explains what is going on,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Fri, Jun 24, 2011 at 2:08 AM, Alessandro alessandro.marrone...@gmail.com
wrote:
Hi
I'm using the search api (for example:
http://search.twitter.com/search.rss?q=%23juventusrpp=100page=4)
I read here: http://search.twitter.com/api/ this:
We do not rate limit the search API under ordinary circumstances,
however we have put measures in place to limit the abuse of our API.
If you find yourself encountering these limits, please contact us and
describe your app's requirements.
The limit seems random: sometimes I do 150 requests sometimes 300,
generally, after 5 minutes I can do other requests.
I was wondering if is it possible do more requests
--
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] Get Twitter Statuses based on a timestamp
Hi Shashank, The Twitter REST API doesn't allow you to restrict the date returned by date or time but we do allow you to provide a since_id and max_id. If you know the ID of a Tweet that happened after the maximum timestamp you are interested in you could pass it as max_id. Alternatively, if you want to look at data that happened in the last few days you can use the until parameter of the search API. More information about that parameter can be found here. http://dev.twitter.com/doc/get/search One other way you could do this is to monitor Tweets as they happen. By using the Streaming API you can open a connection before the event/time you are interested in, and then close the connection when you don't want any more. To restrict Tweets to one user you can use the filter method and follow one user ID. More information about the Streaming API is here: http://dev.twitter.com/pages/streaming_api Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 1:44 AM, Shashank cooldude17202...@gmail.comwrote: Hi Guys, I am new to use twitetr api, but managed to understand it to some extent. But here i am stuck in some problem, i want to get user status updates, but not all updates. I want a way to just provide a timestamp, and let the twitter api get statuses done by the user till that particular timestamp. Hope i am able to explain my problem clearly. Can anyone tell me a way of how to do this?? Thanks in advance. Shashank Singh -- 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] To Get Twitter Follower list
Hi Abhishek, It looks like you are using a particular library to make requests. I'm not familiar with which library it is or how it works. From the Twitter API point of view the request the library should be making is the followers/ids method. This is documented on our developer resources site: http://dev.twitter.com/doc/get/followers/ids Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 12:10 AM, Abhishek mehta abhishekmehta.virtuei...@gmail.com wrote: hi I am trying to get Twitter Follower list using the following methog [_engine getFollowersIncludingCurrentStatus:YES]; but this method when i am printing result on console i am getting the following result 42EAC3DE-2B8A-4C04-84E2-912460060C75 but i need a follower list name when i log in twitter using my login id and password thanks in Advance With Regards Abhishek -- 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: Update status d returns success response but doesn't show up on web
Hi, This is expected behavior and is caused by the SMS commands. You can find a complete list of the commands and their aliases on our help site: https://support.twitter.com/entries/14020-official-twitter-text-commands Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 3:40 PM, R r4eem...@gmail.com wrote: 'w' is another On May 13, 10:34 am, e.p.c. epcoste...@gmail.com wrote: On May 13, 6:29 am, SN Testing sngtwt...@gmail.com wrote: when update status with one character d returns success response but the new status doesn't show up on web; when update status with a or b or c or e, it shows up on web, so the character d is black listed? d' as the first non-blank byte is the command/code for direct message. -- 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: error 401 from oauth, starting a few days ago
Thanks. I was asking about the code as Taylor made a few suggestions about issues with your code. I was wondering if you had implemented them yet. In particular have you updated your URLs to use the correct domain with the /1 included. For example: http://api.twitter.com/1/statuses/user_timeline.xml and have you removed the oauth_token_secret from your authorisation header? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 9:25 AM, arlomedia a...@arlomedia.com wrote: The response body only includes the text of the error message (This method requires authentication) and a copy of my request URI. I included my complete request including all headers in an earlier post in this thread; is that what you meant by authorization header/ parameters? -- 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] Twitter Search API - completeness
Thanks for highlighting this typo. I've updated that page so it should be correct now. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 10:58 AM, Kstolen Kstolen kstole...@gmail.comwrote: The Twitter Search API docs (http://dev.twitter.com/pages/ using_search#) say: Search is focused in relevance and not completeness. This means that some Tweets and users may not be missing from search results. If you want to match for completeness you should consider using the Streaming API instead. Should this be : This means that some Tweets and users may be missing from search results. ? That would seem to make more sense. -- 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] Can't Get OAuth To Work On My Site
Hi David, Thanks for asking. It's fine to send me the file. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 2:06 PM, David Moore glk.da...@gmail.com wrote: I took it off the site for now, but the site is php... It was acting like it was going to let me register with Twitter, I verified my account and allowed it... but when it returned to my site nothing happened. It didn't login or make a new account like it was supposed to. After that it started to say that my token was used already. Can I send you the file I use for my Twitter Oauth? Thanks. On Fri, Jun 24, 2011 at 12:31 PM, Matt Harris thematthar...@twitter.comwrote: Hi David, Can you explain a little more about your setup and what you mean when you say it isn't working. For example: * What language are you using? * Are you using a library? * How far in the process does the OAuth flow get? * Are you seeing any error messages in your code or logs? If you can share this information we'll be able to provide some guidance on what to do. Best, @themattharrishttps://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 3:35 PM, David glk.da...@gmail.com wrote: Hi, I was wondering if anyone could help me? If you go to jesusay.com and click login you'll see the Twitter Oauth button... Can someone test it and maybe tell me what I'm doing wrong? It doesn't work. 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 -- Seek God's mercy and you'll find it - www.GodsMercy.net -- 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] Deleting Extra Callback URLs
We've had reports of this in the past but haven't been able to track down the exact cause. Could you send me the application ID which is exhibiting this problem so I can give the engineers an active example. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 3:43 PM, DustyReagan dustyrea...@gmail.com wrote: I can't seem to delete any of my apps extra callback URLs at dev.twitter.com. I just get an error that says: Sorry, a temporary error occurred. Please try again later. I've tried again later, and the problem persists. Anyone else having this problem? -- 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 home time line in TWITTER works?
Hi Grace, Be default the API returns the most recent Tweets/ReTweets created by users being followed by the authenticating user. When you pass a since_id to the home_timeline method this means the API will return to you the 20 most recent Tweets created since that ID. What this means is you won't necessarily find the Tweet with an ID equal to since_id being returned in your request. To go further back in time you must also pass a max_id with the request. This changes the API request from: All Tweets in the home timeline since since_id to All Tweets in the home timeline created since since_id and up to max_id A few examples may help demonstrate this. In all cases assume the timeline contains Tweets with IDs 1 to 1000, and that count for our requests will always be 20. Request: /1/statuses/home_timeline.json?since_id=1 Response: Tweets 1000 to 980. Request: /1/statuses/home_timeline.json?since_id=900max_id=1000 Response: Tweets 1000 to 980. Request: /1/statuses/home_timeline.json?since_id=900max_id=950 Response: Tweets 950 to 930. Request: /1/statuses/home_timeline.json?since_id=1max_id=50 Response: empty -- this is because home_timeline only has access to the last 800 Tweets Request: /1/statuses/home_timeline.json?since_id=200max_id=250 Response: Tweets 250 to 230. Hope that helps, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 15, 2011 at 11:15 PM, Grace ptyad...@gmail.com wrote: hello everyone.. I try to get tweets from user's home using home method. http://api.twitter.com/version/statuses/home_timeline.format If I use paging and set as the following.. Example. paging.setSinceId(09L); What would be the expected result returned from API ? in my home, there will be like following tweets. 50( The most recent one) 40 39 . 23 22 21 20 .. 13 12 11 10 .. 03 02 01 ** Actually, I should receive Tweets ( 10 to 20 ) . right? but, when I called the API, it seems like the returned result is ( 30 to 50). Is it the correct way of working API ? or do I miss something? If I want to get Tweets ( 10 to 20 ) , how can I do it? Regards, Grace -- 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] Search widgets on both my sites suddenly stopped working
Hi Zippy, The search index is limited in how far back it can go. What this means is if the hashtag you are searching for hasn't been used in the last week there won't be any results returned. In addition, not all Tweets are indexed by the Search API. This is explained a little more in our user support article: https://support.twitter.com/groups/32-something-s-not-working/topics/118-search-problems/articles/66018-i-m-missing-from-search Have the hashtags you are tracking been used recently? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 16, 2011 at 8:38 AM, Zippy rgrigo...@gmail.com wrote: I used Twitter's own Search widget code generator to build search widgets for two of my sites, InterestingAmerica.com and HightPerformanceDataCenters.com to pick up messages tweeted from the sites using their respective hashtabs (#IntAm and #hpdcnews). (take a look -- they are on the right side of all of the pages) A few days ago, however, the boxes on all of the pages stopped picking up new tweets. Strangely, when I go back to the Twitter Search widget code generator and build new ones and trial test them right there, they still don't pick up #IntAm or #hpdcnews. Perhaps the whole twitter stream doesn't like my hashtags...? -- 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 autologin to twitter by providing the username and password using API?
Hi Karthikeyan, The Twitter API doesn't provide a way for an application to log a user into Twitter.com. What information are you wanting to provide to the users of your application? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 16, 2011 at 10:02 PM, Karthikeyan P karthivis...@gmail.comwrote: Thanks Scott Wilcox for your information, I want to achieve the following using oauth twitter API or xauth... or some script 1) I have an icon(twitter) in my air application which has some background details like url(www.twiiter.com) , username , password. 2) if i click the twitter icon, i want the twitter site to login automatically and to be rendered on my AIR browser(webkit) . 3) It can be anything like Twitter API or some script which does the login mechanism. I am stuck with this , How do i login to twitter using auto login.. I am looking at the oauth but i can get only the data in the respective twitter account, I dont want the data , I want it to be logged in and redirect it to the home page. This is the flow i want to achieve in my application.. can anyone help me on this.. thanks in advance. -- 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: error 401 from oauth, starting a few days ago
Hi Arlo, When an error is returned by the API we include some information about the cause in the response body. Take a look at that response body and see if that helps you resolve the problem. If not, let us know what the error says and what your OAuth basestring and authorization header/parameters are. Remember to remove your oauth and consumer secrets though. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 17, 2011 at 8:07 AM, arlomedia a...@arlomedia.com wrote: Just giving this a bump for Taylor. For anyone else, does the oauth-php example script work with your accounts? It works for me when accessing the public timeline as shown in the example, but if I change the request URL to access my user timeline (protected or unprotected) I get the authorization error. It would be helpful to know if the problem is with my account, the example script, or the oauth-php library. -- 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] Post small text link to twitter from my site
Hi Santanu,
The example code you have posted below makes use of basic authentication
(username and password). The Twitter API hasn't support this method of
authentication for a while and instead requires developers to implement
OAuth.
We have some guidance about how to make this transition on our developer
resources site:
http://dev.twitter.com/pages/basic_to_oauth
You may also find our single user token example helpful:
http://dev.twitter.com/pages/oauth_single_token
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Thu, Jun 16, 2011 at 11:33 PM, earth technology 8
earthtechnolo...@gmail.com wrote:
Hi All,
I have a news site. I want that when I post any news from my site, the
news title (small text) and my site link automatically posted on my
twitter account.
I got below codes in internet, but the codes did not work. Please see
this
-
?php
$username = twitter_username;
$password = twitter_password;
$message = 'a href=DOMAIN_NAMESmall News Text/a';
$url = 'http://twitter.com/statuses/update.xml';
$curl_handle = curl_init();
curl_setopt($curl_handle, CURLOPT_URL, $url);
curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl_handle, CURLOPT_POST, 1);
curl_setopt($curl_handle, CURLOPT_POSTFIELDS, status=$message);
curl_setopt($curl_handle, CURLOPT_USERPWD, $username:$password);
$buffer = curl_exec($curl_handle);
curl_close($curl_handle);
if (empty($buffer)) {
echo p align=\center\ .'Sorry, due to an error your Twitter
status could not be updated! Please check your username/password!'./
p;
} else {
echo p align=\center\.'Your Twitter status has successfully
been updated!'./p;
}
?
-
If there is any API or PHP script, please send me. Waiting for reply
Best Regards,
Santanu
--
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] Getting 401 errors trying to send direct message
Hi Chris, On our developer resources page you can find some libraires which handle this process for you. You may find these a helpful reference to see how others have implemented the OAuth specification. The libraries are at this link: http://dev.twitter.com/pages/libraries The 401 error can be returned for a couple of reasons. The response body the API returns contains more information about the cause of the error. Often this reason is enough to be able to know what action is needed in your code. To answer your questions: - From what I understand in the doc, do the parameters for a POST request go in the body? (I saw a reference to adding them as query params in the url string but that seems to have been removed). POST parameters are best sent in the body of the request. - Looking at the OAuth spec and the example on the auth page, can I assume POST parameters are ordered alphabetically along with the other params when building the base string? Do they have to be doubly url encoded? It is more correct to say parameters are sorted by name, using lexicographical byte value ordering. If two parameters share the same name, they are ordered according to their value. One thing that may help is to think of the POST parameters the same as GET parameters when you are constructing your basestring. To the OAuth signing process the difference is the word POST, the rest of the signing process is the same. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sat, Jun 18, 2011 at 7:22 AM, Chris Mowforth ch...@mowforth.com wrote: Hey all, I'm playing around with the Twitter OAuth API, having rolled my own clients in both ruby and Objective-C. I've managed to authorise myself successfully and send status updates, but api methods like direct_messages/new always give me 401 errors. I know I'm missing something elementary in the way I'm making the calls, so I just want to clarify a couple of things: - From what I understand in the doc, do the parameters for a POST request go in the body? (I saw a reference to adding them as query params in the url string but that seems to have been removed). - Looking at the OAuth spec and the example on the auth page, can I assume POST parameters are ordered alphabetically along with the other params when building the base string? Do they have to be doubly url encoded? Here's a quick excerpt of the ruby client I put together: https://gist.github.com/1033130 -- 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] Getting All Child Tweets From Paren Tweets.
Hi Samyag, Replies are not the easiest things to get out of Twitter and there isn't an API method that will reliably do this for you. What you can do is follow the in_reply_to_status_id chain using the /1/statuses/show API request. This will allow you to trace a child Tweet back to it's parent(s). Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sat, Jun 18, 2011 at 5:11 AM, samyag shah sss_sa...@yahoo.com wrote: hello, I m developing the iOS application which contains the twitter as one module. I wanted to know that does the Twitter provides the API for following senario: Suppose user clicks on the Patrent/Root/Main Tweet then I want all the Child tweets correspoding the Patrent/ Root/Main tweets. I observed this senario happens on the Website but not on the authorized Twitter iOS Application . -- 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] trending topics order
Hi,
Yes, trending topic responses are returned in the order of most trending to
least trending. In the example you give Guille Franco is trending more than
Vuvuzela.
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Fri, Jun 17, 2011 at 7:09 PM, xkema kemal...@gmail.com wrote:
Hi there
Are trending topics results, ordered from most-trendy topic to last
trendy?
..
..
..
consider a trends node like:
trends: [
{
name: Guille Franco,
url: http://search.twitter.com/search?q=Guille+Franco;
},
{
name: #honestyhour,
url: http://search.twitter.com/search?q=%23honestyhour;
},
...
...
...
...
{
name: Vuvuzela,
url: http://search.twitter.com/search?q=Vuvuzela;
}
],
Question again: IsGuille Franco most trending and Vuvuzela least
trending. (for these ten result)
--
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 add twitter login functionality to my site
Hi Sheraz, When you say you wish to add a Twitter login to your site do you mean you want users to be able to sign into your site with their Twitter identity, or that you want to be able to log them into Twitter.com? If you want users to be able to sign-in into your website with their Twitter identity you may find our Sign in with Twitter guidance helpful: http://dev.twitter.com/pages/sign_in_with_twitter The other situation isn't possible. The Twitter API does not provide a way for you to log a user into twitter.com. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sat, Jun 18, 2011 at 4:14 AM, sheraz4pro sherazsale...@gmail.com wrote: hi i am trying to integrate twitter login functionality to my site . can some body guide me how i can integrate it. i have read the documentations but unable to find any practical example. -- 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: ABUIKit / TwUI ?
Thanks for your interest in the library. We hope to have information about it released soon. As soon as we do we'll let you know through the mailing list and through @twitterapi. Best @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sun, Jun 19, 2011 at 1:52 PM, nfarina nfar...@gmail.com wrote: *Bump* Also, any info about when TwUI will be available? Would love to use it in a project I'm working on. On Jun 11, 5:21 pm, SM sanja...@gmail.com wrote: I wasn't able to attend the announcement regarding ABUIKit /TwUI. Can someone provide a summary of what was presented? 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] Login to twitter using the oauth
Hi Karthi. The Twitter API doesn't provide a way for an application to log a user into Twitter.com. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sun, Jun 19, 2011 at 11:40 PM, karthi karthivis...@gmail.com wrote: hi i have used twitter oauth API libraries and i can use the API and authorize the application and i can able to post the tweets, I want to redirect it to the twitter's home page once authorized. How it can be done using the API. I should be able to login to twitter and see its home page say www.twitter.com when certain icon is clicked. This icon will have credential info (username and password) in background of the icon in a text file. and when the icon is pressed it takes the user to the twitter site and login by itself using the credential in the text file and shows the home page. This is the issue i am facing..Have anyone used twitter's API and help me to achieve the above task... Thanx... -- 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] Follower count stuck...no one can follow me
Hi Jeff, When I visited the account page for @NYNYfans I was able to follow the account successfully. Is there an error returned when you try and follow the accounts? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Sun, Jun 19, 2011 at 8:10 PM, activefan j...@activefan.com wrote: I set up several dozen twitter accounts at the beginning of the year for the various departments in our sports news business. We have an API for each account that autotweets stories from several locations. The accounts were growing well, and some got up into 600-800 followers and then stopped around April. Our tweets continue to go out, but our follower count stopped and clicking FOLLOW from any other of our customer accounts does not allow them to follow us. I fear that our accouts were blacklisted or marked with a limit that has our accounts now stuck... How can we fix this? \ account examples: @NYNYfans @BigDFans -- 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 error
Hi, A 400 error indicates something in the request you are making is malformed. Are you using a library to make requests or did you create your own wrapper? If you created your own library for making requests you may instead want to try one of the libraries listed on our developer resources site: http://dev.twitter.com/pages/libraries Moving forward, to help identify the cause of the 400 could you share the the request header and URL you are sending and the API headers and response body returned. Remember to remove any OAuth secrets from the code you share. Best @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Mon, Jun 20, 2011 at 12:39 PM, antiphobe gundad...@gmail.com wrote: The time was in sync and I still used ntpd to reset it. No use. I tried to use the same script on different server, same user - 400 error (bad request) Tried on new server, different user, same script - it works! So I'm lead to believe something might be wrong with the twitter user a/c? Is that known to happen? -- 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 many REST calls do you save with the streaming API?
Fabien, Thanks for sharing this insight into how much the Streaming API is helping reduce the API calls you are making. It would be really interesting to hear the difference other developers are seeing. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Mon, Jun 20, 2011 at 1:53 PM, Fabien Penso fabienpe...@gmail.com wrote: Hey, I thought some of you might wonder how many REST calls you save using the Streaming API instead, so here is a graph for my iPhone application http://2apn.com I usually do about 7k requests/hour (for lists, and stuff not available through the streaming API), but I had an temporary glitch in my streaming scripts and my REST scripts launched at full capacity, going from 7,000 requests / hour to 70,000 requests / hour. See the attached graph, over a day of history. -- Fabien Penso @fabienpenso -- 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] Placing follow us and tweet buttons together just impossible
Hi Fernando, You can instruct the follow button to hide the screen_name by passing the parameter show_screen_name as false. When using data attributes this would be written as data-show-screen-name=false. Remember that the user’s screen_name must always be displayed next to the Follow Button though. We cover this in the guidance on our developer resources site: http://dev.twitter.com/pages/follow_button#how-can-i-use-the-follow-button-only-and-display-the-users-screenname-myself In it we say: Note that if you decide to set the show_screen_name parameter to false, you’ll still have to display “manually” which @username the Follow button is interacting with. In other words, it has to be very clear who the user is going to follow by clicking your Follow Button. Hope that helps, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 21, 2011 at 4:56 PM, twitterproblem fernando.agraf...@speedy.com.ar wrote: 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 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] geo_place writeable container for Indonesia
Hi Aldian, We don't have a timeline for any additional place regions. As with language support, if any additional countries/regions are added to our place database we will announce it on the Twitter Blog or through @twitterapi and this list. Best @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 21, 2011 at 5:01 PM, Aldian Fazrihady a...@aldian.net wrote: @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 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] inconsistent data when fetching the stream using location boxes
Hey Thomas,
Thanks for providing the examples. I'm a little confused about the latitude
and longitude you have provided in your example Tweets.
When I query those Tweets through the API I receive geo information which
matches your Streaming API filter.
Where are you reading the latitude and longitude from?
Here are the responses I see:
/1/statuses/show.json?id=83428963950669824\trim_user=1
{
coordinates: null,
favorited: false,
truncated: false,
created_at: Wed Jun 22 06:59:49 + 2011,
id_str: 83428963950669824,
in_reply_to_user_id_str: null,
annotations: null,
text: OMG, Jamie Cullum singing live on Radio 2 right now is amazing!!!
Thank you @achrisevans for suggesting that song!,
contributors: null,
id: 83428963950669824,
retweet_count: 0,
in_reply_to_status_id_str: null,
geo: null,
retweeted: false,
in_reply_to_user_id: null,
source: a href=\http://stone.com/Twittelator\;
rel=\nofollow\Twittelator/a,
in_reply_to_screen_name: null,
user: {
id_str: 63515926,
id: 63515926
},
place: {
name: Hounslow,
country: United Kingdom,
country_code: GB,
attributes: {
},
url: http://api.twitter.com/1/geo/id/c2e57feb725f3ee1.json;,
bounding_box: {
coordinates: [
[
[
-0.457447,
51.420633
],
[
-0.243419,
51.420633
],
[
-0.243419,
51.502851
],
[
-0.457447,
51.502851
]
]
],
type: Polygon
},
id: c2e57feb725f3ee1,
full_name: Hounslow, London,
place_type: city
},
in_reply_to_status_id: null
}
and /1/statuses/show.json?id=83428616981061633\trim_user=1
{
coordinates: null,
favorited: false,
truncated: false,
created_at: Wed Jun 22 06:58:26 + 2011,
id_str: 83428616981061633,
in_reply_to_user_id_str: 42856682,
annotations: null,
text: @icsbcn @XaviGava @martaspons follower, de qui?,
contributors: null,
id: 83428616981061633,
retweet_count: 0,
in_reply_to_status_id_str: 83426231340638208,
geo: null,
retweeted: false,
in_reply_to_user_id: 42856682,
source: web,
in_reply_to_screen_name: icsbcn,
user: {
id_str: 232599714,
id: 232599714
},
place: {
name: Barcelona,
country: Spain,
country_code: ES,
attributes: {
},
url: http://api.twitter.com/1/geo/id/1a27537478dd8e38.json;,
bounding_box: {
coordinates: [
[
[
2.0524766,
41.3200423
],
[
2.2261223,
41.3200423
],
[
2.2261223,
41.4682346
],
[
2.0524766,
41.4682346
]
]
],
type: Polygon
},
id: 1a27537478dd8e38,
full_name: Barcelona, Barcelona,
place_type: city
},
in_reply_to_status_id: 83426231340638208
}
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 22, 2011 at 12:07 AM, Thomas Alisi thomasal...@gmail.comwrote:
hey man,
thanks for this reply! yup, of corse I can.
so, I am using twitter4j and reading the stream with the streaming API
implementation (loosely following the code snippet below). I have setup a
filter query with a list of location boxes, being the following 3
(barcelona, manchester, london):
- [barcelona] 1.48, 41.10, 2.34, 41.4,
- [london] -0.30, 51.10, 0.21, 51.45,
- [manchester] -2.18, 53.25, -2.09, 53.31
then retrieving the status' location through the Status.getGeoLocation()
function (
http://twitter4j.org/en/javadoc/twitter4j/Status.html#getGeoLocation%28%29
)
now, it happen (quite frequently, but I don't have a statistic... say 1
post out of 50) that I find the geo location being with coordinates out of
the boxes, such as:
37.1289787 -84.0832596 (tweet id: 83428963950669824 - reverse geocode using
google maps: london, kentucky)
10.103 -64.669 (tweet id: 83428616981061633 - reverse geocode using
google maps: barcelona, venezuela)
so I am wondering how it can happen, provided that I am giving numerical
coordinates for location boxes...
hope this is clearer, many thanks
thomas
fetch stream:
StatusListener listener = new StatusListener(){
public void onStatus(Status status) {
// get geoLocation and save to db
}
};
TwitterStream twitterStream = new
TwitterStreamFactory(listener).getInstance();
twitterStream.filter( myFilterQuery );
--
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:
Re: [twitter-dev] How long can we access a past profile picture?
Hi yama, Older profile images maybe available for a short period of time after they are changed. This is due to caching and you shouldn't assume they will be there permanently. In answer to your other question, yes you should use the URL provided in the user object of the API responses. The second method is a rate limited API request and you should avoid using it as the URL for a profile image. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 5:24 AM, yama eternalsun...@gmail.com wrote: Hi guys, I'm planning to store a Profile Picture URL to DB from json by search API. When a user change picture, it seems we can still access it for a while. But is it permanent or just short term? I found there are 2 ways to get profile pics. http://a3.twimg.com/profile_images/1407755095/cat_normal.jpg; and http://api.twitter.com/1/users/profile_image/watermusica.xml;. Shouldn't I user the former way? Thank you, yama -- 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] Problem With User/lookup API
Hi Kamesh, The users/lookup method isn't the best way to check for a following relationship. Instead you can either request your friends/ids and see if their user_id is included, or call /1/friendships/show.json: http://dev.twitter.com/doc/get/friendships/show Hope that helps, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 6:37 AM, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Hai, i am getting a problem with users/lookup.json. i am using this API to get My Follower info and in the responsethere is a tag following which should return a bool value...but it is returning the value as null. Because of this i am not able to get recoginize whether i am following this person or not... is there any solution for this? //kamesh -- 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: Twitter Authenticate displays Authorize screen and on reload it Authenticates and continues to callback
Hey, The authenticate flow will display a login screen in a number of situations: * if the user isn't logged into twitter.com * if the user hasn't allowed the application access to their account before * if you pass the force_login or screen_name parameter to the authenticate endpoint * if the user has revoked access to the application * if the requested permission level is different to the one the user originally allowed Is it possible any of those situations are happening? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 6:14 AM, mike_f1 mi...@realflair.com wrote: I have the exact same issue, but am using C# and the Twitterizer library. Also, I can't seem to prevent the Authenticate pop up appearing and asking for permission despite the app already being authorised for this user and the user already signed in to Twitter. Checked by logging into twitter and going to Applications - I 'allowed' it by using Authenticate as per http://dev.twitter.com/pages/sign_in_with_twitter the first time, but it still pops up every time since. Is it something to do with how the App has been 'allowed' access? Do I need to 'allow' the app using the authorize URL first then using the authenticate url for future requests? Must be doing something wrong but I can't see what, can anyone shine any light on this please? -- 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, Thanks for the update. I've passed this information onto the relevant team here. So we can keep track of this could you file a ticket on our public issue tracker: http://code.google.com/p/twitter-api/issues/list Thanks @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 6:51 AM, Eric Mueller nevin...@gmail.com wrote: It's also responding with the 500 in less than two seconds (sometimes less than one), which makes timeouts seem unlikely. -- 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: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
Hi Echo, We haven't announced an end of life date for these methods but we wanted to mark them as deprecated so help developers know they are not suitable anymore. We recommend moving to the friends/ids, followers/ids and users/lookup pattern at your next opportunity though. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter 2011/6/21 Echo liushuang...@gmail.com Thanks Bill. statuses/followers and statuses/friends are deprecated. Is there a timeline in twitter to announce when will the deprecated API be closed? I wonder the deadline since our app is depending them . Thanks! Echo On 6月14日, 下午8时04分, Bill Jacobson gabe...@gmail.com wrote: Amit, Your endpoint is obsolete and no longer supported by Twitter. That's why you got the 403. Statuses/followers will succeed if you change it tohttp://api.twitter.com/1/statuses/followers.xml https://api.twitter.com/1/statuses/followers.xml BUT this API is deprecated. Read all about it here: http://dev.twitter.com/doc/get/statuses/followers Bill On 06/14/2011 12:38 AM, Amit Battan Ror wrote: Bill Working fine :https://twitter.com/statuses/friends_timeline.xml Not Working Giving 403 Error : https://twitter.com/statuses/followers.xml On Jun 14, 10:14 am, Amit Battan Rorbatta...@gmail.com wrote: Thanks Bill I will check and try to track URL .. On Jun 13, 9:07 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, also seehttp:// www.mailinglistarchive.com/html/twitter-development-talk@googl That's what helped me. -Bill On 06/13/2011 10:44 AM, Bill Jacobson wrote: I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.comwrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.com wrote: Hi All I am using Twitter-OAuth-iPhonehttps:// github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- 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
Hi Reet, Our developer resources site includes guidance and examples on how to use OAuth with the Twitter API. You can find more information on the following pages... Authentication: http://dev.twitter.com/pages/auth Libraries: https://dev.twitter.com/pages/libraries Using One Access Token: https://dev.twitter.com/pages/oauth_single_token Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 21, 2011 at 11:10 PM, reet ritushukla@gmail.com wrote: How to use OAuth? -- 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] Stream API Issues
Hi Paul,
I'm not able to reproduce this issue. I'm making my request like this:
twurl -t /1/statuses/filter.json -d track=Boston,hockey,Obama -H '
stream.twitter.com' --no-ssl
I would recommend not using terms like 'the, and, or' in your filter though.
Those words are extremely common and you will find yourself limited very
quickly. Instead pick specific terms that you want to track, or combine two
filter words together with a space.
More information on the AND and OR format of the track parameter is
available on our developer resources site:
http://dev.twitter.com/pages/streaming_api_methods#track
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 22, 2011 at 7:37 AM, Paul Dettorre paul.detto...@gmail.comwrote:
For some reason when I use any keywords other than the, and, or I
get no results. Tried in both cUrl Python. Keywords like Boston,
hockey, Obama return no results! Curl Python code just wait
receiving no results. Any thoughts? Also the keywords the, and, or
produce a {limit:{track:20}}, every 50 or so records. i understand
this is a rate limit but 1) What is the number for 2) What is it
limiting as more tweets seem to still be received?
Thanks
import tweetstream, simplejson as json
words = [the, and, or]
f_out = open(c:\\bitly_test\\results_4.txt,'w')
stream = tweetstream.TrackStream(, , words)
for tweet in stream:
print INPUT:, tweet
f_out.write(tweet)
#result = json.loads(stream)
#print result
--
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] Poor documentation. For example, regarding lists. Suggestions for improvement.
Hi Dave,
Thanks for your feedback, it's important for us to know when developers are
not finding the information they are looking for.
I have responded to your specific points inline:
Issue #1: Valid version numbers
I was unable to locate valid values for version. I tried 1.1.14,
which I understand the current version to be from searching the site,
but that causes a 404. It was only after digging around for examples
that I noticed people using 1. A page describing valid version
numbers should be linked from the word version.
In the API documentation there is a version place marker in the example
request URL. Currently only one version of the API exists, that version is
1. This means any REST API queries will be of the format:
https://api.twitter.com/1/statuses/user_timeline.json
I've updated the API FAQ and Things Every Developer Should Know pages to
include this information.
http://dev.twitter.com/pages/every_developer
https://dev.twitter.com/pages/api_faq
Issue #2: Extremely unclear parameter passing
As this call uses GET, and the documentation lists parameters you
should include, this implies to me that you should use a query string.
The docs list the following required parameters:
* list_id - The numerical id of the list.
* slug - You can identify a list by its slug instead of its numerical
id. If you decide to do so, note that you'll also have to specify the
list owner using the owner_id or owner_screen_name parameters.
As it is not at all obvious how you discover the list_id or
owner_id, I opted to use slug and owner_screen_name. However, if
you
$ curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
you get
{error:You must specify either a list ID or a slug and
owner,request:\/1\/lists\/statuses.json?owner_screen_name=cnn}
Notice that the response json lists the request with only the
owner_screen_name parameter. I imagine that 1 or more things went
wrong, possibly including:
1. The API has a bug that is stripping the second parameter
2. The documentation is incorrect, and you may not use slug and
owner_screen_name to retrieve results.
3. The documentation does not properly describe how you pass the
arguments in the query string. Perhaps you're supposed to encode the
entire string. I was not able to discern this.
4. The documentation is incorrect about the url format.
The request you are making is correct. The error is instead being caused by
the way in which you are using your terminal. When using a terminal like
this you need to remember to either quote your URL or escape the 's.
This would make your request look like this:
curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
Issue #3: No obvious way to discover list_id or owner_id
user_ids are provided in all API responses which include a user object. The
most common way of getting information about a user is through the
users/show method or users/lookup method:
http://dev.twitter.com/doc/get/users/show
http://dev.twitter.com/doc/get/users/lookup
list_id is available from the index of lists for a user. This request is the
/1/lists request:
http://dev.twitter.com/doc/get/lists
Alternatively, if those values are unknown or you don't wish to look them
up, you can provide the slug and screen_name as you have done in your
example.
Issue #4: Undocumented, un-obvious correct url
I was finally able to retrieve the results using this url, pieced
together from scattered examples.
$ curl http://api.twitter.com/1/cnn/lists/cnnnews/statuses.json
So far as I could tell, the documentation in no way implies that you
could use such a url.
This is the deprecated way of making lists requests. It is documented on
this page of the developer resources site:
http://dev.twitter.com/doc/get/:user/lists/:id/statuses
I hope that helps explain a little bit more about the API. Let me know if
this information is useful or what you would change and we'll see how we can
incorporate it into the docs.
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
--
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: A few updates about the permission model change
Hi Aaron, I have't been able to reproduce this issue so could you email me details of the app and captures of the requests and responses. Then I can investigate further. Thanks, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 12:57 PM, Aaron Rankin aran...@sproutsocial.comwrote: Hi Matt / Twitter, We're not seeing the Direct Message permission setting ever take effect. In our application profile, it says that we're set to request read, write and DM, and we've saved this several times successfully. However, both the X-Access-Level header and the oauth/authorize page list that we don't have DM access (and for the former, on accounts for which we've re-authorized). Aaron 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. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter -- 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] http://groups.google.com/group/twitter-development-talk
Hi dalvir, The REST API lives on the domain api.twitter.com not twitter.com. The request you are making should be made to: http://api.twitter.com/1/statuses/user_timeline.json To understand the reason for the error you will need to inspect the response that comes back from the API. We put more details about errors in the response body to help you identify what you need to do in your code. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 12:32 AM, dalvir sainidal...@gmail.com wrote: I am using the following code. This was working fine. oAuthTwitter oAuth = new oAuthTwitter(); oAuth.Token = Token; oAuth.TokenSecret = secrentoken; TwitterToken objtwitter = new TwitterToken(); oAuth.oAuthWebRequest(oAuthTwitter.Method.GET, http://twitter.com/ statuses/user_timeline.xml, null);//This line return the following 401 error But Now it stoped to work. and returning the error The remote server returned an error: (401) Unauthorized. Why this error is coming? -- 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: Introducing the Follow Button
Hi David, Glad to hear this is working for you now. For the benefit of everyone else this issue was identified and resolved in the last few days. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 9:07 AM, David Huang linshunghu...@gmail.comwrote: Seems like my issue was fixed during maintenance.. http://status.twitter.com/post/6816501955/follow-button-off-line Thanks, David On Jun 15, 11:06 am, David Huang linshunghu...@gmail.com wrote: Hi all, I was testing the new Follow button on my webpage and noticed that one-click only works when the user have signed in to Twitter during the same browsing session. If I relaunched the browser, even though I'm still logged in to Twitter, clicking the Follow button would open a popup. Am I missing anything, or is this the expected behavior? Thanks, David On May 31, 1:07 pm, Arnaud Meunier arn...@twitter.com wrote: Hey developers, Today we're launching theFollowButton! Similar to the Tweet Button, it's a new widget that lets users easilyfollowa Twitter account from any web page. TheFollowButton has a single clickfollowexperience, simple implementation model, and is configurable to fit the needs of your website. Read our announcement on the Twitter blog, and use the resources below to set up your ownFollowButton: - Create aFollowButton here: http://twitter.com/about/resources/followbutton - Detailed documentation:http://dev.twitter.com/pages/follow_button We’ve also added a Javascript layer to our Buttons and Web Intents that makes it possible for you to detect how users are interacting with these tools, and to hook them up to your own web analytics. More details on:http://dev.twitter.com/pages/intents-events We're excited to see how you guys will implement theFollowButton. Let us know what you think, or if you have any questions. Arnaud / @rno -- 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] trying to add...
Hi Mirella, Can you let us know a little bit more about the way you add the Tweet Button to your site. For example are you using a content management system or hosted service? Best, @themattharris On Jun 23, 2011, at 10:20, mire...@fortheloveofcakes.ca mire...@fortheloveofcakes.ca wrote: hi I'm trying to add the twitter button on my website and everytime i copy the code and paste it in the HTML area it gives me the code even after I publish it...why? how do i fix this? -- 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
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: Error with Web Intents Javascript Events
Thanks for the update Mike, Is this hosted on a webpage we can access, or can you put a test page up that we can hit? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 15, 2011 at 6:47 PM, MManalo mike.j.man...@gmail.com wrote: Hi Matt, Thanks for your help with this. No JS errors or warnings. The button just does not fire any sort of event when we call it. Again it works just fine in IE8 and Firefox, sending data to Omniture. But unfortunately, nothing happens when clicked in IE7. On Jun 14, 9:27 pm, Matt Harris thematthar...@twitter.com wrote: Hey, Does IE7 report any javascript errors or warnings? Other than the events, does the button render and perform correctly? Best @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 14, 2011 at 10:56 AM, MManalo mike.j.man...@gmail.com wrote: Hey everyone, We have been trying to implement tracking on the tweet buttons that are featured on our sites. We used the method recommended to us on this page: https://dev.twitter.com/pages/intents-events Upon testing, we found that the button sends data to Omniture, our web analytics provider, when we use IE8 and Firefox to access the site, but it does not happen when using IE7. I was wondering if there may be any specific reason as to why, or what might we be doing wrong? 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 -- 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] data-lang defaults to English when it shouldn't
Hi Marc, IPortuguese is a relatively new addition to the languages supported by Twitter so some features are not fully translated yet. The team is working on getting those translations added though. If you leave the data-lang as 'pt' your button will automatically receive the translations when we add them. Best, @themattharris On Jun 14, 2011, at 6:41, mschipperheyn m.schipperh...@gmail.com wrote: Hi, The data-lang currently doesn't support Portugese, which, given Brazils huge and very active Twitter community, is very surprising. So currently if you specify data-lang=pt, it will default back to English. This doesn't make sense. Portugese is to all intents and purposes very similar to Spanish. I can obviously deal with this in my code. But if in the near future, Twitter does update the language support, I would have to adapt my code (or probably forget all about it until someone points it out). So, it makes more sense for the Twitter code itself to make this shortcut. My two cents, Marc -- 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: Twitter Button Torture!
Can you tell us which browsers you are using and explain a little bit about what you mean when you say the button doesn't 'look right'? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 14, 2011 at 7:00 PM, 3 rexes t...@threerexes.com wrote: Are there any brilliant button tweakers out there that can 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 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: Twitter Button Torture!
Hey Tara, Nothing changed our side so it sounds like your browser was the cause. Either way, glad you got it working. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 14, 2011 at 9:38 PM, 3 rexes t...@threerexes.com wrote: Themattharris, somehow you fixed it. I spent a good 2 hours trying to figure this out, and now it looks normal. Maybe my browser needed to shut down re-start? Here it is looking normal http://www.threerexes.com/Shop/NecklacePage/Empress-Silver-Gothic-Choker-Necklace.htmlI need to hire a website tech! 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
[twitter-dev] A few updates about the permission model change
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 on https://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. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter -- 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] assets2.twitter.com seems to be down
Hi, What file/resource are you trying to load from that domain? Best, @themattharris On Jun 11, 2011, at 9:23, kp pki...@gmail.com wrote: http://assets2.twitter.com seems to be down. Is this a transient issue or permanent change? If it is a transient issue, is there an ETA for the fix? -- 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] Current OAuth DM 'bug/hole' being reported? Any official response?
Hi kosso, Thanks for asking this question. If you go through the OAuth flow now you will notice that we have updated the text to better clarify what information applications will or will not have access to during this permission model transition period. We've also released the other requested updates to the OAuth flow. There are: * standardized the language on the screens and API responses to 'direct message' to better relate to the functionality and the API paths it's connected to. * added support for the force_login parameter to the /authorize flow. * added a link/button on the cancel page that calls the application callback with a denied parameter. This allows users who are in the web view to get back to your application without completing the authorization process. * improved the OAuth screens on phones unable to support the new ones. As a reminder, the enforcement date for the new permission is the 30th June. On this date all R/W tokens will lose the ability to read and delete direct messages. Applications requiring DM access are encouraged to transition the requested permission level setting of their applications prior to the cut off date. If you do not need to read or delete direct messages you do not need to update your application. Updates and the FAQ for the new permission model can be found on our developer resources site: https://dev.twitter.com/pages/application-permission-model and https://dev.twitter.com/pages/application-permission-model-faq Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 10, 2011 at 9:59 AM, kosso kos...@gmail.com wrote: It's come to a few people (and blogs') attention that apps 'advertised' as (on the OAuth login page) having R/W access only (ie: no DM) are able to get DM access. I'm assuming that since the change/restrictions were pushed back from June1st to June 14th (or June 30th - depending on which official announcement you read : here or on dev.twitter.com) that the text saying what access level an app has should be taken with a pinch of salt until the change is enforced. Can some at Twitter please respond ASAP? People are calling foul at TechCrunch and Mashable, etc. Thanks @Kosso -- 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: Streaming API, Following just a couple of people
Hey Ray, Thanks for sharing the solution for the problem you hit. Glad everything worked out. Best @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 9, 2011 at 10:17 AM, Ray Slakinski ray.slakin...@gmail.comwrote: Turns out that urllib2's readline has a buffer which you can work around by creating a custom readline that uses read(1) Example: def readline(): buffer = '' while True char = conn.read(1) if '\n' == char: return buffer else: buffer += char Hope this helps out anyone else using python. On Jun 7, 9:26 am, Ray Slakinski ray.slakin...@gmail.com wrote: I should add the account I'm using to follow my account and my co- workers is not the same one as either of these 2. Its completely separate. On Jun 6, 12:46 pm, Matt Harris mhar...@twitter.com wrote: 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 -- 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: Support for oauth_bridge_code via this endpoint is deprecated
Hey everyone, Along with the JSAPI the oauth_bridge_code was one of the unsupported components of @anywhere. It was originally made available during the Social App Workshop July last year but wasn't released as a supported or production ready system. We caution against using unsupported technologies/APIs for anything other than your own experimentation and learning as they could stop functioning, be turned off, or change significantly without notice. If a method or API is not documented and you want to check if it's suitable for production please let us know. If the method is supported but missing from the docs we'll get it added in. To obtain OAuth 1.0a tokens for a user you should incorporate the OAuth web flow described in our documentation: http://dev.twitter.com/pages/auth Best, @themattharris On Jun 9, 2011, at 6:59, Felix Oldenburg oldenburg.fe...@googlemail.com wrote: Ah, sorry I mean since today... Am 09.06.11 15:50, schrieb Felix Oldenburg: Hi, I'm facing the same problem until today. On 9 Jun., 02:53, bisanthebisanthe.gro...@gmail.com wrote: Hello, When I run the following code OAuthRequest request = new OAuthRequest(Verb.POST, https:// api.twitter.com/oauth/access_token); request.addBodyParameter(oauth_bridge_code, oauth_bridge_code); service.signRequest(token, request); Response response = request.send(); Following message appears. errors error code=97Support for oauth_bridge_code via this endpoint is deprecated/error /errors Did something changed in twitter API ? It was working a couple of weeks ago ? -- 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] rate limiting on users profile image
Hey,
This endpoint has always been rate limited so this is an error in the docs.
We have some updates to the docs coming out soon which will correct that.
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
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] exception 403 on status update
Hi Gang, Whenever we return an error we include a reason in the response body telling you why. We recommend you always inspect the response body, and headers, to learn more about the cause of the error. The most common reasons for a 403 are: * The tweet is a duplicate. * The tweet is over 140 characters * The user has reached the limit for the number of Tweets that can be sent Hope that helps, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 8, 2011 at 4:22 PM, Gang T tangg...@gmail.com wrote: Hi there, Could you please tell us in which cases the exception 403 will be thrown on status update? Your help are appreciated. Best, Gang -- 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] rate limiting on users profile image
Hi Denzil,
The paragraph is letting you know that the API isn't the only source of rate
limits. If an API method says it isn't rate limited it means the request
will not count against the 350 authenticated (150 unauthenticated) requests
you are permitted per hour.
It doesn't mean the method isn't limited in some way though. In the text we
link to the page on our Twitter help site which explains the other limits
which exist on Twitter. Those limits are often referred to as user limits
and apply to the user no matter what application or site they are using
(including twitter.com).
The user limits are described on more detail on the help site (linked to
from the rate limiting document):
https://support.twitter.com/forums/10711/entries/15364
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 1:40 PM, Correa Denzil mcen...@gmail.com wrote:
Matt :
Can you also clear the air on what the snippet from the Twitter docs mean?
I read it as there are no non-rate limited methods.
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limits http://support.twitter.com/forums/10711/entries/15364 are
described on our help site
--Regards,
Denzil
On Thu, Jun 9, 2011 at 12:45 AM, Matt Harris thematthar...@twitter.comwrote:
Hey,
This endpoint has always been rate limited so this is an error in the
docs. We have some updates to the docs coming out soon which will correct
that.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
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] 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
[twitter-dev] Please check the Twitter IPs your service is making requests to
Hey everyone, We recently updated the IPs our DNS addresses resolve to. Usually this is a transparent change that requires no action from you but we've noticed a number of requests are going to the old IPs. This is most commonly caused by some code which resolves the IP of our DNS connection at startup and then keeps it until the service is completely restarted. We often change our IPs for load balancing and network performance reasons so it is really important that you use the DNS address when talking to the API. Our DNS entries also have a very short lifetime (30 seconds) so you want to make sure you refresh the DNS cache regularly. To know the currently configured IPs for our DNS you can use the command line tool dig. For example: dig +nocmd api.twitter.com +noall +answer api.twitter.com. 27 IN A 199.59.148.87 api.twitter.com. 27 IN A 199.59.148.20 api.twitter.com. 27 IN A 199.59.149.200 api.twitter.com. 27 IN A 199.59.149.232 If your service is communicating with the API on any other IPs please update your DNS cache and reconnect. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] tweet button zero count
Hi John, Looking at your site the URL is shared correctly through the Tweet Button, and your URL resolves correctly. When I search for your URL though, even just the domain, I don't see any Tweets. Do you have an example of an account where that URL was Tweeted? Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Jun 1, 2011 at 7:04 AM, John Carver johnlewiscar...@gmail.comwrote: Hello Twitter support, Please advice im starting to frustrate. Tweet button count for our posts stays equal to 0. We set urls canonical, we use data-url and data-count-url with exactly same data - nothing helps. Please advice extremely ASAP: http://52outspoker.com/posts/?word1-word2-word0 http://52outspoker.com/posts/?word1-word2-word1 http://52outspoker.com/posts/?word1-word2-word2 http://52outspoker.com/posts/?word1-word2-word3 Regards, John. -- 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] friend and followers sort order
Hi Khandelwal, The friends and followers IDs methods return IDs with the most recent friend/follow first. Changes in the social graph aren't available as a request from the API, but there are a couple of alternatives. * Compare the friends/followers IDs at particular intervals. * If your application is something an individual user runs, you could connect them to userstreams and listen for follow events. * If you have access to sitestreams you can follow the user and receive follow and unfollow events for them. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Jun 1, 2011 at 10:05 AM, Khandelwal khandel...@gmail.com wrote: Is there a guaranteed sort order of the results of a friends/ids or a followers/ids call? From what I've read online, it appears to be in reverse chronological order (newest follower/friend first) but it sounds like that's just because the database happens to return it that way. Is this true? Is the order guaranteed? I'd love for a way to get the changes in the social graph since the last time I checked for a user. -- 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] DM enforcement date has been extended to the end of June
Hey everyone, We wanted to say a big thank you to the developers who have been sending us debug information, and details of steps to follow to reproduce device specific issues. An especially big thank you to those of you who have shared the changes you made to your applications on the mailing list. All of this information has helped us to improve the OAuth flow for you and your users. But, we know that we're getting close to the DM enforcement date and that some of these new features aren't available to you yet. We understand this means you might not be able to fully test your updated flow so we are going to extend the deadline until the end of June. This makes the new enforcement date Thursday, June 30th, 2011. Below is a list of the features we are adding in response to your requests and feedback: 1. Adding the force_login parameter to the /oauth/authorize screen to ensure the /authorize screen displays a login screen. 2. Adding the screen_name parameter to the /oauth/authorize and /oauth/authenticate requests. When provided with the force_login parameter we will pre-fill the username box on the OAuth screen. 3. Adding a Back to app button on the webpage which is loaded if a user selects no, thanks. When selected the Back to app button will open the provided oauth_callback URL with a 'denied' parameter. The value of the denied parameter will be the request_token obtained from the /request_token request. For example: http://example.com/callback/?denied=xyz123abc 4. Design updates to the OAuth screens to improve compatibility across devices. 5. A lightweight OAuth screen flow for devices which are slow or incompatible with the new screens. 6. A new header on authenticated requests which tells you the access level of the oauth_token you are using. The header is available now and is called X-Access-Level. More information for this is available here: https://dev.twitter.com/pages/application-permission-model-faq Thanks for working with us to ensure users can make informed decisions about the access an application has to their account. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] TweetDeck joins Twitter
Hey everyone, Today we announced on the Twitter Blog ( http://blog.twitter.com/2011/05/all-decked-out.html ) that the TweetDeck team has joined Twitter. When Tweetie became part of the Twitter family the user growth was huge, creating more opportunities for developers to build applications for the growing audience. With TweetDeck now joining us we expect to see even more opportunities become available to you and look forward to seeing what you create. TweetDeck is a powerful platform for brands, publishers and advanced Twitter users, and we’re really excited that Iain and his team are joining us. We’re looking forward to working with them as we invest and support the TweetDeck that you all are familiar with. Best @themattharris -- 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] force_login on authorize?
Hi Sean, The support for the parameter on authorize isn't live just yet. It is coming though. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 25, 2011 at 10:08 AM, Sean Heber s...@spiffytech.com wrote: I know there was some talk about adding this, and I may have missed it, but does /oauth/authorize support force_login yet? I know I could try it pretty trivially, but thought I'd ask here since I'm sure others with apps that support multiple accounts are also interested in the answer. l8r Sean -- 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] A new permission level
Hey everyone,
We recently updated our OAuth screens to give users greater transparency
about the level of access applications have to their accounts. The valuable
feedback Twitter users and developers have given us played a large part in
that redesign and helped us identify where we can do more.
In particular, users and developers have requested greater granularity for
permission levels.
In response to this feedback, we have created a new permission level for
applications called “Read, Write Direct Messages”. This permission will
allow an application to read or delete a user's direct messages. When we
enforce this permission, applications without a “Read, Write Direct
Messages” token will be unable to read or delete direct messages. To ensure
users know that an application is receiving access to their direct messages,
we are also restricting this permission to the OAuth /authorize web flow
only. This means applications which use xAuth and want to access direct
messages must send a user through the full OAuth flow.
What does this mean for your application?
If you do not need access to direct messages: you won’t need to make any
changes to your application. When we enforce the new permission level your
read or read/write token will automatically lose access to direct messages.
If you do need access to direct messages: you will need to edit your
application record on https://dev.twitter.com/apps and change the permission
level of your application to “Read, Write and Direct Messages”. The new
permission will not affect existing tokens which means existing users or
your app or service will need to reauthorize.
We know this will take some time so we are allowing a transition period
until the end of this month. During this time there will be no change to the
access Read/Write tokens have to a users account. However, at the end of the
month any tokens which have not been upgrade to “Read, Write and Direct
Messages” will be unable to access and delete direct messages.
Affected APIs and requests
On the REST API, Read and Read/Write applications will no longer be able to
use these API methods:
/1/direct_messages.{format}
/1/direct_messages/sent.{format}
/1/direct_messages/show.{format}
/1/direct_messages/destroy.{format}
For the Streaming API, both User Streams and Site Streams will only receive
direct messages if the user has authorised an application to access direct
messages.
Applications that use “Sign-in with Twitter” or xAuth will only be able to
receive Read or Read/Write tokens.
What this means is only applications which direct a user through the OAuth
web flow will be able to receive access tokens that allow access to direct
messages. Any other method of authorization, including xAuth, will only be
able to receive Read/Write tokens.
What will happen when the permission is activated
When we activate the new permission, all Read and Read/Write user_tokens
issued to third-party applications will lose their ability to read direct
messages. Any attempt to read direct messages will result in an HTTP 403
error being returned.
For example, a GET request to
https://api.twitter.com/1/direct_messages/sent.json will return an HTTP 403
Forbidden with the response body:
{errors:[{code:93,message:This application is not allowed to access
or delete your direct messages}]}
Key Points
* If you wish to access a user’s direct messages you will need to update
your application and reauthorize existing tokens.
* The only way to get direct message access is to request access through the
OAuth /authorize web flow. You will not be permitted to access direct
messages if you use xAuth.
* When we enforce the permission Read/Write and Read tokens will be unable
to access and delete direct messages.
* Read/Write tokens will be able to send direct messages after the
permission is enforced.
We’ll be collating responses and adding more information on our developer
resources permission model page:
https://dev.twitter.com/pages/application-permission-model
We have also blogged about this on the Twitter blog:
http://blog.twitter.com/2011/05/mission-permission.html
Best,
@themattharris
--
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] embed a video player in the Details pane
Hi BB, We're not accepting any new applications for the details pane at the moment. Should this change we will let everyone know. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 18, 2011 at 4:02 PM, BB thebar...@gmail.com wrote: Does anyone know when (if ever) twitter will open up the details pane to new companies? Thanks, BB -- 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: embed a video player in the Details pane
Hi BB, I don't have anymore information i'm afraid. All I know is they are not accepting any more applications right now. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 18, 2011 at 5:10 PM, BB thebar...@gmail.com wrote: Matt, Thank you very much for the prompt reply. 2 follow ups though: Do you ever foresee this happening? And if so do you have an approximate time-frame? Or if you tell me would you have to kill me? :-) Thanks, BB On May 18, 4:54 pm, Matt Harris thematthar...@twitter.com wrote: Hi BB, We're not accepting any new applications for the details pane at the moment. Should this change we will let everyone know. Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, May 18, 2011 at 4:02 PM, BB thebar...@gmail.com wrote: Does anyone know when (if ever) twitter will open up the details pane to new companies? Thanks, BB -- 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-dev] HTTPS profile and profile background image URLs are being added to user objects
Hey everyone,
Later this week we'll start to add two new fields to the user object
responses from the Streaming and REST APIs (not Search). Due to caching, not
all objects will have these fields immediately so you should check they are
present in the response before using them.
The two additional fields are the SSL versions of the profile_image_url and
the profile_background_image_url. They will be identified in the user object
by the attributes:
profile_image_https
profile_background_image_url_https
For example, the @twitter user would look similar to this:
{
profile_background_tile: false,
name: Twitter,
profile_sidebar_fill_color: F6F6F6,
profile_sidebar_border_color: EE,
location: San Francisco, CA,
created_at: Tue Feb 20 14:35:54 + 2007,
profile_image_url:
http://a0.twimg.com/profile_images/1124040897/at-twitter_normal.png;,
id_str: 783214,
is_translator: false,
profile_link_color: 038543,
follow_request_sent: false,
default_profile: false,
contributors_enabled: true,
favourites_count: 10,
url: http://twitter.com;,
utc_offset: -28800,
id: 783214,
profile_image_url_https:
https://si2.twimg.com/profile_images/1124040897/at-twitter_normal.png;,
listed_count: 58963,
profile_use_background_image: true,
lang: en,
protected: false,
profile_text_color: 33,
followers_count: 5063298,
notifications: false,
geo_enabled: true,
verified: true,
profile_background_color: ACDED6,
profile_background_image_url_https:
https://si2.twimg.com/images/themes/theme18/bg.gif;,
description: Always wondering what's happening. ,
time_zone: Pacific Time (US Canada),
statuses_count: ,
friends_count: 487,
default_profile_image: false,
profile_background_image_url:
http://a1.twimg.com/images/themes/theme18/bg.gif;,
status: {
coordinates: null,
created_at: Mon May 16 17:23:59 + 2011,
truncated: false,
favorited: false,
id_str: 70177690392592384,
in_reply_to_user_id_str: null,
text: Remember in 2009 when @aplusk and @cnn were racing to be the
1st to reach a million followers? @ladygaga just reached 10 million. Wow!,
annotations: null,
contributors: [
16739704
],
id: 70177690392592384,
retweet_count: 100+,
in_reply_to_status_id_str: null,
geo: null,
retweeted: false,
in_reply_to_user_id: null,
in_reply_to_screen_name: null,
source: web,
place: null,
in_reply_to_status_id: null
},
screen_name: twitter,
show_all_inline_media: true,
following: true
}
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
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: what happen if auth token inside search api?
Hi Jimmy, The Search API only indexes public Tweets so it doesn't know about Tweets from protected users. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 11, 2011 at 8:29 AM, jimmy6 laise...@gmail.com wrote: If it is the case, how can i get/search private twit? On May 10, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: The Search API will ignore any authentication that you send its way -- it doesn't know anything about authentication. @episod http://twitter.com/episod - Taylor Singletary On Tue, May 10, 2011 at 7:13 AM, jimmy6 laise...@gmail.com wrote: What will happen if i pass in authentication token in search api? Does it return different result? Does it return only my twit and friend twit? -- 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] Auto Authorize Web App (OAuth)
Hi David, The process you describe is supported by the Sign in with Twitter flow described here: http://dev.twitter.com/pages/sign_in_with_twitter Think about the permissions you are asking for though. You often don't need more than Read access for this flow as the writeable actions are supported by Web Intents: http://dev.twitter.com/pages/intents Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 11, 2011 at 8:17 AM, davidb2002 davidburleson2...@gmail.comwrote: Hi, I am using Oauth to create a way for users of our website to login using their twitter account. However, It's quite annoying that everytime they click to sign in with their twitter account they have to grant access each and every time. Couldn't it work so that if it has been granted once they don't have to keep granting access? Therefore removing a step. I'm using the steps found in: http://net.tutsplus.com/tutorials/php/how-to-authenticate-users-with-twitter-oauth/ Thanks for any feedback! -- 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] Search with multiple terms
Hi Adrian, Check out our guide on how to use the Search API: http://dev.twitter.com/pages/using_search It includes information about how to do this and other types of queries. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 11, 2011 at 8:50 AM, Adrian arco.wagemak...@gmail.com wrote: Is it possible to do a search for multiple words that belong together combined with the OR operator? For example if I want to capture all tweets for The Bachelor including people who use hashtags, I would like the query to look something like: the bachelor or thebachelor on Twitter search this is translated as: ors=the+bachelor+thebachelor which is clearly wrong. I have tried it many ways now but seem to fail constantly. Any suggestions? -- 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] What is the best way to find state information from place object when place_type is either poi or neighborhood ?
Hey Priti,
To get more information about a place all you need to do is make an API
request to the URL in the place object. In your case this would be:
http://api.twitter.com/1/geo/id/79c32440a890dad7.json
Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, May 11, 2011 at 11:20 AM, Priti priti.gangr...@gmail.com wrote:
What is the best way to find state information from place object
when place_type is either poi or neighborhood ?
Is it to take place.url and do lookup under contained_within ?
snippet from tweet:
...
place:{full_name=Starbucks Coffee, San Francisco, name=Starbucks
Coffee, url=http://api.twitter.com/1/geo/id/79c32440a890dad7.json,
country=United States, place_type=poi, bounding_box={type=Polygon,
coordinates=[[[-122.434817, 37.760942], [-122.434817, 37.760942],
[-122.434817, 37.760942], [-122.434817, 37.760942]]]},
country_code=US, attributes={street_address=4094 18th Street},
id=79c32440a890dad7},geo:{type=Point, coordinates=[37.7609,
-122.435]},
... rest part of tweet ignored
I have been trying to read on the discussions but did not find
concrete solution.
Thanks,
-Priti
--
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] Reducing rate-limited calls to friends/ids
Hi Which method do you use currently to get the users follower list? The best method to use for this is 1/followers/ids which is documented here: http://dev.twitter.com/doc/get/followers/ids Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, May 11, 2011 at 1:20 PM, torncanvas torncan...@gmail.com wrote: I'm developing a Twitter visualizer application. Currently it stores tweets in a DB based on a hashtag using the Streaming API, and then looks up the friends (as in friends/ids) lists of those who've tweeted and stores those lists in a DB. In essence, it shows how people tweeting with the same hashtag are connected to each other. At least for iteration 1. I'm having a problem with rate limiting because I need to do a friends list lookup for every unique user that has tweeted with the hashtag. My application is conferences, and for larger ones it's very easy to get above several hundred unique users per hour. That doesn't even account the fact that my list could get dirty fairly quickly when conference attendees see someone else in the visualizer and decide to follow them on-the-spot. Simply testing the application has been difficult for this very reason. Is there another way get a list of people a user follows without very quickly running into the rate limit? -- 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] Twitter Search Api Keyword Geocode Query concern ?
Hi Harik, That is correct. Adding Geocode as a querystring parameter will AND it with the queried keywords. There is an updated description of how this works on our developer resources site: http://dev.twitter.com/doc/get/search and http://dev.twitter.com/pages/using_search Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, May 10, 2011 at 11:08 AM, harik padmahar...@gmail.com wrote: Can I combine Keyword and Geocode query this way ? http://search.twitter.com/search.atom?q=twittergeocode=37.781157,-122.398720,25mi I read here tht geocode does not support disjunction? http://apiwiki.twitter.com/w/page/22554756/Twitter-Search-API-Method:-search So will the abv query work? Also ,does the above query work as an And operator? Like it would give the tweets with the word twitterand near to that location? If I am wrong please correct me. -- 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: Oauth authorize isn't working consistently
Hi Ryan, We've tested across a range of feature and smart phones and haven't been able to reproduce this. Do you know which devices are experiencing the issue so we can investigate further? Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, May 8, 2011 at 12:20 PM, artesea ryancul...@gmail.com wrote: I have reports of users not having any username/password boxes when on the oauth page using their mobiles. Ryan Cullen dabr / dab.argh On May 7, 11:21 pm, Aaron Rankin aran...@sproutsocial.com wrote: I'm posting in case Twitter is unaware. The authorize page/process is regularly returning no tokens. It is working some of the time. Our users have reported this since Wednesday. Aaron Rankin Sprout Social -- 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] Getting since date or since_id is too old Error code 403 when trying to use search API with since_id
Hi Abhi, The ID you are passing is 1304977102 which is really old. If you are not sure which since_id to use you should omit it from your query. The response from the API will then include the oldest since_id available. Remember the Search API only stores the last 7 days worth of Tweets. Anything created more than a week ago will not be available through the Search API. You can learn more about Search on our developer resources page: http://dev.twitter.com/doc/get/search and http://dev.twitter.com/pages/using_search Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, May 9, 2011 at 8:34 PM, Abhi abhishek2j...@gmail.com wrote: sample url : http://search.twitter.com/search.atom?lang=enrpp=100result_type=mixedq=%22Geometry+Essentials+For+Dummies%22+Mark+Ryansince_id=1304977102 all my twitter search api calls (with since_id in them ) are returning since date or since_id is too old -- 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] Getting since date or since_id is too old Error code 403 when trying to use search API with since_id
Hi Abhi, As Mark mentions, since_id is a Tweet ID not a unix timestamp. Right now this is in the region of 67770831463395328. If you want to Search since a certain date you can include the parameter since:-mm-dd in your query parameter. e.g: http://search.twitter.com/search.atom?lang=enrpp=100result_type=mixedq=%22Hell+To+Pay%22+Neal+Hall+since%3A2011-05-08 Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, May 9, 2011 at 8:55 PM, Mark Linsey m...@crowdbooster.com wrote: since_id values are tweet ID's, not unix timestamps. On Mon, May 9, 2011 at 8:47 PM, Abhishek Jain abhishek2j...@gmail.comwrote: Hi Matt, thanks for the quick response: http://search.twitter.com/search.atom?lang=enrpp=100result_type=mixedq=%22Hell+To+Pay%22+Neal+Hallsince_id= *1304633831* However unix time 1304633831 stands for May 5th is that too old for the twitter API? Cheers, Abhi On Mon, May 9, 2011 at 8:42 PM, Matt Harris thematthar...@twitter.comwrote: Hi Abhi, The ID you are passing is 1304977102 which is really old. If you are not sure which since_id to use you should omit it from your query. The response from the API will then include the oldest since_id available. Remember the Search API only stores the last 7 days worth of Tweets. Anything created more than a week ago will not be available through the Search API. You can learn more about Search on our developer resources page: http://dev.twitter.com/doc/get/search and http://dev.twitter.com/pages/using_search Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, May 9, 2011 at 8:34 PM, Abhi abhishek2j...@gmail.com wrote: sample url : http://search.twitter.com/search.atom?lang=enrpp=100result_type=mixedq=%22Geometry+Essentials+For+Dummies%22+Mark+Ryansince_id=1304977102 all my twitter search api calls (with since_id in them ) are returning since date or since_id is too old -- 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 -- cheers, Abhishek jain -- 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] Twitter for pages on Facebook Not Working
Hi Jen, The Facebook Application isn't part of the Twitter APIs so we're not able to help you specifically here. Our user support team should be able to help you though. You can contact them through: http://bit.ly/gottaproblem Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, May 1, 2011 at 4:00 PM, Jennse23 jenns...@gmail.com wrote: Hi everyone, I have tried installing both Twitter for Pages, and Twitter App so that I can have my Twitter posts appear on my FB Page status's. I have added the app to my page as instructed by Involver, and then gone to the apps section of my page. When I click on Edit Settings or one of the other options, I just get a message saying that the link is broken. I tried removing and reinstalling but it makes no difference. Your help would be appreciated. Jen -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Five-Oh-Two Fest
Hey Dewald, There is an issue filed on the public issue tracker for this but as reported in the ticket, this seems to work sometimes and not at others: http://code.google.com/p/twitter-api/issues/detail?id=2156 To help us track this down, an iIf you are happy to, can you paste some screen_names or user_ids which you are reporting for spam and getting the error for? If not, send them to me directly. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Apr 28, 2011 at 12:05 PM, Dewald Pretorius dpr...@gmail.com wrote: Twitter, are you aware that your API is throwing 502s left right and center on blocks/create/nnn.json and report_spam.json? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Visual refresh of the OAuth screens
Hey Developers, Some of you may have noticed already that earlier today we deployed a redesign of the OAuth screens. We know both you and your users have been asking for better clarity about what an application can see and do with an account and these screens are a step towards doing that. One of the areas we wanted to improve is showing the details of your application. If you visit the new screens you will see we've separated your application details from the permissions that are being requested. We did this to help users see that it is your application, not Twitter's. Remember you can update your application details at anytime on http://dev.twitter.com/apps . Mobile and international support has also been improved and we now use the same rendering templates as those created for Web Intents. This ensures the design matches the rest of #newtwitter and, more importantly, works cross-browser, cross-platform, and multilingual. We hope you find the new designs more welcoming and friendly. Let us know what you think. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Visual refresh of the OAuth screens
@Shannon: thanks for the feedback on this. The new screens are fluid in size so wrap to the available space. Hosting in a local iframe isn't something we've encouraged in the past. We prefer the user to be taken to the authenticate or authorize page in a tab/new window that they can see the URL of. This is a good area for us to write some guidance for so thanks for raising this. @Orian: great feedback and definitely something for us to take on board - thanks. This is a first release of these pages to get a feel for if they are going in the right direction. We tried to select a number of phrases that explain the access that's being granted to an application but that are also easy to understand. I think there will always be some that don't make it, but there are others, like the ones you raise, which would help aid transparency more. @themattharris On Thu, Apr 28, 2011 at 3:00 PM, Orian Marx (@orian) or...@orianmarx.comwrote: I think it's good to be giving users more information on what they are granting access to, but by leaving out a number of things there are misleading implications. In particular, this list does not mention that users will be granting access to all their private DMs. I also find it interesting the list mentions the ability to follow new people, but not to unfollow existing people. Obviously it's been to everyone's benefit who has built apps that rely on OAuth up to this point that there has been specific mentioning of access to DMs as this would likely turn off a lot of people from granting access to experimental apps. The reality is that the OAuth system needs finer-grained controls. It would be good to hear if there has been any new thought on this from Twitter engineering. Otherwise, I like the new page :) @orian On Apr 28, 5:02 pm, Matt Harris thematthar...@twitter.com wrote: Hey Developers, Some of you may have noticed already that earlier today we deployed a redesign of the OAuth screens. We know both you and your users have been asking for better clarity about what an application can see and do with an account and these screens are a step towards doing that. One of the areas we wanted to improve is showing the details of your application. If you visit the new screens you will see we've separated your application details from the permissions that are being requested. We did this to help users see that it is your application, not Twitter's. Remember you can update your application details at anytime onhttp:// dev.twitter.com/apps. Mobile and international support has also been improved and we now use the same rendering templates as those created for Web Intents. This ensures the design matches the rest of #newtwitter and, more importantly, works cross-browser, cross-platform, and multilingual. We hope you find the new designs more welcoming and friendly. Let us know what you think. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Dev.twitter.com - your apps
Hey Barry, Thanks for this. Sometimes when the system is seeing a lot of traffic there can be a delay in the new records being created and the cache getting update. It shouldn't be for a long time though - how long ago did you create the apps? Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Apr 27, 2011 at 4:18 PM, BarryCarlyon barrycarl...@gmail.comwrote: Just created a new twitter account for a project. So went to make a application so I can oauth in and a tweet with Abraham's lib. The lib was throwing a Incorrect signature so I went to check I got all the keys right. However in your apps (https://dev.twitter.com/apps) I find no apps. And I am unable to create a application with the same name. So my app exists I am unable to see if application entry. I created three under the user @minecraftfmnow and cannot see any. The third and final app is call minecraftfmnow. Please advise. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: error 401 failed oauth_signature and token / javascript - qml
);
request_maker.setRequestHeader(Authorization, data);
request_maker.onreadystatechange = oth_func;
request_maker.send();
}
and here is the BaseString it generates :
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_tokenoauth_consumer_key%253D[OAUTH_CONSUMER_KEY]
%26oauth_nonce%253D9HQfzLWlhqFpZAaURHNHr5bkpvMlweg
%26oauth_signature_method%253DHMAC-SHA1%26oauth_timestamp
%253D1303216955%26oauth_token%253DOAUTH_TOKEN%26oauth_version%253D1.0
and here is the signature :
N2K3D1ZjAd7h8urLAjeyUSTWFUU=
I've tried generate the signature with composite signing key :
consumer_secret + + token_secret and without the token_secret
On 19 avr, 11:08, galeyte gaetan...@gmail.com wrote:
Hi,
Thanks for answering my question.
I've tried a lot of things to reach oauth/request_token, and i've
tried :
request_maker.open(POST, https://api.twitter.com/oauth/
request_token)
but nothing has changed !
here is my new code :
function signForm() {
accessor = { consumerSecret: consumer_secret
, tokenSecret : oauth_token_secret};
message = { action: https://api.twitter.com/oauth/request_token;
, method: POST
, parameters: []
};
message.parameters.push([oauth_consumer_key=, consumer_key]);
message.parameters.push([oauth_callback=, oauth_callback]);
message.parameters.push([oauth_signature_method=,
signature_method]);
OAuth.setTimestampAndNonce(message);
message.parameters.push([oauth_version=, oauth_version]);
OAuth.SignatureMethod.sign(message, accessor);
return true;
}
function getSignature() {
signForm();
console.log(OAuth.SignatureMethod.getBaseString(message));
console.log(OAuth.getParameter(message.parameters,
oauth_signature));
request_maker = new XMLHttpRequest();
request_maker.open(POST, https://api.twitter.com/oauth/
request_token);
request_maker.setRequestHeader(Host, api.twitter.com);
request_maker.setRequestHeader(Content-type, application/x-www-
form-urlencoded);
request_maker.setRequestHeader(Authorization, OAuth
+oauth_signature_method=+signature_method
+oauth_timestamp=+OAuth.getParameter(message.parameters,
oauth_timestamp)
+oauth_nonce=+OAuth.getParameter(message.parameters, oauth_nonce)
+oauth_signature=+OAuth.getParameter(message.parameters,
oauth_signature));
request_maker.onreadystatechange = oth_func;
request_maker.send(oauth_signature_method=+signature_method
+oauth_timestamp=+OAuth.getParameter(message.parameters,
oauth_timestamp)
+oauth_nonce=+OAuth.getParameter(message.parameters, oauth_nonce)
+oauth_signature=+escape(OAuth.getParameter(message.parameters,
oauth_signature)));
}
At first i thought it was my signature but i've checked again and it
appears to be ok. maybe it's about base64 thing.
I've also seen that when i checked request_token with that tool
:http://oauth.googlecode.com/svn/code/javascript/example/requestToken
Request_token succees on https but fails on http.
On 18 avr, 21:14, Matt Harris thematthar...@twitter.com wrote:
Hi,
Looking at your code this line:
request_maker.open(POST, https://api.twitter.com/oauth;);
makes it look like you are making a request to:
https://api.twitter.com/oauth
Double check you are sending the user to the correct endpoint. At this
point
of your flow I think you mean to make a request
tohttps://api.twitter.com/oauth/request_token.
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Apr 15, 2011 at 4:51 AM, galeyte gaetan...@gmail.com wrote:
I don't have a 401 anymore but i recieve a you are being redirected
page, so i can't get my request_token
here is my code :
function getSignature() {
var accessor = { consumerSecret: consumer_secret,
tokenSecret: oauth_token_secret
};
var message = { method: POST,
action: /request_token,
parameters: []
};
message.parameters.push([oauth_callback,
OAuth.formEncode(oauth_callback)]);
message.parameters.push([oauth_consumer_key,
OAuth.formEncode(consumer_key)]);
message.parameters.push([oauth_nonce, OAuth.nonce(32)]);
message.parameters.push([oauth_signature_method,
signature_method]);
message.parameters.push([oauth_timestamp, OAuth.timestamp()]);
OAuth.completeRequest(message, accessor);
OAuth.SignatureMethod.sign(message, accessor);
console.log(OAuth.getParameter(message.parameters,
oauth_signature));
var data = Oauth oauth_consumer_key=+consumer_key
+oauth_signature_method=+signature_method
+oauth_callback=+OAuth.getParameter(message.parameters,
oauth_callback)
+oauth_timestamp=+OAuth.getParameter(message.parameters,
oauth_timestamp)
+oauth_nonce=+OAuth.getParameter(message.parameters, oauth_nonce)
+oauth_signature=+OAuth.getParameter(message.parameters,
oauth_signature);
console.log(data);
request_maker = new XMLHttpRequest
Re: [twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account
Hi Chris,
Our policy team are the beat ones to contact about this as they have access to
the information about why the app was suspended. You can contact them through
a...@twitter.com .
When you contact them let then know what you've put in the email below and
include the ticket number of your previous communication with them.
They will be able to let you know the next steps.
Best
@themattharris
On Apr 19, 2011, at 8:57, Christopher Stolte stolte...@gmail.com wrote:
Hi Matt,
Thank you so much for your timely response. Your suggestion was very
helpful - I logged the response body and am seeing the following
error:
Invalid / suspended application
I really don't know why that would be - does that mean that we are
blacklisted? I should point out a few things that you will probably
want to know:
1. We have a conservative and fairly sophisticated throttling system
to prevent us from over-stepping the rate limit (I don't think that's
the problem...)
2. On Saturday I received a message from the API support team
confirming that our whitelisted account was in good standing (can
provide the message if it's helpful)
3. We've seen the rate limit reported in the response change back and
forth somewhat sporadically...
Thank you again for any help you can provide - in general we are very
pleased with the API and we certainly appreciate your support!
Best,
Chris
On Apr 18, 3:44 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Mon, Apr 18, 2011 at 11:23 AM, Christopher Stolte
stolte...@gmail.comwrote:
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.
In the last few days, we started getting only 401 Not Authorized
responses when using these credentials. Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic. Error messages look like this:
WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm=http://api.twitter.com}
The response header shows 401 but no other enlightening information.
I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so
forth:
http://api.twitter.com/1/users/show.json?user_id=[id]
Something appears to have changed on Twitter's end but we don't know
what.
Can anyone shed some light on what might be happening? We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?
Thank you in advance for any help or guidance!
Sincerely,
Chris Stolte
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] The remote server returned an error: (401) Unauthorized.
Hi Nathan, So we can help diagnose the problem could you inspect the response body that comes back from your request to the API. It contains an explanation of why the 401 is being returned and let's us know how to proceed. Best @themattharris On Apr 19, 2011, at 11:17, The World Connection nathan.poeppel...@gmail.com wrote: I'm using TwitterVB and for some reason in the last week I've been receiving the following error. The remote server returned an error: (401) Unauthorized. I'm using the following code structure. http://twittervb.codeplex.com/wikipage?title=OAuth%20Web%20Tutorial Nothing changed. I've tried to reset my customer key/secret, that didn't work. I've tried to recreate the app, that didn't work. Do I have to wait for a propagation time period? Does Twitter restrict IP addresses? My website is sitting on a host. Any ideas? Thanks! Nathan -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: error 401 failed oauth_signature and token / javascript - qml
Hi,
Looking at your code this line:
request_maker.open(POST, https://api.twitter.com/oauth;);
makes it look like you are making a request to:
https://api.twitter.com/oauth
Double check you are sending the user to the correct endpoint. At this point
of your flow I think you mean to make a request to
https://api.twitter.com/oauth/request_token .
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Apr 15, 2011 at 4:51 AM, galeyte gaetan...@gmail.com wrote:
I don't have a 401 anymore but i recieve a you are being redirected
page, so i can't get my request_token
here is my code :
function getSignature() {
var accessor = { consumerSecret: consumer_secret,
tokenSecret: oauth_token_secret
};
var message = { method: POST,
action: /request_token,
parameters: []
};
message.parameters.push([oauth_callback,
OAuth.formEncode(oauth_callback)]);
message.parameters.push([oauth_consumer_key,
OAuth.formEncode(consumer_key)]);
message.parameters.push([oauth_nonce, OAuth.nonce(32)]);
message.parameters.push([oauth_signature_method,
signature_method]);
message.parameters.push([oauth_timestamp, OAuth.timestamp()]);
OAuth.completeRequest(message, accessor);
OAuth.SignatureMethod.sign(message, accessor);
console.log(OAuth.getParameter(message.parameters,
oauth_signature));
var data = Oauth oauth_consumer_key=+consumer_key
+oauth_signature_method=+signature_method
+oauth_callback=+OAuth.getParameter(message.parameters,
oauth_callback)
+oauth_timestamp=+OAuth.getParameter(message.parameters,
oauth_timestamp)
+oauth_nonce=+OAuth.getParameter(message.parameters, oauth_nonce)
+oauth_signature=+OAuth.getParameter(message.parameters,
oauth_signature);
console.log(data);
request_maker = new XMLHttpRequest();
request_maker.open(POST, https://api.twitter.com/oauth;);
request_maker.setRequestHeader(Authorization, data);
request_maker.onreadystatechange = oth_func;
request_maker.send(Authorization OAuth + data);
}
I don't now if it's me being dumb or anything else, but i really can't
find my mistake.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] 401 Unauthorized Responses to requests signed with whitelisted account
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Apr 18, 2011 at 11:23 AM, Christopher Stolte stolte...@gmail.comwrote:
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.
In the last few days, we started getting only 401 Not Authorized
responses when using these credentials. Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic. Error messages look like this:
WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm=http://api.twitter.com}
The response header shows 401 but no other enlightening information.
I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so
forth:
http://api.twitter.com/1/users/show.json?user_id=[id]
Something appears to have changed on Twitter's end but we don't know
what.
Can anyone shed some light on what might be happening? We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?
Thank you in advance for any help or guidance!
Sincerely,
Chris Stolte
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Tweet Button Display Issue
Hey Sam, Can you share the HTML you are using to markup the Tweet Button so we can see what the issue could be. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Apr 11, 2011 at 3:37 AM, Sam Hughes samvhug...@googlemail.comwrote: Hey guys, I am trying to customize some tweet buttons so that when clicked on the pop-up opens and the tweet text is something I have wrote. I know that the tweet button has this functionality, but when I try to embed the code onto any site the text reverts so that it tweets the page title that the Tweet button sits on. Anyone know why this isn't working? or know any good work arounds? Cheers, Sam -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
