[twitter-dev] Re: Revoked Access
And as an addition to what D. Smith said: you're probably storing your users' token and token_secret somewhere. So if you do have a tokens are present, you know they have granted access before. Also, you can check the message in the headers. Twitter sends a 401 when access has been revoked, and last time I checked, the accompanying message was Could not authenticate with OAuth. However, these error messages are not set in stone, and afaik they are not officially documented by Twitter.
Re: [twitter-dev] Re: Introducing the Tweet Button
Hey everyone,
I've updated the Tweet Button docs today with information which I hope
will answer a number of your questions. In particular the example
about using a short URL with the parameter data-counturl should help
those of you whose counts are staying at 0.
http://dev.twitter.com/pages/tweet_button#using-shorturl
For reference the documentation URLs are:
http://dev.twitter.com/pages/tweet_button
and
http://dev.twitter.com/pages/tweet_button_faq
Hope that helps,
Matt
On Fri, Aug 20, 2010 at 7:58 PM, felipe.lavin felipe.la...@gmail.com wrote:
Hi. I've been trying to create my own TweetButton links (something
like http://dev.twitter.com/pages/tweet_button#build-your-own-tweet-button)
and load them on a lightboxed iframe, using Fancybox (http://
fancybox.net/) but I'm getting an error that won't let me actually use
the TweetButton -- you can see an example on
http://beta.yukei.net/2010/06/trabajar-con-fechas-en-javascript/ (work-
in-progress)
It seems the error it's caused by a jQuery detection and livequery
function about the end of scribe.js, which is loaded in the
TweetButton page... there you have this code (beautified for better
reading):
if (window.jQuery) {
(function (A) {
A.extend(A.fn, {
scribe: function (B, D, C) {
C = C || {};
A(this).bind(C.clientEvent || mousedown,
function (E) {
window.scribe.call(this, B, D, C, E)
});
return this
}
})
})(jQuery);
(function (A) {
A(a.ab-reloading).livequery(function () {
watchReloadingABLink(A(this))
})
})(jQuery)
};
So, since I'm on an iframe, it correctly detects jQuery, but since I'm
not using the livequery plugin, the second function fails and nothing
is displayed on the iframe. Any way around this? Bug fix coming?
Thanks!
On 12 ago, 11:28, themattharris thematthar...@twitter.com wrote:
Hey everyone,
Today we’re launching theTweetButtonto make it easy for your users
to share your website with their followers. When they click on
theTweetButton, aTweetbox will appear pre-populated with a message and
link chosen by you. Once they have sent aTweetthey can choose to
follow accounts recommended by you. All of this happens on your
website, so the user never has to leave.
You have complete control over the suggested text of theTweetButton,
who theTweetshould be attributed to and recommendations of who to
follow. All of this is possible through a line of javascript and a few
URL parameters or data attributes of a link.
To add this to your own site grab it fromhttp://twitter.com/tweetbutton,
or create your own using our developer
documentation,http://dev.twitter.com/pages/tweet_button
Read more about theTweetButtonon our
blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html
Best
Matt
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
[twitter-dev] Re: null posts in home_timeline
Hi Guys
I'm also seeing this and forwarded on some markup for the
home_timeline to you, Matt.
It's easier to spot in XML, where Twitter are returning the following
between status objects:
nil-classes type=array/
e.g. (objects hidden using code folding)
status
status
nil-classes type=array/
status
status
nil-classes type=array/
status
status
Cheers
-N
Type pattern
-N
On Aug 24, 10:07 am, Thomas Woolway priv...@tswoolway.co.uk wrote:
I'm seeing this in my home timeline - @tomwoolway. Matt, I've sent you the
JSON output of my home timeline (seemed a bit big to spam the list with).
Tom
On Tue, Aug 24, 2010 at 8:22 AM, Kazuho Okui kaz...@gmail.com wrote:
I'm having same issue. It looks like null tweets appear when your
follower deletes their tweets. You can easily reproduce this bug.
Many twitter applications stop working since this evening. (guess most
of apps can't handle null correctly.) I think this should be addressed
by twitter end.
Thanks,
Kazuho
On Aug 23, 11:41 pm, Matt Harris thematthar...@twitter.com wrote:
Hi David,
Could you provide a couple of status IDs or a username so we can take
a look at this.
Thanks,
Matt
On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
davidnovako...@gmail.com wrote:
Hey, seeing json like this:
text: I really need to work out a way to make myself read
more books...I've found three in the last 10 minutes.
},
null,
{
coordinates: null,
.
null objects being included in the list of tweets?
Only seems to have started today.
David
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] White-listed IP showing rate-limit 150 requests/hour
Hi there, I have got my IP and a/c white-listed, until now I was working on account which was giving proper rate-limit, now I am trying to move from account to IP, but IP just showing rate-limit 150 requests/hr. (just doubt: working on sub domain of IP , will it be a cause? ) I just want to ask you that is there anything wrong I am doing? Also my white-listed account showing rate-limit 2667/hr right now. can you guys shed some light here please? I also want to ask you guys that , if I switched from account (passing id/pwd ) to IP , will I get 20k calls/hr or same like account showing right? Your help will be greatly appreciated. Thank you in advance.
[twitter-dev] Re: Unfollow bug?
I verified the same behavior with twurl ~ twurl -d screen_name=$NAME /1/friendships/destroy.json -c. On Mon, Aug 23, 2010 at 4:12 PM, funkyboy cesareroc...@gmail.com wrote: Hello, I am playing with the api. When I unfollow somebody (friendships/destroy) the info returned is incorrect, that is following = 1. The opposite works correctly, that is when I follow (friendships/ create), the info returned is correct, following = 1. Is it a bug? I am using json format. Thanks -c. ps: After unfollowing if I load user profile (/users/show) the info returned is correct, I am not following him. -- Cesare Rocchi studiomagnolia.com
[twitter-dev] Re: null posts in home_timeline
Just a quick update to point any Twitter folks reading this thread to
issue #1823 on the bug tracker
http://code.google.com/p/twitter-api/issues/detail?id=1823
Cheers!
-N
On Aug 24, 10:42 am, Nik Fletcher nik.fletc...@gmail.com wrote:
Hi Guys
I'm also seeing this and forwarded on some markup for the
home_timeline to you, Matt.
It's easier to spot in XML, where Twitter are returning the following
between status objects:
nil-classes type=array/
e.g. (objects hidden using code folding)
status
status
nil-classes type=array/
status
status
nil-classes type=array/
status
status
Cheers
-N
Type pattern
-N
On Aug 24, 10:07 am, Thomas Woolway priv...@tswoolway.co.uk wrote:
I'm seeing this in my home timeline - @tomwoolway. Matt, I've sent you the
JSON output of my home timeline (seemed a bit big to spam the list with).
Tom
On Tue, Aug 24, 2010 at 8:22 AM, Kazuho Okui kaz...@gmail.com wrote:
I'm having same issue. It looks like null tweets appear when your
follower deletes their tweets. You can easily reproduce this bug.
Many twitter applications stop working since this evening. (guess most
of apps can't handle null correctly.) I think this should be addressed
by twitter end.
Thanks,
Kazuho
On Aug 23, 11:41 pm, Matt Harris thematthar...@twitter.com wrote:
Hi David,
Could you provide a couple of status IDs or a username so we can take
a look at this.
Thanks,
Matt
On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
davidnovako...@gmail.com wrote:
Hey, seeing json like this:
text: I really need to work out a way to make myself read
more books...I've found three in the last 10 minutes.
},
null,
{
coordinates: null,
.
null objects being included in the list of tweets?
Only seems to have started today.
David
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: null posts in home_timeline
Hello,
Many users of some client apps are still in trouble because of null
results in home_timeline.
You can check usernames in trouble by searching famous twitter app
names.
Did you change the api specific? Or do you have any plan to fix this?
Thanks,
emmettoc
On 8月24日, 午後3:41, Matt Harris thematthar...@twitter.com wrote:
Hi David,
Could you provide a couple of status IDs or a username so we can take
a look at this.
Thanks,
Matt
On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
davidnovako...@gmail.com wrote:
Hey, seeing json like this:
text: I really need to work out a way to make myself read
more books...I've found three in the last 10 minutes.
},
null,
{
coordinates: null,
.
null objects being included in the list of tweets?
Only seems to have started today.
David
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] urlencoded vs percent encoded
I'll try to make this part clearer in the docs soon. I made the mistake of not including guidelines that one's actual sent POST body should always conform to application/x-www-form-urlencoded and that the values you pass into an OAuth signature base string algorithm are to have already been encoded. The POST body should be shown in two stages rather than just one, the unencoded POST body and the encoded POST body. In my example, the actual POST body sent would have been: status=setting%20up%20my%20twitter%20%E7%A7%81%E3%81%AE%E3%81%95%E3%81%88%E3%81%9A%E3%82%8A%E3%82%92%E8%A8%AD%E5%AE%9A%E3%81%99%E3%82%8B (Taking into account normalization of spaces as well, which is optional. One could also leave them as plusses and encode likewise in the POST body and signature base string). So many layers to take into account. Taylor On Mon, Aug 23, 2010 at 7:31 PM, richcollins richcoll...@gmail.com wrote: I'm adding OAuth support to the Twitter addon for the Io programming language. I'm trying to follow the example on http://dev.twitter.com/pages/auth#auth-request but there are a number of inconsistencies. Reading the OAuth spec http://oauth.net/core/1.0/#encoding_parameters leads me to believe the the base string is composed by joining together the percent-encoded query, oauth and post parameters with , and then percent encoding the resulting string. However, the example on dev.twitter.com depicts the status post parameter as urlencoded, but then shows it (double) percent encoded in the base string. Are the post parameters urlencoded in the body but then percent encoded in the base string? Are parameters generally percent-encoded twice? Once before joining with and then once after?
[twitter-dev] Re: null posts in home_timeline
http://twitter.com/twitterapi/status/22002256380
-N
--
Nik Fletcher
@nikf
On Aug 24, 9:49 am, emmettoc creepyman2...@gmail.com wrote:
Hello,
Many users of some client apps are still in trouble because of null
results in home_timeline.
You can check usernames in trouble by searching famous twitter app
names.
Did you change the api specific? Or do you have any plan to fix this?
Thanks,
emmettoc
On 8月24日, 午後3:41, Matt Harris thematthar...@twitter.com wrote:
Hi David,
Could you provide a couple of status IDs or a username so we can take
a look at this.
Thanks,
Matt
On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
davidnovako...@gmail.com wrote:
Hey, seeing json like this:
text: I really need to work out a way to make myself read
more books...I've found three in the last 10 minutes.
},
null,
{
coordinates: null,
.
null objects being included in the list of tweets?
Only seems to have started today.
David
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] White-listed IP showing rate-limit 150 requests/hour
Basic auth is going away. Read about it here: http://dev.twitter.com/pages/basic_auth_shutdown After Aug 31, you won't be able to use your login and password to access the API from any IP address. Your IP-based whitelisting will continue to be valid for unauthenticated and OAuth-authenticated requests. You are seeing your whitelisted basic auth rate limits go down proportional to the weekday-daily drop off we're performing. Taylor On Tue, Aug 24, 2010 at 3:37 AM, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi there, I have got my IP and a/c white-listed, until now I was working on account which was giving proper rate-limit, now I am trying to move from account to IP, but IP just showing rate-limit 150 requests/hr. (just doubt: working on sub domain of IP , will it be a cause? ) I just want to ask you that is there anything wrong I am doing? Also my white-listed account showing rate-limit 2667/hr right now. can you guys shed some light here please? I also want to ask you guys that , if I switched from account (passing id/pwd ) to IP , will I get 20k calls/hr or same like account showing right? Your help will be greatly appreciated. Thank you in advance.
Re: [twitter-dev] Re: null posts in home_timeline
Hey everyone,
Thanks for your patience and for sharing the erroneous responses.
We're working on this and will have a fix rolled out soon.
Best,
Matt
On Tue, Aug 24, 2010 at 7:25 AM, Nik Fletcher nik.fletc...@gmail.com wrote:
http://twitter.com/twitterapi/status/22002256380
-N
--
Nik Fletcher
@nikf
On Aug 24, 9:49 am, emmettoc creepyman2...@gmail.com wrote:
Hello,
Many users of some client apps are still in trouble because of null
results in home_timeline.
You can check usernames in trouble by searching famous twitter app
names.
Did you change the api specific? Or do you have any plan to fix this?
Thanks,
emmettoc
On 8月24日, 午後3:41, Matt Harris thematthar...@twitter.com wrote:
Hi David,
Could you provide a couple of status IDs or a username so we can take
a look at this.
Thanks,
Matt
On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
davidnovako...@gmail.com wrote:
Hey, seeing json like this:
text: I really need to work out a way to make myself read
more books...I've found three in the last 10 minutes.
},
null,
{
coordinates: null,
.
null objects being included in the list of tweets?
Only seems to have started today.
David
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
[twitter-dev] Following remotely
Is it possible to make a widget for my website that will allow users to follow me without leaving my website? If so what method would I use. E
Re: [twitter-dev] Following remotely
Hi E, Your best probably is the somewhat-frictionless Follow Button, part of the @Anywhere arm of the platform. http://dev.twitter.com/anywhere/begin It does involve a very smooth, frictionless pop-up authorization, but requires very little coding and is less heavy than the standard authorization patterns the API offers. Taylor On Tue, Aug 24, 2010 at 7:14 AM, eruna michael.levy...@gmail.com wrote: Is it possible to make a widget for my website that will allow users to follow me without leaving my website? If so what method would I use. E
[twitter-dev] Re: OAuth/authentication language setting
Hi Matt, Thank you very much for the fast response. I don't know how to post the screenshots on this group. So I'll email you directly the images. thanks. On Aug 24, 2:45 am, Matt Harris thematthar...@twitter.com wrote: Hi, It sounds like the language is being detected successfully as some of the text is translated, but also looks like we're missing some translations. I know in the bug report you explained which strings were in English and which were in French but could I ask you to provide a screenshot as well. This will help our international team work out which of their translations need addressing. Best, Matt On Mon, Aug 23, 2010 at 2:27 PM, bobt tester bobtester8...@gmail.com wrote: Hi, I'm trying to develop a Twitter app in French. I saw discussion in this group which seems to indicate that this can be done by setting the browser Accept-Language header to french (fr- ca). However, this doesn't work well for me. I set the browser Accept-Language: fr-ca and end up with OAuth/ authentication which is mixed with both english and french text. This happens for both FireFox InternetExplorer. -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] Replies/mentions not available?
There is a known issue related to JSON timelines containing null elements, which has crippled some clients. We'll have a fix for this deployed today as soon as we can. As for your mentions not showing on your web page -- can you share any status ids that you think should be there that aren't? Thanks, Taylor On Tue, Aug 24, 2010 at 7:52 AM, srikanth reddy srikanth.yara...@gmail.comwrote: I am not getting the mentions even in web page. Is there some problem? Also one of my users has complained about the inconsistency in fetching the results for hometimeline (related to json output. Not sure(yet) if this is my app's problem or from twitter but just want to check if there are any known problems from twitter related to json output)
[twitter-dev] Re: POST Daily limits and Direct Messages
Matt: Not sure what you want me to pick up in the documentation. I must be missing something. When I read the page on daily POST limits [http://support.twitter.com/ forums/10711/entries/15364] I see: quote Current Twitter Limits The current technical limits for accounts are: Direct Messages: 250 per day. API Requests: 150 per hour. Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. Changes to Account Email: 4 per hour. Following (daily): Please note that this is a technical account limit only, and there are additional rules prohibiting aggressive following behavior. You can find detailed page describing following limits and prohibited behavior on the Follow Limits and Best Practices Page. The technical follow limit is 1,000 per day. Following (account-based): Once an account is following 2,000 other users, additional follow attempts are limited by account-specific ratios. The Follow Limits and Best Practices Page has more information. /quote When I read the page you pointed me to, I see that OAuth calls are 350 per hour. So I am still left with the same question, when we hit the daily POST limit, is there a process to ask for an increase? The documentation says it is controlled at a user level, which implies an increase is possible. Yet the documentation does not explicitly say how an increase is requested. I am sure the answer is obvious, I just have been unable to find it. Looking forward to your reply... Dave
Re: [twitter-dev] Re: Recent API changes and new fields
Is there a time line for the streaming API getting these changes? Zac Bowling On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris thematthar...@twitter.com wrote: Hey everyone, Thanks for the questions. I'll try and answer them all in this message. 1) are the counts turned on? This weekend the counts were turned off and have remained off. This is because of some bugs we found in the way the value was calculated. I'll let you know when we have this resolved. 2) Will these fields show up in the Search and Streaming API? The fields are already in the Streaming API but be aware the 'retweeted' field is not meaningful here. This is because the streamed status knows nothing of the connected user. The search API does not include this information. 3) How do I know if the feature is turned off? Tweets will contain a retweeted_count if available. If the service is not enabled newer Tweets will likely be missing their retweeted_count. The safest thing to do is code to handle missing values. If they are present use them, if they are not, treat them the same as when the field didn't exist. This way your code works when the retweeted_count is both enabled and disabled. 4) When was the feature turned on? The service was rolled out the week beginning Aug 16th Hope that answers your questions, Matt On Sat, Aug 21, 2010 at 4:33 PM, Joe j...@ajcomputers.com wrote: will we see this in both search and stream API? On Aug 20, 6:45 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This week we rolled out a couple of new data fields for the status and user objects. For a while it has been difficult for you to get the number of lists a user is listed in, or the number of times a Tweet has been retweeted. You were also finding it hard to know if the user had retweeted the status themselves or not. The feature requests you filed and the messages on the developer mailing list showed this is a pain point for many of you as it uses up many of your hourly API requests. These fields are live now and many of you have already seen them in our API responses. We intended to tell you about these changes before they were live, and in the future for things like this we will, but this time around our system for doing that didn't work. The good news is we know what went wrong and have made the necessary improvements needed to ensure you are notified before the changes happen. The recent changes which have been made affect the user and status objects. In both cases we have added fields: To the user object: --- listed_count represents the number of public lists a user is listed in. This field is an integer. As this is a new field it is possible some users will not have a listed_count value yet. follow_request_sent representing whether the user you are authenticating as has requested to follow the user you are viewing. This will be false unless the friendship request is pending. The field is a boolean and will be true or false. To the status object: - retweet_count represents the number of times a status has been retweeted using the Twitter retweet action. This field is an integer. There will not be a value for this field when the feature is turned off, or the Tweet was created before we added retweet_count support. retweeted represents whether the user you are authenticating as has retweeted this status or not. The field is a boolean and can be true or false. Changes to existing methods -- users/show When requesting data for suspended users the user/show used to return an HTTP 404 status code - it now returns HTTP 403. This change is in response to number of users who were asking if there was a way to know if a user they were getting data for had been deleted or was instead suspended. The change means the API agrees with the twitter.com in that we confirm a user exists, but that you may not see their information because they are suspended. If you call /users/show on a suspended user the API response will include the error message User has been suspended. Please remember we sometimes turn features off to maintain site stability. We recommend you always check a field exists before attempting to use it and be prepared for the value to be empty. This will help ensure your code stays stable if we have to turn features off. We'll also be adding this information to the main API documentation soon. Best, Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Limit to search API query parameters
I would like to use the search API to pass in a bunch of usernames to get tweets - basically getting tweets from a group of usernames rather than manually trying to create a list everytime: http://search.twitter.com/search.json?q=from:al3x+OR+from:twitterapiz+OR+from:mashable Does anyone know how many from: parameters I can pass in? What is the max number of parameters? thanks, Quy
[twitter-dev] Re: Replies/mentions not available?
Hi Taylor, I am missing all mentions since July 31. This has been the case for at least a week, probably more. On Aug 24, 8:17 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There is a known issue related to JSON timelines containing null elements, which has crippled some clients. We'll have a fix for this deployed today as soon as we can. As for your mentions not showing on your web page -- can you share any status ids that you think should be there that aren't? Thanks, Taylor On Tue, Aug 24, 2010 at 7:52 AM, srikanth reddy srikanth.yara...@gmail.comwrote: I am not getting the mentions even in web page. Is there some problem? Also one of my users has complained about the inconsistency in fetching the results for hometimeline (related to json output. Not sure(yet) if this is my app's problem or from twitter but just want to check if there are any known problems from twitter related to json output)
Re: [twitter-dev] Limit to search API query parameters
Hi Quy, Queries are limited 140 URL encoded characters. [1] http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search On Tue, Aug 24, 2010 at 10:00 AM, Quy quyten...@gmail.com wrote: I would like to use the search API to pass in a bunch of usernames to get tweets - basically getting tweets from a group of usernames rather than manually trying to create a list everytime: http://search.twitter.com/search.json?q=from:al3x+OR+from:twitterapiz+OR+from:mashable Does anyone know how many from: parameters I can pass in? What is the max number of parameters? thanks, Quy -- Peter Denton Co-Founder, Product Marketing www.mombo.com cell: (206) 427-3866 twitter @Mombo_movies twitter - personal: @petermdenton
[twitter-dev] Re: Twitter Button Counts
Matt, I've been using data-counturl from the start and still seeing 0 counts. Here is the source for the button on http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/ which is showing 0 tweets: a href=http://twitter.com/share; class=twitter-share-button data- url=http://awe.sm/59O75; data-counturl=http:// blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for- wordpress/ data-text=Tweet Button with Shortening for WordPress data-count=vertical data-via=snowballfactory data- related=jhstrauss:Author of the postTweet/ascript type=text/ javascript src=http://platform.twitter.com/widgets.js;/script As you can see, BackType is indexing the tweets correctly: http://www.backtype.com/page/blog.snowballfactory.com%2F2010%2F08%2F15%2Ftweet-button-with-shortening-for-wordpress%2F/conversations Yet Twitter search doesn't appear to be: http://search.twitter.com/search?q=http%3A%2F%2Fblog.snowballfactory.com%2F2010%2F08%2F15%2Ftweet-button-with-shortening-for-wordpress%2F From what I can see, the issue appears to be related to what short URLs Twitter is choosing to index for the count. Thanks, -jonathan On Aug 24, 12:10 am, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This is a repeat of a message on another thread. I've updated the Tweet Button docs today with information which I hope will answer a number of your questions. In particular the example about using a short URL with the parameter data-counturl should help those of you whose counts are staying at 0. http://dev.twitter.com/pages/tweet_button#using-shorturl For reference the documentation URLs are: http://dev.twitter.com/pages/tweet_button and http://dev.twitter.com/pages/tweet_button_faq Hope that helps, Matt On Mon, Aug 23, 2010 at 2:10 AM, artesea ryancul...@gmail.com wrote: Just tried something else, I click on a tweet containing one of my short urls this actually redirects to http://www.libdemvoice.org/?p=20818utm_source=tweetutm_medium=twitt... by setting data-counturl=http://www.libdemvoice.org/?p=20818; it finally counts all the posts. If you are still seeing zeros, double check to see where you exactly redirect to. Regards Ryan On Aug 22, 12:27 pm, artesea ryancul...@gmail.com wrote: Anyone from Twitter looking at this list??? I now have a post with 32 tweets when looking athttp://twitter.com/#search?q=http%3A%2F%2Fldv.org.uk%2F20818 Yet the post itself is still showing 0. Until this is fixed there is no point having the numbers displayed. Completely useless. Ryan On Aug 19, 9:22 am, artesea ryancul...@gmail.com wrote: I don't give a damn about bit.ly or t.co. I just want people to a) tweet with my own shortlink, and b) display the number of people using that shortlink. I'm not expecting twitter to workout thathttp://ldv.org.uk/20680isa shortlink forhttp://www.libdemvoice.org/office-of-the-public-guardian-finally-star... I'm just expecting them to count the number of tweets withhttp://ldv.org.uk/20680 in them as per the spec. Ryan On Aug 19, 12:53 am, Jonathan Strauss jonat...@snowballfactory.com wrote: I'm pretty sure they're only indexing a subset of redirect links for the count at this point. So, the 4 or 5 being counted are probably ones that were shared with t.co or bit.ly. -jonathan -- Jonathan Strauss, Co-Founderhttp://snowballfactory.com Campaign tracking for social media -http://awe.sm A smarter way to update Facebook from Twitter -http://tweetpo.st Sharecount button for Facebook -http://www.fbshare.me On Aug 18, 12:12 pm, artesea ryancul...@gmail.com wrote: Happens in all browsers even days after the number of tweets is up to 4 or 5 (ok not a busy site but still zero make it look crap) Like I said before clicking on the number brings me to a page showing all the tweets so they are there, just for some reason twitter when doing the count lookup isn't finding them (url to short??? doesn't like .org.uk???) My shortlinks are the same for each post as I'm just using the wordpress post id with a 301 redirect. Not seeing any reply from Twitter other than it's probably a cache issue, which it clearly isn't. Ryan On Aug 16, 1:13 pm, Tom van der Woerdt i...@tvdw.eu wrote: I have one theory and that is that the Twitter button caches the numbers. Try opening a different browser - I've heard people that said that this works. You should also make sure that you don't generate a new shortlink for every tweet. Tom -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] ReTweet / Count Consistency
Hey Jimbo,
I can understand your confusion. Each of the APIs handles things
differently and their different approaches can make things like this
hard to work out. I've answered your questions inline.
A) Search API: Keyword Search
--
All retweets appear, against matching search term ( some text from the
tweet ) including opening phrase: retweeter RT @retweeted
{tweet.}
This is expected behavior although the Retweet you refer to is the
old style and is not counted as a retweet in our system. Native
retweets show as a single Tweet with a block underneath saying
something like 100+ recent retweets. Native retweets do not show as
separate entries in the search API.
So searching for a keyword will show the original Tweet with a block
underneath indicating how many native retweets that Tweet had. It will
also find old style RTs as to Twitter those are the same as a Tweet.
Example JSON NULL
B) Search API: Username
--
Only the original tweet plus those RT's that have been done the old
fashioned way appear.
If you are searching for just the username and not from:username,
the results behave the same as A.
So searching for a username will show the original Tweet with a block
underneath indicating how many native retweets that Tweet had. It will
also find old style RTs as to Twitter those are the same as a Tweet.
Example twitterapi
X) Twitter Website - twitter.com/#retweeted_of_mine
--
Tweets appear plus lots of information about the retweets; count, user IDs etc.
In some ways it is useful to think of Search as Index which points you
to the actual Tweet. If you think of it that way it makes sense the
website knows more about a Tweet than Search does. twitter.com is also
built to show you complete information about Tweets. Search is
designed to find real-time relevant Tweets about a keyword.
Y) Twitter API - http://api.twitter.com/1/statuses/retweets_of_me.json
--
Original retweeted tweets appear but there's no retweet data. There's
an empty retweet_count node and a FALSE retweeted node ( which is
demonstrably wrong ).
Many developers have been asking for access to the retweet information
displayed on the website so we added the retweet_count and retweeted
nodes last week. Unfortunately we found an issue with those fields
soon after launch which we need to work out. Until then those fields
will not include useful information. We'll be updating this mailing
list with developments.
I hope that answers you questions and clarifies reason for the differences.
Matt Harris
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?hl=en
[twitter-dev] Search API problems...
Hey guys - I'm curious as to know whether there's any problems with the search API? I'm curling from a PHP script, and it keeps timing out with 'couldn't connect to host' errors when my URL is a search (eg: http://search.twitter.com/search.atom?q=test). Interestingly, if I curl either of the following: http://api.twitter.com/1/help/test.xml http://api.twitter.com/1/account/rate_limit_status.xml ...and it doesn't time out, I get a true, and my rate limit is 150/150. I'm not using any authentication, this is a straight request from a script. Could I be on an IP blacklist for search (can I check this?)? I've been pretty careful with my caching, I make nowhere near 150 requests an hour, although my site is on a shared server, so it's entirely plausible someone else has been hammering it. Although if that was the case, would something not show up on the odd times I actually get the rate limit to show something? If anyone can help, or point me in the direction of something I've missed, I'd be eternally grateful... ben -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Search API problems...
There are no known issues with search and running your query works for me. Hey Ben, The Search API does not use authentication and is rate limited differently to the 150 IP requests allowed on the REST API. If you are rate limited on the Search API we would return an error telling you rather than not reply. If the atom link is still not responding can you try http://search.twitter.com/search.json?q=test and let us know the result? Thanks, Matt On Tue, Aug 24, 2010 at 4:28 PM, Ben goo...@iamben.co.uk wrote: Hey guys - I'm curious as to know whether there's any problems with the search API? I'm curling from a PHP script, and it keeps timing out with 'couldn't connect to host' errors when my URL is a search (eg: http://search.twitter.com/search.atom?q=test). Interestingly, if I curl either of the following: http://api.twitter.com/1/help/test.xml http://api.twitter.com/1/account/rate_limit_status.xml ...and it doesn't time out, I get a true, and my rate limit is 150/150. I'm not using any authentication, this is a straight request from a script. Could I be on an IP blacklist for search (can I check this?)? I've been pretty careful with my caching, I make nowhere near 150 requests an hour, although my site is on a shared server, so it's entirely plausible someone else has been hammering it. Although if that was the case, would something not show up on the odd times I actually get the rate limit to show something? If anyone can help, or point me in the direction of something I've missed, I'd be eternally grateful... ben -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris 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?hl=en
Re: [twitter-dev] Re: Twitter Button Counts
Hi Jonathan, The count we use is completely separate to search so no inference should be drawn from there. As well as that the search index is only 5 or so days now so anything Tweeted before then won't be found. When counting URLs we count the final destination of a shortURL so it doesn't matter which is used. Knowing this I took a look at the code you shared and it looks good, but here's the problem I noticed. The URL being Tweeted is not the URL you placed in data-counturl. You can see this when you hover over the short URL in the backtype results. Instead of: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/ You are Tweeting: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button When I replaced your data-counturl with the Tweeted URL I was shown a count of 6. In this case 6 makes sense as this is the number of t.co links created from that longer query string URL. The 3 other URLs are not counted recognised because they have different utm_content and awesm values. I've passed this information onto the Tweet Button team who are working on ways to identify that the URLs like this below are collapsed into the correct URL: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O75utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=tweet-button http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59QYbutm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=backtype-tweetcount http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O74utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=twitter-publisher-author http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/?awesm=59O73utm_medium=awe.sm-twitterutm_source=direct-awe.smutm_content=twitter-publisher-main I hope this explains why your situation occurs, Best, Matt On Tue, Aug 24, 2010 at 10:46 AM, Jonathan Strauss jonat...@snowballfactory.com wrote: Matt, I've been using data-counturl from the start and still seeing 0 counts. Here is the source for the button on http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/ which is showing 0 tweets: a href=http://twitter.com/share; class=twitter-share-button data- url=http://awe.sm/59O75; data-counturl=http:// blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for- wordpress/ data-text=Tweet Button with Shortening for WordPress data-count=vertical data-via=snowballfactory data- related=jhstrauss:Author of the postTweet/ascript type=text/ javascript src=http://platform.twitter.com/widgets.js;/script As you can see, BackType is indexing the tweets correctly: http://www.backtype.com/page/blog.snowballfactory.com%2F2010%2F08%2F15%2Ftweet-button-with-shortening-for-wordpress%2F/conversations Yet Twitter search doesn't appear to be: http://search.twitter.com/search?q=http%3A%2F%2Fblog.snowballfactory.com%2F2010%2F08%2F15%2Ftweet-button-with-shortening-for-wordpress%2F From what I can see, the issue appears to be related to what short URLs Twitter is choosing to index for the count. Thanks, -jonathan On Aug 24, 12:10 am, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This is a repeat of a message on another thread. I've updated the Tweet Button docs today with information which I hope will answer a number of your questions. In particular the example about using a short URL with the parameter data-counturl should help those of you whose counts are staying at 0. http://dev.twitter.com/pages/tweet_button#using-shorturl For reference the documentation URLs are: http://dev.twitter.com/pages/tweet_button and http://dev.twitter.com/pages/tweet_button_faq Hope that helps, Matt On Mon, Aug 23, 2010 at 2:10 AM, artesea ryancul...@gmail.com wrote: Just tried something else, I click on a tweet containing one of my short urls this
Re: [twitter-dev] Re: Recent API changes and new fields
Hey Zac, The Streaming API already has these fields included. Matt On Tue, Aug 24, 2010 at 9:38 AM, Zac Bowling zbowl...@gmail.com wrote: Is there a time line for the streaming API getting these changes? Zac Bowling On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris thematthar...@twitter.com wrote: Hey everyone, Thanks for the questions. I'll try and answer them all in this message. 1) are the counts turned on? This weekend the counts were turned off and have remained off. This is because of some bugs we found in the way the value was calculated. I'll let you know when we have this resolved. 2) Will these fields show up in the Search and Streaming API? The fields are already in the Streaming API but be aware the 'retweeted' field is not meaningful here. This is because the streamed status knows nothing of the connected user. The search API does not include this information. 3) How do I know if the feature is turned off? Tweets will contain a retweeted_count if available. If the service is not enabled newer Tweets will likely be missing their retweeted_count. The safest thing to do is code to handle missing values. If they are present use them, if they are not, treat them the same as when the field didn't exist. This way your code works when the retweeted_count is both enabled and disabled. 4) When was the feature turned on? The service was rolled out the week beginning Aug 16th Hope that answers your questions, Matt On Sat, Aug 21, 2010 at 4:33 PM, Joe j...@ajcomputers.com wrote: will we see this in both search and stream API? On Aug 20, 6:45 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This week we rolled out a couple of new data fields for the status and user objects. For a while it has been difficult for you to get the number of lists a user is listed in, or the number of times a Tweet has been retweeted. You were also finding it hard to know if the user had retweeted the status themselves or not. The feature requests you filed and the messages on the developer mailing list showed this is a pain point for many of you as it uses up many of your hourly API requests. These fields are live now and many of you have already seen them in our API responses. We intended to tell you about these changes before they were live, and in the future for things like this we will, but this time around our system for doing that didn't work. The good news is we know what went wrong and have made the necessary improvements needed to ensure you are notified before the changes happen. The recent changes which have been made affect the user and status objects. In both cases we have added fields: To the user object: --- listed_count represents the number of public lists a user is listed in. This field is an integer. As this is a new field it is possible some users will not have a listed_count value yet. follow_request_sent representing whether the user you are authenticating as has requested to follow the user you are viewing. This will be false unless the friendship request is pending. The field is a boolean and will be true or false. To the status object: - retweet_count represents the number of times a status has been retweeted using the Twitter retweet action. This field is an integer. There will not be a value for this field when the feature is turned off, or the Tweet was created before we added retweet_count support. retweeted represents whether the user you are authenticating as has retweeted this status or not. The field is a boolean and can be true or false. Changes to existing methods -- users/show When requesting data for suspended users the user/show used to return an HTTP 404 status code - it now returns HTTP 403. This change is in response to number of users who were asking if there was a way to know if a user they were getting data for had been deleted or was instead suspended. The change means the API agrees with the twitter.com in that we confirm a user exists, but that you may not see their information because they are suspended. If you call /users/show on a suspended user the API response will include the error message User has been suspended. Please remember we sometimes turn features off to maintain site stability. We recommend you always check a field exists before attempting to use it and be prepared for the value to be empty. This will help ensure your code stays stable if we have to turn features off. We'll also be adding this information to the main API documentation soon. Best, Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources:
[twitter-dev] getting 404 error when trying to subscribe to a list
Using oAuth I am making the following call: POST /1/userid/3968155/subscribers.json where userid is the user whose oAuth tokens are in use and 3968155 is the id of the list i'm trying to subscribe to Twitter returns a stock 404 result I've even tried it with the slug id of the list, same result. I also know I have a valid oAuth environment because i'm getting the list information from a previous valid call to /1/userid/lists/ subscriptions.json and I always do /1/account/verify_credentials.json when i'm working on the library code. any clues? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] getting 404 error when trying to subscribe to a list
Try screen_name instead of userid. I'm not certain but it rings a bell. Not that it shouldn't work with id, of course. On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote: Using oAuth I am making the following call: POST /1/userid/3968155/subscribers.json where userid is the user whose oAuth tokens are in use and 3968155 is the id of the list i'm trying to subscribe to Twitter returns a stock 404 result I've even tried it with the slug id of the list, same result. I also know I have a valid oAuth environment because i'm getting the list information from a previous valid call to /1/userid/lists/ subscriptions.json and I always do /1/account/verify_credentials.json when i'm working on the library code. any clues? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: POST Daily limits and Direct Messages
Hi Dave, Thanks for the reply, and i'm sorry the documentation didn't answer your question. OAuth does have a rate limit of 350 REST API requests per hour which applies mainly to GET requests. This API rate limit is separate to the limits you found on the support pages. In fact, the limits on the support pages are ones which apply if you use the API or not. The options you have are this: If your application requires a higher rate limit you can apply for whitelisting using the Whitelisting Request Form. Be aware that whitelisting is only available to developers and to applications in production though; all other requests are rejected. The link and details of what to expect for this can be found in the Whitelisting section of the Rate Limiting documentation: http://dev.twitter.com/pages/rate-limiting#whitelisting The alternative is to open a support ticket explaining your situation. The user support team will then be able to advise you on what options are available. You can open a ticket using http://bit.ly/twicket Hope that helps, Matt On Tue, Aug 24, 2010 at 9:09 AM, DaveH d...@idreia.com wrote: Matt: Not sure what you want me to pick up in the documentation. I must be missing something. When I read the page on daily POST limits [http://support.twitter.com/ forums/10711/entries/15364] I see: quote Current Twitter Limits The current technical limits for accounts are: Direct Messages: 250 per day. API Requests: 150 per hour. Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. Changes to Account Email: 4 per hour. Following (daily): Please note that this is a technical account limit only, and there are additional rules prohibiting aggressive following behavior. You can find detailed page describing following limits and prohibited behavior on the Follow Limits and Best Practices Page. The technical follow limit is 1,000 per day. Following (account-based): Once an account is following 2,000 other users, additional follow attempts are limited by account-specific ratios. The Follow Limits and Best Practices Page has more information. /quote When I read the page you pointed me to, I see that OAuth calls are 350 per hour. So I am still left with the same question, when we hit the daily POST limit, is there a process to ask for an increase? The documentation says it is controlled at a user level, which implies an increase is possible. Yet the documentation does not explicitly say how an increase is requested. I am sure the answer is obvious, I just have been unable to find it. Looking forward to your reply... Dave -- Matt Harris 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?hl=en
Re: [twitter-dev] getting 404 error when trying to subscribe to a list
I agree this isn't clear in the docs so i'll get onto updating them.
The structure for this URL is:
POST /1/:user/:list_id/subscribers.{format}
where:
:user is the user_id or screen_name of the user who owns the list
:list_id is the ID or slug for the list owned by :user. This isn't
necessarily the display name of the list.
The method will then subscribe the user who you are authenticating as
to the list of subscribers.
For example if I want to subscribe to the world-leaders list created
by the @verified account I would use:
POST /1/verified/world-leaders/subscribers.json
On success the method will return the details of of the list subscribed to.
Hope that helps
Matt
On Tue, Aug 24, 2010 at 6:12 PM, Matthew Terenzio mteren...@gmail.com wrote:
Try screen_name instead of userid. I'm not certain but it rings a bell. Not
that it shouldn't work with id, of course.
On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote:
Using oAuth I am making the following call:
POST /1/userid/3968155/subscribers.json
where userid is the user whose oAuth tokens are in use and 3968155 is
the id of the list i'm trying to subscribe to
Twitter returns a stock 404 result
I've even tried it with the slug id of the list, same result. I also
know I have a valid oAuth environment because i'm getting the list
information from a previous valid call to /1/userid/lists/
subscriptions.json and I always do /1/account/verify_credentials.json
when i'm working on the library code.
any clues?
thanks
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Matt Harris
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?hl=en
[twitter-dev] Re: Twitter Button Counts
Ah, canonicalization. Thanks Matt. As you probably know, those URL parameters (other than awesm=) are standard Google Analytics tracking parameters. So, it's something that should probably be handled better by the counter code. But at least we now know the root cause. Thanks, -jonathan On Aug 24, 5:23 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, The count we use is completely separate to search so no inference should be drawn from there. As well as that the search index is only 5 or so days now so anything Tweeted before then won't be found. When counting URLs we count the final destination of a shortURL so it doesn't matter which is used. Knowing this I took a look at the code you shared and it looks good, but here's the problem I noticed. The URL being Tweeted is not the URL you placed in data-counturl. You can see this when you hover over the short URL in the backtype results. Instead of: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... You are Tweeting: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... When I replaced your data-counturl with the Tweeted URL I was shown a count of 6. In this case 6 makes sense as this is the number of t.co links created from that longer query string URL. The 3 other URLs are not counted recognised because they have different utm_content and awesm values. I've passed this information onto the Tweet Button team who are working on ways to identify that the URLs like this below are collapsed into the correct URL: http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni...http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... I hope this explains why your situation occurs, Best, Matt On Tue, Aug 24, 2010 at 10:46 AM, Jonathan Strauss jonat...@snowballfactory.com wrote: Matt, I've been using data-counturl from the start and still seeing 0 counts. Here is the source for the button on http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... which is showing 0 tweets: a href=http://twitter.com/share; class=twitter-share-button data- url=http://awe.sm/59O75; data-counturl=http:// blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for- wordpress/ data-text=Tweet Button with Shortening for WordPress data-count=vertical data-via=snowballfactory data- related=jhstrauss:Author of the postTweet/ascript type=text/ javascript src=http://platform.twitter.com/widgets.js;/script As you can see, BackType is indexing the tweets correctly: http://www.backtype.com/page/blog.snowballfactory.com%2F2010%2F08%2F1... Yet Twitter search doesn't appear to be: http://search.twitter.com/search?q=http%3A%2F%2Fblog.snowballfactory From what I can see, the issue appears to be related to what short URLs Twitter is choosing to index for the count. Thanks, -jonathan On Aug 24, 12:10 am, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This is a repeat of a message on another thread. I've updated the Tweet Button docs today with information which I hope will answer a number of your questions. In particular the example about using a short URL with the parameter data-counturl should help those of you whose counts are staying at 0. http://dev.twitter.com/pages/tweet_button#using-shorturl For reference the documentation URLs are: http://dev.twitter.com/pages/tweet_button and http://dev.twitter.com/pages/tweet_button_faq Hope that helps, Matt On Mon, Aug 23, 2010 at 2:10 AM, artesea ryancul...@gmail.com wrote: Just tried something else, I click on a tweet containing one of my short urls this actually redirects to http://www.libdemvoice.org/?p=20818utm_source=tweetutm_medium=twitt... by setting data-counturl=http://www.libdemvoice.org/?p=20818; it finally counts all the posts. If you are still seeing zeros, double check to see where you exactly redirect to. Regards Ryan On Aug 22, 12:27 pm, artesea ryancul...@gmail.com wrote: Anyone from Twitter looking at this list??? I now have a post with 32 tweets when looking athttp://twitter.com/#search?q=http%3A%2F%2Fldv.org.uk%2F20818 Yet the post itself is still showing 0. Until this is fixed there is no point having the numbers displayed. Completely useless. Ryan On Aug 19, 9:22 am, artesea ryancul...@gmail.com wrote: I don't give a damn about
Re: [twitter-dev] Re: Need Help!! - How Oauth will work in my case?
Hi Rushikesh, OAuth replaces Basic Auth as the way to authenticate with the Twitter API. If you application didn't require a users password before you won't need it now. In this situation you will probably find this document helpful: http://dev.twitter.com/pages/oauth_single_token If, on the other hand, you were asking users for their username and password you will need to ask the user to grant your application access to their account. This process is explained in the Basic to OAuth transition document: http://dev.twitter.com/pages/basic_to_oauth The oauth_single_token page listed above contains information about some OAuth libraries. We list others which you may want to try here: http://dev.twitter.com/pages/oauth_libraries Regarding your question about not using authentication. If your application doesn't need to make any authenticated calls you could just curl the server for information. If you need to request information from an endpoint which we require authentication for you will need to use OAuth. Also, as Justin said, if your account was whitelisted before, it will be whitelisted on OAuth. Hope that helps, Matt On Tue, Aug 24, 2010 at 3:59 AM, Rushikesh Bhanage rishibhan...@gmail.com wrote: Hi Justin, First of all thank you for your reply. I have some questions in your answer? You'll have to change clients - what clients you are talking about ? Changing auth schemes shouldn't change what you can get out of the API - If it is basic/ oauth , yes I am aware about that. Once you setup your user's app/ids the same whitelist applies - what this means to you? Can you tell me that as my account and IP is white-listed , If I switched from account(id/password) to IP(where I won't need to pass ID/password) on which I am working right now, in that case do I really need to do Oauth for IP also? Lastly congrats that you got all working again. Thank you in advance. On Tue, Aug 24, 2010 at 6:44 AM, Justin justin.carl...@gmail.com wrote: You'll have to change clients, but you can obtain the required tokens to do the same calls. Changing auth schemes shouldn't change what you can get out of the API. Once you setup your user's app/ids the same whitelist applies. I just finished my conversion yesterday and everything's working the same. I use this now: http://github.com/abraham/twitteroauth/tree/master/twitteroauth/ Go up a directory from there to see samples. On Aug 21, 8:47 am, Rushikesh Bhanage rishibhan...@gmail.com wrote: Hi there, I have a white-listed account, but the rate-limit has decreased from 20k before 5 days to 12k right now. Initially I thought that this might be due to twitter running over-capacity because I was busy in finishing part of app to launch it in two days. But i just read one mail from Justin who is having same problem, now I realized that this cut off might be due to basic auth. I was also aware about the basic oauth shutting down, but didn't click the mind. We can switch to Oauth, but here are some doubts: 1. *What my app does*? - in my app, when any twitter user enters his name- we crawl his data thru userstatus method, then we crawl his all the followers and show him his real followers. For this I am using My Twitter Library from Andres Scheffer, to which I pass my white listed account user name and password to get all the data. *Now which Oauth library should I prefer that will meet my requirement?* 2. *How Oauth is going to work*? - I am doubtful that how Oauth is going to work in my case, until now any user can enter his user name and was able to get his result. now will I have to take Oauth from each searched user to show his result? If it is so how can I use my white listed account log ins to get 20k calls. Please clear my doubts. Thank you in advance. -- Matt Harris 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?hl=en
[twitter-dev] Twitter OAuth Authentication Fails
I have three iPhone apps that use OAuth to communicate with Twitter. They have been working well for several months but recently when trying to set-up authentication and exchange the various OAuth tokens using Safari on the iPhone, Safari brings up a page from Twitter that says: Something is technically wrong. Thanks for noticing -- we're going to fix it up and have things back to normal soon. Normally authentication works and the page Twitter returns redirects back to our application on the iPhone. Again, this has all worked for several months until very recently. We just noticed the problem ourselves today. Here's an example authenticate URL that used to work but now fails: http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0AZnHkIwg1GfvRn9HaNMB7q0force_login=true Does anyone out there know what's going wrong? This has all worked for hundreds of thousands of our customers for several months now and nothing in our app has changed in two months. Can anyone shed light on this for me? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Search API problems...
Matt, thanks for the quick response. After an evening of trying to figure out what's going on, it appears to be working again. I guess the problem must have been on my side. Thank you so much for replying so quickly though, and for the explanation on rates and error messages! Many thanks, ben On Aug 25, 1:02 am, Matt Harris thematthar...@twitter.com wrote: There are no known issues with search and running your query works for me. Hey Ben, The Search API does not use authentication and is rate limited differently to the 150 IP requests allowed on the REST API. If you are rate limited on the Search API we would return an error telling you rather than not reply. If the atom link is still not responding can you tryhttp://search.twitter.com/search.json?q=testand let us know the result? Thanks, Matt On Tue, Aug 24, 2010 at 4:28 PM, Ben goo...@iamben.co.uk wrote: Hey guys - I'm curious as to know whether there's any problems with the search API? I'm curling from a PHP script, and it keeps timing out with 'couldn't connect to host' errors when my URL is a search (eg: http://search.twitter.com/search.atom?q=test). Interestingly, if I curl either of the following: http://api.twitter.com/1/help/test.xml http://api.twitter.com/1/account/rate_limit_status.xml ...and it doesn't time out, I get a true, and my rate limit is 150/150. I'm not using any authentication, this is a straight request from a script. Could I be on an IP blacklist for search (can I check this?)? I've been pretty careful with my caching, I make nowhere near 150 requests an hour, although my site is on a shared server, so it's entirely plausible someone else has been hammering it. Although if that was the case, would something not show up on the odd times I actually get the rate limit to show something? If anyone can help, or point me in the direction of something I've missed, I'd be eternally grateful... ben -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris 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?hl=en
Re: [twitter-dev] Twitter OAuth Authentication Fails
Hi Kevin, Thanks for raising this query. We have a fix on it's way out tonight or tomorrow morning for this. Also, whilst this isn't related to the issue you are experiencing I recommended updating your URL to point to our API. All requests for the API should be directed to http://api.twitter.com/1/method. OAuth requests should go to https://api.twitter.com/oauth/method,e.g. https://api.twitter.com/oauth/authenticate Best, Matt On Tue, Aug 24, 2010 at 4:55 PM, Kevin Wallace kevin.wall...@abvio.com wrote: I have three iPhone apps that use OAuth to communicate with Twitter. They have been working well for several months but recently when trying to set-up authentication and exchange the various OAuth tokens using Safari on the iPhone, Safari brings up a page from Twitter that says: Something is technically wrong. Thanks for noticing -- we're going to fix it up and have things back to normal soon. Normally authentication works and the page Twitter returns redirects back to our application on the iPhone. Again, this has all worked for several months until very recently. We just noticed the problem ourselves today. Here's an example authenticate URL that used to work but now fails: http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0AZnHkIwg1GfvRn9HaNMB7q0force_login=true Does anyone out there know what's going wrong? This has all worked for hundreds of thousands of our customers for several months now and nothing in our app has changed in two months. Can anyone shed light on this for me? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris 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?hl=en
[twitter-dev] Re: getting 404 error when trying to subscribe to a list
On Aug 24, 9:27 pm, Matt Harris thematthar...@twitter.com wrote:
I agree this isn't clear in the docs so i'll get onto updating them.
The structure for this URL is:
POST /1/:user/:list_id/subscribers.{format}
where:
:user is the user_id or screen_name of the user who owns the list
:list_id is the ID or slug for the list owned by :user. This isn't
necessarily the display name of the list.
The method will then subscribe the user who you are authenticating as
to the list of subscribers.
For example if I want to subscribe to the world-leaders list created
by the @verified account I would use:
POST /1/verified/world-leaders/subscribers.json
oh my, now that is one not what I gathered from the doc and prior
use...
one set of api calls requires that :userid is the caller (I guess they
are pre-oauthcalypse) and the lists ones are not.
I can see why it would be that way from a REST point of view if I tilt
my head a bit - but yea, some rewording of the doc page is definitely
in order :)
thanks,
On success the method will return the details of of the list subscribed to.
Hope that helps
Matt
On Tue, Aug 24, 2010 at 6:12 PM, Matthew Terenzio mteren...@gmail.com wrote:
Try screen_name instead of userid. I'm not certain but it rings a bell. Not
that it shouldn't work with id, of course.
On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote:
Using oAuth I am making the following call:
POST /1/userid/3968155/subscribers.json
where userid is the user whose oAuth tokens are in use and 3968155 is
the id of the list i'm trying to subscribe to
Twitter returns a stock 404 result
I've even tried it with the slug id of the list, same result. I also
know I have a valid oAuth environment because i'm getting the list
information from a previous valid call to /1/userid/lists/
subscriptions.json and I always do /1/account/verify_credentials.json
when i'm working on the library code.
any clues?
thanks
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Matt Harris
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?hl=en
