Re: [twitter-dev] Incorrect signature while getting home tweets
Now I set to http header name is Authorization
header value =
oauth_consumer_key=**,oauth_nonce=b8qoVIxfQyEOOgu6vHjN215,oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1287389017,oauth_token=*,oauth_version=1.0,page=1
,oauth_signature=cY%2F7W%2FuLWCidUD7KziKFwOcM9RI%3D
http req url = http://api.twitter.com/1/statuses/home_timeline.json?page=1
But Its not working {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json?page=1}
I have posted a tweet successfully in to twitter server using query string
authentication. The followers/following url's working fine using query
string auth params. B Home tweets and credential url was not working.
Could u please help me .. I am waiting for your response.
On Sat, Oct 16, 2010 at 4:08 PM, Tom van der Woerdt i...@tvdw.eu wrote:
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
* Now I set to Http header value
Header name = Authorization
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=*oauth_nonce=QyRr
PmridwwSG6oEsr4EIoauth_signature_method=HMAC-SHA1oauth_timestamp=1287212752oauth_token=***oauth_version=1.0oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
Now i got {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json} exception message.
What can I do for resolve this exception.
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com
wrote:
Without getting to deep into this, some advice:
* Use HTTP header based authentication instead of attaching OAuth
parameters to the query string. It makes it much more difficult to
receive assistance from others when you use query-string based auth
and increases the chances of an encoding error exponentially.
* Avoid strange characters in an oauth_nonce. When possible, avoid
the ~ character entirely -- depending on the language and
libraries you are using, some are less spec compliant than others on
characters like tilde
* That you were able to negotiate oauth_tokens through xAuth is a
good sign that your code does something right. POSTs are harder than
GETs. There must be something simple wrong with your GET. Look very
closely. Compare to the spec if necessary. Compare to other code
that produces the correct results.
Taylor
On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
georgo...@gmail.com mailto:georgo...@gmail.com wrote:
Before I have implemented a twitter client in C# using xAuth
authentication . At that application I have used xauth params
for each url signin. Any problem I didn't get. That aclient
application works fine.
Now I have changed language C# to C. I have used liboauth
library. I got oauth_token and oauth_token_secret values
successfully. Then I have try to get home tweets. But i got
incorrect signature.
Base URL
--
GEThttp%3A%2F%2Fapi.twitter.com
http://2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3DOm
TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
Signature
-
FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324REdirvhD970MRu
oQxPM2uOfzocpkRT3m0LKn0HPDcKkM
URL
--
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Qo
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Qo
auth_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZoauth_signature_method=HMAC-SHA1oauth_timestamp=1287053858
oauth_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7oauth_version=1.0oauth_signature=wgRPZqaIJU%2BrkHOSAN99JreWLr4%3D
Error response look like below.
---
Header received header name:Date Value:Thu, 14 Oct 2010
10:57:39 GMT
NN 2010-10-14 16:27:39.700 Header received header
name:Server Value:hi
NN 2010-10-14 16:27:39.700 Header received header
name:Status Value:401 Unauthorized
NN 2010-10-14 16:27:39.700 Header received header
name:WWW-Authenticate Value:Basic realm=Twitter API
NN 2010-10-14 16:27:39.700 Header received header
name:Content-Type Value:application/json; charset=utf-8
NN 2010-10-14 16:27:39.700 Header received header
Re: [twitter-dev] How to embed my video in newtwitter? oembed?
I have asked the same last week http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6a57ce3cc83e9bcc/6c6e73113e49c3b5?lnk=gst On Sun, Oct 17, 2010 at 10:47 PM, Brent Noorda brent.noo...@gmail.comwrote: I see that newtwitter will now sometimes embed video directly. How to I prepare my site pages so they will also be directly embedded? I'm already supporting oembed. Is oembed used? must I get on a whitelist? what? -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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] Incorrect signature while getting home tweets
could you please help me .. I am waiting for your reply...
On Mon, Oct 18, 2010 at 1:39 PM, Georgooty varghese georgo...@gmail.comwrote:
Now I set to http header name is Authorization
header value =
oauth_consumer_key=**,oauth_nonce=b8qoVIxfQyEOOgu6vHjN215,oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1287389017,oauth_token=*,oauth_version=1.0,page=1
,oauth_signature=cY%2F7W%2FuLWCidUD7KziKFwOcM9RI%3D
http req url =
http://api.twitter.com/1/statuses/home_timeline.json?page=1
But Its not working {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json?page=1}
I have posted a tweet successfully in to twitter server using query string
authentication. The followers/following url's working fine using query
string auth params. B Home tweets and credential url was not working.
Could u please help me .. I am waiting for your response.
On Sat, Oct 16, 2010 at 4:08 PM, Tom van der Woerdt i...@tvdw.eu wrote:
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
* Now I set to Http header value
Header name = Authorization
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=*oauth_nonce=QyRr
PmridwwSG6oEsr4EIoauth_signature_method=HMAC-SHA1oauth_timestamp=1287212752oauth_token=***oauth_version=1.0oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
Now i got {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json} exception message.
What can I do for resolve this exception.
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com
wrote:
Without getting to deep into this, some advice:
* Use HTTP header based authentication instead of attaching OAuth
parameters to the query string. It makes it much more difficult to
receive assistance from others when you use query-string based auth
and increases the chances of an encoding error exponentially.
* Avoid strange characters in an oauth_nonce. When possible, avoid
the ~ character entirely -- depending on the language and
libraries you are using, some are less spec compliant than others on
characters like tilde
* That you were able to negotiate oauth_tokens through xAuth is a
good sign that your code does something right. POSTs are harder than
GETs. There must be something simple wrong with your GET. Look very
closely. Compare to the spec if necessary. Compare to other code
that produces the correct results.
Taylor
On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
georgo...@gmail.com mailto:georgo...@gmail.com wrote:
Before I have implemented a twitter client in C# using xAuth
authentication . At that application I have used xauth params
for each url signin. Any problem I didn't get. That aclient
application works fine.
Now I have changed language C# to C. I have used liboauth
library. I got oauth_token and oauth_token_secret values
successfully. Then I have try to get home tweets. But i got
incorrect signature.
Base URL
--
GEThttp%3A%2F%2Fapi.twitter.com
http://2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3DOm
TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
Signature
-
FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324REdirvhD970MRu
oQxPM2uOfzocpkRT3m0LKn0HPDcKkM
URL
--
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Qo
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Qo
auth_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZoauth_signature_method=HMAC-SHA1oauth_timestamp=1287053858
oauth_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7oauth_version=1.0oauth_signature=wgRPZqaIJU%2BrkHOSAN99JreWLr4%3D
Error response look like below.
---
Header received header name:Date Value:Thu, 14 Oct 2010
10:57:39 GMT
NN 2010-10-14 16:27:39.700 Header received header
name:Server Value:hi
NN 2010-10-14 16:27:39.700 Header received header
name:Status Value:401 Unauthorized
NN 2010-10-14 16:27:39.700 Header received header
name:WWW-Authenticate Value:Basic realm=Twitter API
NN 2010-10-14 16:27:39.700 Header received header
[twitter-dev] tweepy.error.TweepError: Twitter error response: status code = 400
hi,
whenever i call search method i receive tweepy.error.TweepError:
Twitter error response: status code = 400 error. I have checked the
details with tweepy.debug() and i got the following,
connect: (search.twitter.com, 80)
send: 'GET /search.json?q=ipodrpp=100show_user=True HTTP/1.1\r
\nAccept-Encoding: identity\r\nHost: search.twitter.com\r\n\r\n'
reply: 'HTTP/1.1 400 Bad Request\r\n'
header: Date: Mon, 18 Oct 2010 07:11:43 GMT
header: Server: Apache
header: Vary: Accept-Encoding
header: Content-Length: 226
header: Connection: close
header: Content-Type: text/html; charset=iso-8859-1
Traceback (most recent call last):
File stdin, line 1, in module
File stdin, line 3, in twee
File build/bdist.linux-x86_64/egg/tweepy/binder.py, line 178, in
_call
File build/bdist.linux-x86_64/egg/tweepy/binder.py, line 161, in
execute
tweepy.error.TweepError: Twitter error response: status code = 400
I read http error response 400 docs. It was mentioned rate limit
factor does this. but rate_limit_status returned the following,
header: Connection: close
{'reset_time_in_seconds': 1287390651, 'remaining_hits': 150,
'hourly_limit': 150, 'reset_time': 'Mon Oct 18 08:30:51 + 2010'}
I dont know why it is happeningpls help me!!
--
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] Re: retweeted always returing as false in /1/statuses/user_timeline.json
Any update on this issue? I don't see any news in the mailing list :-/ Cheers, Carlos On Sep 4, 8:27 pm, Orian Marx (@orian) or...@orianmarx.com wrote: At this point there are a number of fields on various objects returned by Twitter that should be considered unreliable (mostly on user objects). It might be time for Twitter to consider a better solution than just returning unreliable data, such as either stripping out the fields, giving them an attribute such as fieldstatus=deprecated or fieldstatus=disabled. These expected behaviors are only expected by the engineers on Twitter's end and I've seen lots of posts on the mailinglist where people have had to question why they were getting unreliable data. On Sep 3, 12:25 pm, Matt Harris thematthar...@twitter.com wrote: Hi Michael, Soon after launching those fields we identified some problems with them so had to disable them. That means the behavior you are seeing is expected right now. When the fields are enabled again we'll announce it to this mailing list. Best, Matt On Thu, Sep 2, 2010 at 9:04 PM, Michael Babker mbab...@flbab.com wrote: Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I'veretweetedusing the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? 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, 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-dev] Tweeter and Android
Hi, I am looking to add a tweet button for my Android Application. How best should I do this? Are there any good examples, which use any provided Twitter apis? Ideally open a dialog on android for user name and password then tweet a status? Have noticed some Android Application which tweet but do not seem to be working currently? I believe there has been a change which has caused existing application that tweet to break? Answers with examples would be much appricated. Best Regards George -- 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] Re: libauth library
Using libcurl http://curl.haxx.se/ and a little of my brain, took me a week to get full integration and api support on my app. Implemented the oauth by myself, let curl do the transfers, but watchout for its urlencoding function! It encoded even reserved characters, but that is fixed since 7.21.2. Regards, Miguel. On Oct 15, 6:31 am, Georgooty varghese georgo...@gmail.com wrote: Dear Twitter, Is anybody using liboauth library for twitter authentication?...'' Using this library I got xAuth auth token values.. But using this I didnt get home tweets..etc.. It didnt work any authentication required URL calls.. But Follower status/following status URL working fine... Any body working on twitter development using liboauth library..in C.. Please help me... Regards, George -- 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] Incorrect signature while getting home tweets
When using headers, you need to wrap each value in quotes. The authorization
header should contain only oauth_* parameters, not any additional query
parameters that may have been part of your request.
Here's an example of the same request you're trying to make (with different
keys, but the same basic request). Note the format of the authorization
header.
*Signature Base String*
GEThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DaZj92w9Wna0lSdL8RsGuNPi7YWyLPaVxTX5k1Xqo%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1287412992%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26page%3D1
*Authorization Header*
OAuth oauth_nonce=aZj92w9Wna0lSdL8RsGuNPi7YWyLPaVxTX5k1Xqo,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1287412992,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=Cucyk%2FMx0saSsJA%2B79fe29HZu9Q%3D, oauth_version=1.0
*Executed URL*
http://api.twitter.com/1/statuses/home_timeline.json?page=1
Taylor
On Mon, Oct 18, 2010 at 6:04 AM, Georgooty varghese georgo...@gmail.comwrote:
could you please help me .. I am waiting for your reply...
On Mon, Oct 18, 2010 at 1:39 PM, Georgooty varghese
georgo...@gmail.comwrote:
Now I set to http header name is Authorization
header value =
oauth_consumer_key=**,oauth_nonce=b8qoVIxfQyEOOgu6vHjN215,oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1287389017,oauth_token=*,oauth_version=1.0,page=1
,oauth_signature=cY%2F7W%2FuLWCidUD7KziKFwOcM9RI%3D
http req url =
http://api.twitter.com/1/statuses/home_timeline.json?page=1
But Its not working {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json?page=1}
I have posted a tweet successfully in to twitter server using query string
authentication. The followers/following url's working fine using query
string auth params. B Home tweets and credential url was not working.
Could u please help me .. I am waiting for your response.
On Sat, Oct 16, 2010 at 4:08 PM, Tom van der Woerdt i...@tvdw.eu wrote:
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
* Now I set to Http header value
Header name = Authorization
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=*oauth_nonce=QyRr
PmridwwSG6oEsr4EIoauth_signature_method=HMAC-SHA1oauth_timestamp=1287212752oauth_token=***oauth_version=1.0oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
Now i got {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json} exception message.
What can I do for resolve this exception.
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com
wrote:
Without getting to deep into this, some advice:
* Use HTTP header based authentication instead of attaching OAuth
parameters to the query string. It makes it much more difficult to
receive assistance from others when you use query-string based auth
and increases the chances of an encoding error exponentially.
* Avoid strange characters in an oauth_nonce. When possible, avoid
the ~ character entirely -- depending on the language and
libraries you are using, some are less spec compliant than others
on
characters like tilde
* That you were able to negotiate oauth_tokens through xAuth is a
good sign that your code does something right. POSTs are harder
than
GETs. There must be something simple wrong with your GET. Look very
closely. Compare to the spec if necessary. Compare to other code
that produces the correct results.
Taylor
On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
georgo...@gmail.com mailto:georgo...@gmail.com wrote:
Before I have implemented a twitter client in C# using xAuth
authentication . At that application I have used xauth params
for each url signin. Any problem I didn't get. That aclient
application works fine.
Now I have changed language C# to C. I have used liboauth
library. I got oauth_token and oauth_token_secret values
successfully. Then I have try to get home tweets. But i got
incorrect signature.
Base URL
--
GEThttp%3A%2F%2Fapi.twitter.com
http://2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3DOm
TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
Signature
-
[twitter-dev] apparent new bug with REST favorites API
I have noticed an apparent bug with the REST favorites API which seems to have just started a few days ago, I think around the 12th or 13th Oct. I am working on an app which amongst other things archives a user's favorites. Periodically, the app pages through older pages of favorites to see if any tweets further back in the stream are now favorited, and to see if any older favs have been unfavorited. e.g. /1/favorites.xml?page=20 (as an authenticated user) It appears that only about every other actually favorited tweet is being returned from these requests. This is new behaviour-- it worked correctly last week. Because the app has the older tweets stored, it detects those that are missing from the API response sequence. It is typically about 10 out of 20 missing, typically ~every other one. However, if I check the actual 'missing' favs individually, they do indicate that the authenticated user has favorited them. So it appears that Twitter still considers the missing tweets favorited by the user, but the API is not serving them all up any more, only about half of them. This bug doesn't appear to manifest with 'newer' favs (e.g. the first retrieved page seems okay). -Amy -- 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] Re: twitter button not showing counter
I had the same problem. Not sure if it helps you but it worked when I specified the url, instead of using The URL for the page the button is on. On Oct 17, 1:06 am, Ismael Briasco brias...@gmail.com wrote: There is a problem with the tweet-button since the last days, when nobody shared that link the counter isn't showing 0 anymore... e.g.:http://mashable.com/2006/07/18/tworl-connects-strangers-via-instant-m... Any ideas? -- 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: Search with geocode does not respect search radius?
This is by design for the Search API. When a Tweet doesn't include any Geo information the Search API will instead use the location in the users profile. The Streaming API looks only for Geo information on a Tweet and ignores the user location. If the users location is not important to you this may be a better solution. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, Oct 17, 2010 at 2:41 PM, Daniel daniel.a...@gmail.com wrote: the issue is still happening... You could check it at http://metaki.com Some times the search api query with geo params returns tweets with the lat lon of the BIO and not the lat lon of the tweet!!! You may check this problem for example in Santiago de Chile, or in Buenos Aires. On 16 oct, 05:51, Johannes la Poutre jsixp...@gmail.com wrote: Update: the ticket is closed and @TweepsAround seems to be working fine again. Details:http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris thematthar...@twitter.com wrote: Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread... More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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] Re: twitter button not showing counter
When you use the iframe version of the Tweet Button you need to specify the URL parameter. This is because the iframe code isn't aware of the URL it should be sharing or counting - instead the Share Box flow manages that when the user clicks the Tweet Button. To cause the count to show your iframe could should look similar to this: iframe allowtransparency=true frameborder=0 role=presentation scrolling=no src= http://platform.twitter.com/widgets/tweet_button.html?url=http://google.com; style=width:120px; height:20px;/iframe I hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Oct 18, 2010 at 11:46 AM, K kim...@gmail.com wrote: I had the same problem. Not sure if it helps you but it worked when I specified the url, instead of using The URL for the page the button is on. On Oct 17, 1:06 am, Ismael Briasco brias...@gmail.com wrote: There is a problem with the tweet-button since the last days, when nobody shared that link the counter isn't showing 0 anymore... e.g.: http://mashable.com/2006/07/18/tworl-connects-strangers-via-instant-m... Any ideas? -- 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] Cross-domain policy file
Does Twitter have any plans on when/whether they'll change its current cross-domain policy file? http://api.twitter.com/crossdomain.xml does not allow requests from Flash-based websites and web apps because it restricts response to twitter.com subdomains. http://search.twitter.com/crossdomain.xml, however, does allow Flash requests from any domain. This policy pretty much renders all Flash calls to the API useless (unless they're search calls). One could use proxy scripts, but given the limitations imposed by the Twitter API (150 calls per IP per hour), it means public websites are out of luck if they're getting any kind of public data without authenticating like, say, getting a (public) user timeline. This has been discussed at length in previous threads. Change in crossdomain.xml?? http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8d09970f449abc70 Most curiously, the above thread mentions on March 2008 that Twitter would be moving API calls to api.twitter.com and allowing a more permissive crossdomain policy file there in a few months. This hasn't happened, though, since people have continued to be dumbfounded by the inability to load Twitter data from Flash-based web apps. Twitter Stream crossdomain.xml http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fa7c3f42f85b8d3 I think this decision is specially questionable as the cross-domain restrictions in place do nothing else other than put a tax on what people can do from Flash-based web apps, but also allow any other usage from any other technology, be it a security issue or not. In fact, even using PHP proxies one could make the API calls from Flash (albeit in a restricted manner) so I can't see a real reason for singling out/blocking this platform. Normally, public APIs add no such artificial/ineffective restrictions, and simply allow any kind of connection (doing their own top of their own built-in restrictions and rate limiting)... http://graph.facebook.com/crossdomain.xml - allows connections from all domains http://api.flickr.com/crossdomain.xml - allows connections from all domains http://api.plixi.com/crossdomain.xml - allows connections from all domains http://api.bit.ly/crossdomain.xml - allows connections from all domains http://stream.twitvid.com/crossdomain.xml - allows connections from all domains ...etc etc So, is there any clear reason why the restriction is still in place? Or any idea on when this policy will be reviewed? Thanks, Zeh -- 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] Re: Cross-domain policy file
Just to add some other examples of popular API domains: Youtube API cross-domain policies - allow connections from all (real) domains http://gdata.youtube.com/crossdomain.xml Google search APIs - allow conection from all domains http://ajax.googleapis.com/crossdomain.xml Ebay APIs - allow connection from all domains http://svcs.ebay.com/crossdomain.xml Delicious APIs - allow connections from all domains https://api.del.icio.us/crossdomain.xml Last.fm APIs - allow connections from all domains http://ws.audioscrobbler.com/crossdomain.xml Bing Maps APIs - allow connections from all domains http://ecn.dev.virtualearth.net/crossdomain.xml See a trend here? Zeh On Oct 18, 3:34 pm, zeh fernando z...@zehfernando.com wrote: Does Twitter have any plans on when/whether they'll change its current cross-domain policy file? http://api.twitter.com/crossdomain.xmldoes not allow requests from Flash-based websites and web apps because it restricts response to twitter.com subdomains. http://search.twitter.com/crossdomain.xml, however, does allow Flash requests from any domain. This policy pretty much renders all Flash calls to the API useless (unless they're search calls). One could use proxy scripts, but given the limitations imposed by the Twitter API (150 calls per IP per hour), it means public websites are out of luck if they're getting any kind of public data without authenticating like, say, getting a (public) user timeline. This has been discussed at length in previous threads. Change in crossdomain.xml??http://groups.google.com/group/twitter-development-talk/browse_thread... Most curiously, the above thread mentions on March 2008 that Twitter would be moving API calls to api.twitter.com and allowing a more permissive crossdomain policy file there in a few months. This hasn't happened, though, since people have continued to be dumbfounded by the inability to load Twitter data from Flash-based web apps. Twitter Stream crossdomain.xmlhttp://groups.google.com/group/twitter-development-talk/browse_thread... I think this decision is specially questionable as the cross-domain restrictions in place do nothing else other than put a tax on what people can do from Flash-based web apps, but also allow any other usage from any other technology, be it a security issue or not. In fact, even using PHP proxies one could make the API calls from Flash (albeit in a restricted manner) so I can't see a real reason for singling out/blocking this platform. Normally, public APIs add no such artificial/ineffective restrictions, and simply allow any kind of connection (doing their own top of their own built-in restrictions and rate limiting)... http://graph.facebook.com/crossdomain.xml- allows connections from all domainshttp://api.flickr.com/crossdomain.xml- allows connections from all domainshttp://api.plixi.com/crossdomain.xml- allows connections from all domainshttp://api.bit.ly/crossdomain.xml- allows connections from all domainshttp://stream.twitvid.com/crossdomain.xml- allows connections from all domains ...etc etc So, is there any clear reason why the restriction is still in place? Or any idea on when this policy will be reviewed? Thanks, Zeh -- 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] Re: Cross-domain policy file
Yahoo! maps APIs - allows all domains http://local.yahooapis.com/crossdomain.xml Yahoo! search APIs - allows all domains http://search.yahooapis.com/crossdomain.xml On Oct 18, 3:34 pm, zeh fernando z...@zehfernando.com wrote: Does Twitter have any plans on when/whether they'll change its current cross-domain policy file? http://api.twitter.com/crossdomain.xmldoes not allow requests from Flash-based websites and web apps because it restricts response to twitter.com subdomains. http://search.twitter.com/crossdomain.xml, however, does allow Flash requests from any domain. This policy pretty much renders all Flash calls to the API useless (unless they're search calls). One could use proxy scripts, but given the limitations imposed by the Twitter API (150 calls per IP per hour), it means public websites are out of luck if they're getting any kind of public data without authenticating like, say, getting a (public) user timeline. This has been discussed at length in previous threads. Change in crossdomain.xml??http://groups.google.com/group/twitter-development-talk/browse_thread... Most curiously, the above thread mentions on March 2008 that Twitter would be moving API calls to api.twitter.com and allowing a more permissive crossdomain policy file there in a few months. This hasn't happened, though, since people have continued to be dumbfounded by the inability to load Twitter data from Flash-based web apps. Twitter Stream crossdomain.xmlhttp://groups.google.com/group/twitter-development-talk/browse_thread... I think this decision is specially questionable as the cross-domain restrictions in place do nothing else other than put a tax on what people can do from Flash-based web apps, but also allow any other usage from any other technology, be it a security issue or not. In fact, even using PHP proxies one could make the API calls from Flash (albeit in a restricted manner) so I can't see a real reason for singling out/blocking this platform. Normally, public APIs add no such artificial/ineffective restrictions, and simply allow any kind of connection (doing their own top of their own built-in restrictions and rate limiting)... http://graph.facebook.com/crossdomain.xml- allows connections from all domainshttp://api.flickr.com/crossdomain.xml- allows connections from all domainshttp://api.plixi.com/crossdomain.xml- allows connections from all domainshttp://api.bit.ly/crossdomain.xml- allows connections from all domainshttp://stream.twitvid.com/crossdomain.xml- allows connections from all domains ...etc etc So, is there any clear reason why the restriction is still in place? Or any idea on when this policy will be reviewed? Thanks, Zeh -- 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] Re: Possible to return a year of status data?
Hmm, thank you for that input Tom van der Woerdt; are you aware of any of these sites that have caches tweets? I will have a look at Topsy's search API. Thank you M.Edward On Oct 17, 10:35 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: Have you looked at Topsy's search API? As far as I know, that's the only publicly available tool that indexes tweets further back than Twitter. -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Toggle toggle...@hotmail.com: Hello, I'm working on a final year project at university which incorporates Twitter as its primary data repository. After looking through the API it seems that search queries are capped to 1500 posts: Clients may request up to 1,500 statuses via the page and rpp parameters for the search method. My problem originates from the fact I need to look at status tweets over the past year on a given search query. Assuming I type in the pope on Twitter Search I can only go back to 4 hours ago because of the 1500 cap. What I have noticed however, there is a LOT of noise (irrelevant tweets). My project is based on Natural Language Engineering and so I need quality data. The question I ask, how flexible is the search within the twitter API? Could I potentially construct queries that would return the information I need? I only need tweets that contain the subject matter but are basically not spam. I need tweets about -Real Peoples Opinions- over the last year. What would be the best way to do this? -- 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] Pintme rails rumble twitter account suspended - please help
Hey Dev list members, We're trying to figure out why the account we setup for the rumble was suspended. We sent a tweet with an @reply to a user when someone purchases them a pint on http://pint.me. A couple hours ago one of our team logged into the email account from the service and noticed that there was a suspension notice from twitter. We've sent in two tickets and have seen no response. Any assistance with figuring this out would be much appreciated! -Mark Turner - @amerine -- 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] Change Background Image Not Working . Any help is appreciated
I used the exact same code for the profile pic update except changing
the api function. The profile picture update works, but unfortunately
the background image update fails.
$img_path = $_SERVER[DOCUMENT_ROOT].'/images/twitter_bg/'.$image;
require_once('./application/libraries/tmhOAuth.php');
$oauth_tokens = $this-session-userdata('twitter_oauth_tokens');
$tmhOAuth = new tmhOAuth(array(
'consumer_key'= T_CONSUMER_KEY,
'consumer_secret' = T_CONSUMER_SECRET,
'user_token' = $oauth_tokens['access_token'],
'user_secret' = $oauth_tokens['access_token_secret']
));
$img_post = array('image' = @{$img_path};type=image/jpeg;);
$tmhOAuth-request('POST', $tmhOAuth-url(account/
update_profile_background_image), $img_post,
true, // use auth
true // multipart
);
The picture is jpg and only 40kb
The response I had:
(
[date] = Mon, 18 Oct 2010 23:00:56 GMT
[server] = hi
[status] = 403 Forbidden
[x_transaction] = 1287442856-44067-31467
[code] = 403
[response] = {error:There was a problem with your background
image. Probably too big.,request:/1/account/
update_profile_background_image.json}
Thanks for taking a look.
--
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] Re: twitter button not showing counter
Matt - I posted this same problem under this post: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/58e171bc000aa471# We're specifying the url parameter in the iframe tweet button. If its the root url e.g. http://nowmov.com/; we'll get a number but for specific links e.g. http://nowmov.com/video/video id the count bubble disappears. On Oct 18, 12:23 pm, Matt Harris thematthar...@twitter.com wrote: When you use the iframe version of the Tweet Button you need to specify the URL parameter. This is because the iframe code isn't aware of the URL it should be sharing or counting - instead the Share Box flow manages that when the user clicks the Tweet Button. To cause the count to show your iframe could should look similar to this: iframe allowtransparency=true frameborder=0 role=presentation scrolling=no src=http://platform.twitter.com/widgets/tweet_button.html?url=http://goog...; style=width:120px; height:20px;/iframe I hope that helps, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 18, 2010 at 11:46 AM, K kim...@gmail.com wrote: I had the same problem. Not sure if it helps you but it worked when I specified the url, instead of using The URL for the page the button is on. On Oct 17, 1:06 am, Ismael Briasco brias...@gmail.com wrote: There is a problem with the tweet-button since the last days, when nobody shared that link the counter isn't showing 0 anymore... e.g.: http://mashable.com/2006/07/18/tworl-connects-strangers-via-instant-m... Any ideas? -- 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] Change Background Image Not Working . Any help is appreciated
There's an example in the tmhOAuth github project that has code for this:
http://github.com/themattharris/tmhOAuth/blob/master/examples/images.php
The big difference for background images is remembering to send the filename
as well.
There have also been some users who have found that their version of curl
required changing 'image' = to '@image'
If neither of those work can you share the image that isn't working and
we'll see what could be the problem.
Best
---
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Oct 18, 2010 at 4:04 PM, x.charles.z x.charle...@gmail.com wrote:
I used the exact same code for the profile pic update except changing
the api function. The profile picture update works, but unfortunately
the background image update fails.
$img_path = $_SERVER[DOCUMENT_ROOT].'/images/twitter_bg/'.$image;
require_once('./application/libraries/tmhOAuth.php');
$oauth_tokens = $this-session-userdata('twitter_oauth_tokens');
$tmhOAuth = new tmhOAuth(array(
'consumer_key'= T_CONSUMER_KEY,
'consumer_secret' = T_CONSUMER_SECRET,
'user_token' = $oauth_tokens['access_token'],
'user_secret' = $oauth_tokens['access_token_secret']
));
$img_post = array('image' = @{$img_path};type=image/jpeg;);
$tmhOAuth-request('POST', $tmhOAuth-url(account/
update_profile_background_image), $img_post,
true, // use auth
true // multipart
);
The picture is jpg and only 40kb
The response I had:
(
[date] = Mon, 18 Oct 2010 23:00:56 GMT
[server] = hi
[status] = 403 Forbidden
[x_transaction] = 1287442856-44067-31467
[code] = 403
[response] = {error:There was a problem with your background
image. Probably too big.,request:/1/account/
update_profile_background_image.json}
Thanks for taking a look.
--
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] Trust Level
I am using VB.Net 3.5 and VS 2010. I have a web app that needs to send Tweets when information is made available, such as news updates, new members, etc. But I seem to be having a problem with the Trust level when I publish the application to Rackspace,my web host. I have talked to them about the trust issue but they are unwilling to change the level to Full trust for my app. Anyway here is what I have done so far. I added all 4 required values, ConsumerKey, ConsumerSecret, OAuthToken, and OAuthTokenSecret to the web.config file in the appSettings section of the configuration section. appSettings !-- Twitter and BitLy access keys -- add key=ConsumerKey value=YOUR CONSUMER KEY / add key=ConsumerSecret value=YOUR CONSUMER SECRET KEY / add key=OAuthToken value=YOUR APPS OAUTHTOKEN KEY / add key=OAuthTokenSecret value=YOUR APPS OAUTHTOKEN SECRET KEY / /appSettings If found that by going to twitter.com and signing into the account that is using the application, then go to the Settings page, go to the bottom of the page and click on the API menu option. Once the API page appears you will clik on the button 2, Register An App. On the right side on the new page, you will see a button View Your Applications. If you have previously registered your app, click this button, If not fill out the appliction for a new app. Now at the View your Applications page, select the app you want to get the authorization keys for where is says Edit Details. Now click on the button to the right that says, Application Detail. Here you will find your Consumer Key and your Consumer Secret Key. On the right side of this page you will see the menu option My Access Token, click it and you will find your oauth_token and your oauth_token_secret keys! Not that you have all the keys, put them in the appSettings section of the web.config file. Add Dim twConn As New TwitterVB2.TwitterAPI at the top of the page. I then created a subroutine where I pass in the Tweet: Public Sub PostOnTwitter(ByVal Tweet As String) 'Retrieve Keys from web.config Dim twitterKey As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerKey) Dim twitterSecret As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerSecret) Dim twitterOAuthToken As String = System.Configuration.ConfigurationManager.AppSettings(OAuthToken) Dim twitterOAuthTokenSecret As String = System.Configuration.ConfigurationManager.AppSettings(OAuthTokenSecret) Try twConn.AuthenticateWith(twitterKey, twitterSecret, twitterOAuthToken, twitterOAuthTokenSecret) twConn.Update(Trim(Tweet)) Catch ex As Exception lblError.Text = Twitter Returned: ex.Message End Try End Sub This code works great in an enviornment that allows at least a Medium trust level. However it appears that many of the new hosting envrionments such as Cloud Hosting and others do not allow this trust level automatically! However if the trust level is less than Full on your host you will likely receive the error message: Twitter Returned: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. If anyone has found a fix for this Trust Level issue please post it! -- 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] Snowflake: An update and some very important information
Last week you may remember Twitter planned to enable the new Status ID
generator - 'Snowflake' but didn't. The purpose of this email is to explain
the reason why this didn't happen, what we are doing about it, and what the
new release plan is.
So what is Snowflake?
--
Snowflake is a service we will be using to generate unique Tweet IDs. These
Tweet IDs are unique 64bit unsigned integers, which, instead of being
sequential like the current IDs, are based on time. The full ID is composed
of a timestamp, a worker number, and a sequence number.
The problem
-
Before launch it came to our attention that some programming languages such
as Javascript cannot support numbers with 53bits. This can be easily
examined by running a command similar to: (90071992547409921).toString() in
your browsers console or by running the following JSON snippet through your
JSON parser.
{id: 10765432100123456789, id_str: 10765432100123456789}
In affected JSON parsers the ID will not be converted successfully and will
lose accuracy. In some parsers there may even be an exception.
The solution
To allow javascript and JSON parsers to read the IDs we need to include a
string version of any ID when responding in the JSON format. What this means
is Status, User, Direct Message and Saved Search IDs in the Twitter API will
now be returned as an integer and a string in JSON responses. This will
apply to the main Twitter API, the Streaming API and the Search API.
For example, a status object will now contain an id and an id_str. The
following JSON representation of a status object shows the two versions of
the ID fields for each data point.
[
{
coordinates: null,
truncated: false,
created_at: Thu Oct 14 22:20:15 + 2010,
favorited: false,
entities: {
urls: [
],
hashtags: [
],
user_mentions: [
{
name: Matt Harris,
id: 777925,
id_str: 777925,
indices: [
0,
14
],
screen_name: themattharris
}
]
},
text: @themattharris hey how are things?,
annotations: null,
contributors: [
{
id: 819797,
id_str: 819797,
screen_name: episod
}
],
id: 12738165059,
id_str: 12738165059,
retweet_count: 0,
geo: null,
retweeted: false,
in_reply_to_user_id: 777925,
in_reply_to_user_id_str: 777925,
in_reply_to_screen_name: themattharris,
user: {
id: 6253282
id_str: 6253282
},
source: web,
place: null,
in_reply_to_status_id: 12738040524
in_reply_to_status_id_str: 12738040524
}
]
What should you do - RIGHT NOW
--
The first thing you should do is attempt to decode the JSON snippet above
using your production code parser. Observe the output to confirm the ID has
not lost accuracy.
What you do next depends on what happens:
* If your code converts the ID successfully without losing accuracy you are
OK but should consider converting to the _str versions of IDs as soon as
possible.
* If your code has lost accuracy, convert your code to using the _str
version immediately. If you do not do this your code will be unable to
interact with the Twitter API reliably.
* In some language parsers, the JSON may throw an exception when reading the
ID value. If this happens in your parser you will need to ‘pre-parse’ the
data, removing or replacing ID parameters with their _str versions.
Summary
-
1) If you develop in Javascript, know that you will have to update your code
to read the string version instead of the integer version.
2) If you use a JSON decoder, validate that the example JSON, above, decodes
without throwing exceptions. If exceptions are thrown, you will need to
pre-parse the data. Please let us know the name, version, and language of
the parser which throws the exception so we can investigate.
Timeline
---
by 22nd October 2010 (Friday): String versions of ID numbers will start
appearing in the API responses
4th November 2010 (Thursday) : Snowflake will be turned on but at ~41bit
length
26th November 2010 (Friday) : Status IDs will break 53bits in length and
cease being usable as Integers in Javascript based languages
We understand this isn’t as seamless a transition as we had planned and
appreciate for some of you this change requires an update to your code.
We’ve tried to give as much time as possible for you to make the migration
and update your code to use the new string representations.
Our own products and tools are affected by the change and we will be making
available any pre-parsing snippets we have created to ensure code continues
to work with the new IDs.
Thanks for your support and understanding.
---
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources:
[twitter-dev] Re: Snowflake: An update and some very important information
Thanks to @gotwalt for spotting the missing commas.
Fixed JSON sample ...
[
{
coordinates: null,
truncated: false,
created_at: Thu Oct 14 22:20:15 + 2010,
favorited: false,
entities: {
urls: [
],
hashtags: [
],
user_mentions: [
{
name: Matt Harris,
id: 777925,
id_str: 777925,
indices: [
0,
14
],
screen_name: themattharris
}
]
},
text: @themattharris hey how are things?,
annotations: null,
contributors: [
{
id: 819797,
id_str: 819797,
screen_name: episod
}
],
id: 12738165059,
id_str: 12738165059,
retweet_count: 0,
geo: null,
retweeted: false,
in_reply_to_user_id: 777925,
in_reply_to_user_id_str: 777925,
in_reply_to_screen_name: themattharris,
user: {
id: 6253282,
id_str: 6253282
},
source: web,
place: null,
in_reply_to_status_id: 12738040524,
in_reply_to_status_id_str: 12738040524
}
]
Best,
@themattharris
On Oct 18, 5:19 pm, Matt Harris thematthar...@twitter.com wrote:
Last week you may remember Twitter planned to enable the new Status ID
generator - 'Snowflake' but didn't. The purpose of this email is to explain
the reason why this didn't happen, what we are doing about it, and what the
new release plan is.
So what is Snowflake?
--
Snowflake is a service we will be using to generate unique Tweet IDs. These
Tweet IDs are unique 64bit unsigned integers, which, instead of being
sequential like the current IDs, are based on time. The full ID is composed
of a timestamp, a worker number, and a sequence number.
The problem
-
Before launch it came to our attention that some programming languages such
as Javascript cannot support numbers with 53bits. This can be easily
examined by running a command similar to: (90071992547409921).toString() in
your browsers console or by running the following JSON snippet through your
JSON parser.
{id: 10765432100123456789, id_str: 10765432100123456789}
In affected JSON parsers the ID will not be converted successfully and will
lose accuracy. In some parsers there may even be an exception.
The solution
To allow javascript and JSON parsers to read the IDs we need to include a
string version of any ID when responding in the JSON format. What this means
is Status, User, Direct Message and Saved Search IDs in the Twitter API will
now be returned as an integer and a string in JSON responses. This will
apply to the main Twitter API, the Streaming API and the Search API.
For example, a status object will now contain an id and an id_str. The
following JSON representation of a status object shows the two versions of
the ID fields for each data point.
[
{
coordinates: null,
truncated: false,
created_at: Thu Oct 14 22:20:15 + 2010,
favorited: false,
entities: {
urls: [
],
hashtags: [
],
user_mentions: [
{
name: Matt Harris,
id: 777925,
id_str: 777925,
indices: [
0,
14
],
screen_name: themattharris
}
]
},
text: @themattharris hey how are things?,
annotations: null,
contributors: [
{
id: 819797,
id_str: 819797,
screen_name: episod
}
],
id: 12738165059,
id_str: 12738165059,
retweet_count: 0,
geo: null,
retweeted: false,
in_reply_to_user_id: 777925,
in_reply_to_user_id_str: 777925,
in_reply_to_screen_name: themattharris,
user: {
id: 6253282
id_str: 6253282
},
source: web,
place: null,
in_reply_to_status_id: 12738040524
in_reply_to_status_id_str: 12738040524
}
]
What should you do - RIGHT NOW
--
The first thing you should do is attempt to decode the JSON snippet above
using your production code parser. Observe the output to confirm the ID has
not lost accuracy.
What you do next depends on what happens:
* If your code converts the ID successfully without losing accuracy you are
OK but should consider converting to the _str versions of IDs as soon as
possible.
* If your code has lost accuracy, convert your code to using the _str
version immediately. If you do not do this your code will be unable to
interact with the Twitter API reliably.
* In some language parsers, the JSON may throw an exception when reading the
ID value. If this happens in your parser you will need to ‘pre-parse’ the
data, removing or replacing ID parameters with their _str versions.
Summary
-
1) If you develop in Javascript, know that you will have to update your code
to read the string version instead of the integer version.
2)
Re: [twitter-dev] Maximum username length
On Thu, Mar 11, 2010 at 7:12 AM, Nick Telford nick.telf...@tweetmeme.com wrote: Hi everyone, Can we get a clarification on the maximum length of a username? The twitter.com frontend refuses to accept anything over 15 characters, and I'm fairly sure 15 characters is mentioned elsewhere in some documentation. However, we're seeing an increasing number of users who have (somehow) managed to register with a longer username: http://twitter.com/toasteroverheated http://twitter.com/veganstraightedge http://twitter.com/Laura_Villas_Boas http://twitter.com/colepatrickturner The number of user's that have managed to generate usernames over 15 characters in length is increasing, although not by a lot. It wouldn't surprise me if there are 100 users affected. A clarification on the absolute limit would be useful for us to determine how best to optimise our storage of usernames. I think it's really important get an specific definition on which usernames we may expect historically, and what's the actual username criteria. Can any twitter dev explain how we may validate usernames and what's the best way to store them into a db? Thanks! -- Slds, Gonzalo. -- 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] Incorrect signature while getting home tweets
Thank u twitter.
Could you specify what is header name?
On Mon, Oct 18, 2010 at 8:15 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
When using headers, you need to wrap each value in quotes. The
authorization header should contain only oauth_* parameters, not any
additional query parameters that may have been part of your request.
Here's an example of the same request you're trying to make (with different
keys, but the same basic request). Note the format of the authorization
header.
*Signature Base String*
GEThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DaZj92w9Wna0lSdL8RsGuNPi7YWyLPaVxTX5k1Xqo%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1287412992%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26page%3D1
*Authorization Header*
OAuth oauth_nonce=aZj92w9Wna0lSdL8RsGuNPi7YWyLPaVxTX5k1Xqo,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1287412992,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=Cucyk%2FMx0saSsJA%2B79fe29HZu9Q%3D, oauth_version=1.0
*Executed URL*
http://api.twitter.com/1/statuses/home_timeline.json?page=1
Taylor
On Mon, Oct 18, 2010 at 6:04 AM, Georgooty varghese
georgo...@gmail.comwrote:
could you please help me .. I am waiting for your reply...
On Mon, Oct 18, 2010 at 1:39 PM, Georgooty varghese
georgo...@gmail.comwrote:
Now I set to http header name is Authorization
header value =
oauth_consumer_key=**,oauth_nonce=b8qoVIxfQyEOOgu6vHjN215,oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1287389017,oauth_token=*,oauth_version=1.0,page=1
,oauth_signature=cY%2F7W%2FuLWCidUD7KziKFwOcM9RI%3D
http req url =
http://api.twitter.com/1/statuses/home_timeline.json?page=1
But Its not working {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json?page=1}
I have posted a tweet successfully in to twitter server using query
string authentication. The followers/following url's working fine using
query string auth params. B Home tweets and credential url was not working.
Could u please help me .. I am waiting for your response.
On Sat, Oct 16, 2010 at 4:08 PM, Tom van der Woerdt i...@tvdw.euwrote:
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct
syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
* Now I set to Http header value
Header name = Authorization
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=*oauth_nonce=QyRr
PmridwwSG6oEsr4EIoauth_signature_method=HMAC-SHA1oauth_timestamp=1287212752oauth_token=***oauth_version=1.0oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
Now i got {error:Could not authenticate
you.,request:/1/statuses/home_timeline.json} exception message.
What can I do for resolve this exception.
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com
wrote:
Without getting to deep into this, some advice:
* Use HTTP header based authentication instead of attaching OAuth
parameters to the query string. It makes it much more difficult to
receive assistance from others when you use query-string based
auth
and increases the chances of an encoding error exponentially.
* Avoid strange characters in an oauth_nonce. When possible, avoid
the ~ character entirely -- depending on the language and
libraries you are using, some are less spec compliant than others
on
characters like tilde
* That you were able to negotiate oauth_tokens through xAuth is a
good sign that your code does something right. POSTs are harder
than
GETs. There must be something simple wrong with your GET. Look
very
closely. Compare to the spec if necessary. Compare to other code
that produces the correct results.
Taylor
On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
georgo...@gmail.com mailto:georgo...@gmail.com wrote:
Before I have implemented a twitter client in C# using xAuth
authentication . At that application I have used xauth params
for each url signin. Any problem I didn't get. That aclient
application works fine.
Now I have changed language C# to C. I have used liboauth
library. I got oauth_token and oauth_token_secret values
successfully. Then I have try to get home tweets. But i got
incorrect signature.
Base URL
--
GEThttp%3A%2F%2Fapi.twitter.com
http://2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3DOm
TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
[twitter-dev] [twitcurl Lib] Direct Message signbase string
I'm using twitcurl library. When you send a direct message an error occurs. Error Message : errorIncorrect signature/error When I send a message signbase string is shown below. POSThttp%3A%2F%2Ftwitter.com%2Fdirect_messages%2Fnew.xml%3F screen_name%3DRECEIVERNM oauth_consumer_key%3DCKEY%26 oauth_nonce%3D1287392764ed%26 oauth_signature_method%3DHMAC-SHA1%26 oauth_timestamp%3D1287392764%26 oauth_token%3DATOKEN%26 oauth_version%3D1.0%26 text%3D12345 See you on the signbase wrong ones? If you know something is wrong, please correct parts. -- 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
