[twitter-dev] Re: Link Wrapping and Favorites
I just switched over to include_entities, and I'm also not seeing the entities come back for favorites or mentions. Works great for home_timeline and retweets. I can fall back on my own parsing when entities are missing, but for consistently I definitely prefer letting Twitter do this work. Is it a known issue that it's missing for favorites and mentions, and if so any idea when it can be rolled out across the board? Thanks! On Jun 13, 6:17 am, Georgios kapero...@gmail.com wrote: Hi I have a website that focuses on Twitter favorites (http://favorious.com ) and I have tried to implement the new Link Wrapping guidelines using entities. However ?include_entities=true is not working (I tried getting a @raffi tweet that I have favorited). The documentation (http://dev.twitter.com/doc/get/favorites) also doesn't mention anything about entities for this. Does Twitter plan to roll out link wrapping info for Favorites? If not, then I cannot implement the new Link Wrapping according to Twitter's TOS. Thanks Georgioshttp://favorious.com- Only the best of Twitter, based on favorites.
[twitter-dev] Re: secure key - desktop applications?
Sure, that's an option, but not one which I would likely take, for multiple reasons, including rate limiting which I would like to apply to my client (my server is whitelisted so all accounts would suddenly get 2 - that's a bad idea). I was wondering how the big clients do this, like TweetDeck, Twitter for iPhone, Gwibber, DestroyTwitter, TwitterBerry, etc. Is their key storage so secure that they have never had a key leak, or do they implement oAuth differently? I doubt that all of their requests go via a server... Also, I know that this may sound a bit stupid, but I'd like to propose a change in oAuth (1.1?) so that it's no longer needed to supply both keys. Where can I do this? Tom On Jun 24, 12:04 am, Jef Poskanzer jef.poskan...@gmail.com wrote: You're right in theory that requests after the initial authentication step should not really need the app's credentials, a single authentication token secret ought to suffice and the service (twitter) should remember which app each token came from. But shrug, that's just not the way OAuth works. It's not twitter's fault, they are just following the spec. I can't even say it's particularly unreasoinable - flickr's similar three-party authentication protocol is much simpler than OAuth but it still uses the app key on every request. As for embedding the app secret in desktop and mobile executables and trusting that it will be just too difficult for miscreants to extract, I say don't do it. The OAuth RFC says so too. Keeping the secret in a server-side proxy is probably the best solution.
[twitter-dev] Re: Kwwika - World Cup Web Development competition announced using Twitter World Cup data
A Kwwik update on this: We've had a few entries for this competition but not too many so the opportunity to win that iPad is pretty good due to the low number of competitor. The deadline for entry is July 1st but the main thing is to have something in place for that date and you can then build on it. We've also managed to get Opta Sports involved and they are now pushing real-time updates about live games through. So, this is a great chance to play with some cool real-time Opta stats as well as #worldcup real-time tweets. A final incentive is that we have a potential client lined up to use Kwwika and by building an application using Kwwika you put yourself in the shop window to be considered for that contract. As before, if you are interested in entering the competition, or just having a play with Kwwika, please get in touch (p...@kwwika.com). Phil On Jun 14, 9:41 pm, Phil Leggetter p...@leggetter.co.uk wrote: Hi Dean, Not really :o) I'm looking to try and drum up some interest in this competition. In addition to real-time twitter push updates we'll also be pushing out some world class World Cup sports data to be used in the mashup. Phil On Jun 12, 7:40 pm, Dean Collins d...@cognation.net wrote: Hi Phil, Check out the twitter integration withwww.LiveWorldCupChat.comif that's what you want. Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Phil Leggetter Sent: Saturday, 12 June 2010 11:13 AM To: Twitter Development Talk Subject: [twitter-dev]Kwwika- World Cup Web Development competition announced using Twitter World Cup data Hello all! I'm working on a project calledKwwikawhich allows anybody to add real-time push functionality to your website. To try and get people developing usingKwwikawe've decided to create a competition that will hopefully encourage web developers to sign up for the opportunity of winning an Apple iPad. The reason I'm messaging the group is that the majority of data that we are using is from the Twitter streaming API, something a lot of you may be familiar with. The purpose of the competition is to see who can build the most engaging real-time push World Cup 2010 web application. More details can be found in the following locations: * Blog post announcment: http://blog.kwwika.com/kwwika-world-cup-2010-real- time-push-web-app *KwwikaWiki with competition details: http://wiki.kwwika.com/competitions/world-cup-2010-real-time-push-web-ap p- competition * A real-time push World Cup demo created to give people an idea of what can be built: http://kwwika.com/Standalone/Demos/WorldCup2010/#SouthAfrica If you have any questions or idea please feel free to get in touch with me via p...@kwwika.com Thanks, Phil Leggetter
[twitter-dev] Difference between Connect with Twitter and Sign in with Twitter
Hi there, I'm having an headache, trying to understand the difference between the two methods in object. They're both using OAuth, is that correct? I just noticed that Connect opens up a popup (and it's using JavaScript), sign in does not; have I to intend that diversity lays on authorization flow and that sign in is language indipendent? Anyone can explain me that in the simpliest way possible? Sorry for my english, I'm so confused. Many thanks.
[twitter-dev] Access Token
HI I have an requirement of reading all the tweets that has specifed word and replying to that tweeet. I am able to query all the tweets while replying to the tweet i am getting error.Couldnt autheticate the user. Please let me know how can i get the access token for the user. Please help me in resolving this issue. Regards Manjunatha M.N
[twitter-dev] Re: Problems with filtered Streaming API and Location
I downloaded the Twitter iPhone app (v. 3.0.1c) and when I use it my geocoded tweets are showing up in the location-filtered stream. So, seems there is Twitterrific-specific issue with location - I will pull and compare tweets from both apps and compare them to see if I can figure out whats wrong. Still not sure why explicitly specifying a Place when tweeting on the twitter website, that place isn't coming through but instead a generic Neighbourhood or City is specified. I guess this Place stuff is relatively new and still has some quirks to work out. On Jun 23, 8:50 pm, metafedora metafed...@gmail.com wrote: The api request I am making looks like this POST /1/statuses/filter.json HTTP/1.1 Authorization: Basic bVW0YWIZIG8yYTp3d3F0eGVz X-Twitter-Client-URL:http://twitter4j.org/en/twitter4j-2.1.3-SNAPSHOT(build: e8b3d79cea14c4f8cb20101726d92169b905da0e).xml X-Twitter-Client: Twitter4J Accept-Encoding: gzip User-Agent: twitter4j X-Twitter-Client-Version: 2.1.3 Connection: close Content-Type: application/x-www-form-urlencoded Content-Length: 49 Host: stream.twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 count=0locations=-97.42%2C32.56%2C-96.57%2C33.21 This should return a sample of all geocoded tweets within the geographic area, defined by the bounding box (it surrounds the Dallas- Ft. Worth area where I live). Using Safari, I log into Twitter with my test user: GiscJTest1 - it asks to use location, to which I answer OK. I select a location (such as the coffeeshop down the street from me) from the list and post a tweet. I see the tweet in my api output, but instead of the location I selected, it just says East Dallas, TX. Also, there is no lat-long. Then I try it with Twiterrific on my iPhone - again using GiscJTest1 - and with Location enabled. I *never* see these tweets in the stream output. I've tried many times, but the iPhone tweets do not show up in the stream. Can anyone explain this behavior?
[twitter-dev] 404 Problem 3 day
i cant connect twitter api 3 days . I get follower and following count but not get timeline and other action. What is changing ?
[twitter-dev] position of the widget
Hello, anyone knows if there is any attribute to set the position of the twitter widget??I need to put my widget code inside a div.
[twitter-dev] Re: position of the widget
I have the following div and I want my widget inside of this div...here is
the css of the twitter div:
.twitter{
background: url(../images/bg/bg_twitter.gif) 0 0 no-repeat;
width: 207px;
height: 276px;
float: left;
}
here is the code of the div:
div class=twitter
ul
li@virtumony Lançamento!! 24/05/2010!! Aguardem...
br / spanAbout 6 hours ago/span/li
/ul
/div
if someone can help me...i already putted the twitter code inside the div
but the result was very ugly...is there an attribute to the widget
positon,anyone knows a solution??
2010/6/24 André Luís Moura Lima azdr3mi...@gmail.com
Hello,
anyone knows if there is any attribute to set the position of the twitter
widget??I need to put my widget code inside a div.
[twitter-dev] Can I use offline access of twitter using anywhere api?
Can I use offline access of twitter using anywhere api? just like the facebook javascript SDK.
[twitter-dev] Re: Twitter Abrahams library
I manage with:
$CONSUMER_KEY = $this-config-item('CONSUMER_KEY');
$CONSUMER_SECRET = $this-config-item('CONSUMER_SECRET');
$connection = new TwitterOAuth($CONSUMER_KEY, $CONSUMER_SECRET);
$response = json_decode($connection-http('http://api.twitter.com/1/
statuses/public_timeline.json', 'GET'));
The $response object have the 20 most recent tweets.
Thanks
On Jun 23, 11:39 am, luisg luisfmgoncal...@gmail.com wrote:
Hello all,
I'm testing Abraham twitter library and works really nice.
But I have a doubt for more simple stuff... Imagine that I want to do
a call to twitter without authenticate first. For example, to get the
last 20 public tweets I dont need to authenticate first, right? So,
you have any example how to do it?
I looked at the http method in twitteroauth class and I tried
something like:
$content = json_decode($connection-http('https://api.twitter.com/1/
statuses/public_timeline.json', 'GET'));
but my doubt is how can I create the $connection object? I tried
something like:
$connection = new TwitterOAuth($CONSUMER_KEY, $CONSUMER_SECRET);
But didn't work.
Can you help me?
P.S.: sorry for the stupid question...
[twitter-dev] Re: Streaming API OAuth explanation?
I'm getting this response: HTTP/1.1 401 Unauthorized Content-Length: 1296 Cache-Control: must-revalidate,no-cache,no-store Content-Type: text/html; charset=iso-8859-1 Server: Jetty(6.1.17) WWW-Authenticate: Basic realm=Firehose html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 UNAUTHORIZED/title /head body h2HTTP ERROR: 401/h2 pProblem accessing /1/statuses/filter.json. Reason: preUNAUTHORIZED/pre/p hr /ismallPowered by Jetty:///small/i Here's what I POSTed(oauth tokens are filtered out): REQUEST: POST http://stream.twitter.com/1/statuses/filter.json Authorization: OAuth oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC- SHA1,oauth_signature=,oauth_version=1.0, Content-Type: application/x-www-form-urlencoded Vary: Accept-Encoding Connection: close source=softwarenamedelimited=1follow=156934710 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote: OAuthshould work fine onstream.twitter.com -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jun 22, 2010 at 10:00 AM, Wil willi...@gmail.com wrote: I'm a bit dumbfounded here... I've been trying to login tostream.twitter.com usingOAuth (particularly, I've been trying to access http://stream.twitter.com/1/statuses/filter.json?follow=). I used the access keys obtained fromhttps://api.twitter.com/oauth/access_token however, I've been getting 401 errors. I've tried basic authentication and it works fine. Does that mean thatstream:statuses/filter is still can only accept basic authentication? Regards, Wil On May 25, 5:51 am, John Kalucki j...@twitter.com wrote: We haven't announced our plans for streaming andoAuth, beyond stating that User Streams will only be onoAuth. On Mon, May 24, 2010 at 1:57 PM, 140dev 140...@gmail.com wrote: Does this mean that the streaming API will also make the switch from basic authentication toOAuthat the end of June? On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com wrote: OAuthis now enabled onstream.twitter.com. I'll also send a note out to the announce list ---Mark http://twitter.com/mccv On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin aran...@gmail.com wrote: Hi, Is there an ETA for enablingoauthonstream.twitter.com? Thanks, Aaron On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote: OAuthis not enabled onstream.twitter.com. You can try on chirpstream.twitter.com. On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com wrote: I am writing my own c++ basedOAuthlibrary. I know there is liboauth but I like to do things myself to learn. Anyhow I am trying to accesshttp:// stream.twitter.com/1/statuses/sample.xml and I keep getting 401. I have verified pretty much every parameter, and used the tool on http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... to verify my signature is correct. I used twurl to obtain the user access tokens to my account. After doing some reading I'm no longer convinced that thestreaming server even supportsoauth. can you fill me in on the current status ofstream.twitter.com and oauth? thanks! Lucas On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote: Thanks Taylor for the very detailed and helpful response! Jonathon On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jonathon, ForStreamingAPI access that isn't from the perspective of a user's account, you would use two-leggedOAuthto establish authentication instead of basic auth. A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have a specific resource you are trying to access, you have some parameters you want to pass to that resource, and you have anOAuthconsumer key andOAuth consumer secret. Which is unlike three-leggedOAuthwhere you also have oauth_tokens representing either a user/access_token or a request token in addition to the rest. But the rules remain the same. You take all theOAuthparameters and the parameters you are sending to the resource, organize them, build a signature base string, then sign that with your consumer secret and send the request on to Twitter properly signed. The only difference is that there is no oauth_token and oauth_token_secret getting involved in the mix. This is essentially what a two-legged request to thestreamingAPI would look like: Signature Base String GEThttp%3A%2F%2Fstream.twitter.com %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2
Re: [twitter-dev] Re: Streaming API OAuth explanation?
Aside from the oAuth issue, which others can address, the only valid delimited value is length. -John On Thu, Jun 24, 2010 at 7:58 AM, Wil willi...@gmail.com wrote: I'm getting this response: HTTP/1.1 401 Unauthorized Content-Length: 1296 Cache-Control: must-revalidate,no-cache,no-store Content-Type: text/html; charset=iso-8859-1 Server: Jetty(6.1.17) WWW-Authenticate: Basic realm=Firehose html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 UNAUTHORIZED/title /head body h2HTTP ERROR: 401/h2 pProblem accessing /1/statuses/filter.json. Reason: preUNAUTHORIZED/pre/p hr /ismallPowered by Jetty:///small/i Here's what I POSTed(oauth tokens are filtered out): REQUEST: POST http://stream.twitter.com/1/statuses/filter.json Authorization: OAuth oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC- SHA1,oauth_signature=,oauth_version=1.0, Content-Type: application/x-www-form-urlencoded Vary: Accept-Encoding Connection: close source=softwarenamedelimited=1follow=156934710 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote: OAuthshould work fine onstream.twitter.com -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jun 22, 2010 at 10:00 AM, Wil willi...@gmail.com wrote: I'm a bit dumbfounded here... I've been trying to login tostream.twitter.com usingOAuth (particularly, I've been trying to access http://stream.twitter.com/1/statuses/filter.json?follow=). I used the access keys obtained fromhttps:// api.twitter.com/oauth/access_token however, I've been getting 401 errors. I've tried basic authentication and it works fine. Does that mean thatstream:statuses/filter is still can only accept basic authentication? Regards, Wil On May 25, 5:51 am, John Kalucki j...@twitter.com wrote: We haven't announced our plans for streaming andoAuth, beyond stating that User Streams will only be onoAuth. On Mon, May 24, 2010 at 1:57 PM, 140dev 140...@gmail.com wrote: Does this mean that the streaming API will also make the switch from basic authentication toOAuthat the end of June? On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com wrote: OAuthis now enabled onstream.twitter.com. I'll also send a note out to the announce list ---Mark http://twitter.com/mccv On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin aran...@gmail.com wrote: Hi, Is there an ETA for enablingoauthonstream.twitter.com? Thanks, Aaron On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote: OAuthis not enabled onstream.twitter.com. You can try on chirpstream.twitter.com. On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com wrote: I am writing my own c++ basedOAuthlibrary. I know there is liboauth but I like to do things myself to learn. Anyhow I am trying to accesshttp:// stream.twitter.com/1/statuses/sample.xml and I keep getting 401. I have verified pretty much every parameter, and used the tool on http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... to verify my signature is correct. I used twurl to obtain the user access tokens to my account. After doing some reading I'm no longer convinced that thestreaming server even supportsoauth. can you fill me in on the current status ofstream.twitter.comand oauth? thanks! Lucas On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote: Thanks Taylor for the very detailed and helpful response! Jonathon On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jonathon, ForStreamingAPI access that isn't from the perspective of a user's account, you would use two-leggedOAuthto establish authentication instead of basic auth. A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have a specific resource you are trying to access, you have some parameters you want to pass to that resource, and you have anOAuthconsumer key andOAuth consumer secret. Which is unlike three-leggedOAuthwhere you also have oauth_tokens representing either a user/access_token or a request token in addition to the rest. But the rules remain the same. You take all theOAuthparameters and the parameters you are sending to the resource, organize them, build a signature base string, then sign that with your consumer secret and send the request on to Twitter properly signed. The only difference is that there is no oauth_token and oauth_token_secret getting involved in the mix. This is essentially
Re: [twitter-dev] Re: Link Wrapping and Favorites
Hi Manton, I see the entities coming through when I request my mentions timeline.. http://api.twitter.com/1/statuses/mentions.xml?include_entities=true Can you verify again that you're not seeing it for the mentions timeline when you include this parameter? Favorites doesn't yet return entities. It's our intention to return entities wherever a tweet is returned; I'll make sure this gets some attention. Thanks! Taylor On Thu, Jun 24, 2010 at 12:00 AM, Manton Reece man...@gmail.com wrote: I just switched over to include_entities, and I'm also not seeing the entities come back for favorites or mentions. Works great for home_timeline and retweets. I can fall back on my own parsing when entities are missing, but for consistently I definitely prefer letting Twitter do this work. Is it a known issue that it's missing for favorites and mentions, and if so any idea when it can be rolled out across the board? Thanks! On Jun 13, 6:17 am, Georgios kapero...@gmail.com wrote: Hi I have a website that focuses on Twitter favorites (http://favorious.com ) and I have tried to implement the new Link Wrapping guidelines using entities. However ?include_entities=true is not working (I tried getting a @raffi tweet that I have favorited). The documentation (http://dev.twitter.com/doc/get/favorites) also doesn't mention anything about entities for this. Does Twitter plan to roll out link wrapping info for Favorites? If not, then I cannot implement the new Link Wrapping according to Twitter's TOS. Thanks Georgioshttp://favorious.com- Only the best of Twitter, based on favorites.
Re: [twitter-dev] Re: Streaming API OAuth explanation?
Hi Wil, I can help you with the OAuth component of this. Can you share your signature base string for the request? Here's an example of a few of the steps of a functioning OAuth request against this endpoint: POST body source=softwarenamedelimited=1follow=156934710 Signature Base String POSThttp%3A%2F%2Fstream.twitter.com %2F1%2Fstatuses%2Ffilter.jsondelimited%3D1%26follow%3D156934710%26oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DVBOxfmeKM2mgMeou28zK78MKlfrkvc7Wo4Hx8BAkf0%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1277394877%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26source%3Dsoftwarename Authorization Header OAuth oauth_nonce=VBOxfmeKM2mgMeou28zK78MKlfrkvc7Wo4Hx8BAkf0, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877, oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ, oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw, oauth_signature=cLdFEiEy16d2HdWnb5dPBtuxvko%3D, oauth_version=1.0 How do your values for signature base string differ, if at all? (other than the tokens, timestamp, and nonce being different). Thanks, Taylor On Thu, Jun 24, 2010 at 8:17 AM, John Kalucki j...@twitter.com wrote: Aside from the oAuth issue, which others can address, the only valid delimited value is length. -John On Thu, Jun 24, 2010 at 7:58 AM, Wil willi...@gmail.com wrote: I'm getting this response: HTTP/1.1 401 Unauthorized Content-Length: 1296 Cache-Control: must-revalidate,no-cache,no-store Content-Type: text/html; charset=iso-8859-1 Server: Jetty(6.1.17) WWW-Authenticate: Basic realm=Firehose html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 UNAUTHORIZED/title /head body h2HTTP ERROR: 401/h2 pProblem accessing /1/statuses/filter.json. Reason: preUNAUTHORIZED/pre/p hr /ismallPowered by Jetty:///small/i Here's what I POSTed(oauth tokens are filtered out): REQUEST: POST http://stream.twitter.com/1/statuses/filter.json Authorization: OAuth oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC- SHA1,oauth_signature=,oauth_version=1.0, Content-Type: application/x-www-form-urlencoded Vary: Accept-Encoding Connection: close source=softwarenamedelimited=1follow=156934710 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote: OAuthshould work fine onstream.twitter.com -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jun 22, 2010 at 10:00 AM, Wil willi...@gmail.com wrote: I'm a bit dumbfounded here... I've been trying to login tostream.twitter.com usingOAuth (particularly, I've been trying to access http://stream.twitter.com/1/statuses/filter.json?follow=). I used the access keys obtained fromhttps:// api.twitter.com/oauth/access_token however, I've been getting 401 errors. I've tried basic authentication and it works fine. Does that mean thatstream:statuses/filter is still can only accept basic authentication? Regards, Wil On May 25, 5:51 am, John Kalucki j...@twitter.com wrote: We haven't announced our plans for streaming andoAuth, beyond stating that User Streams will only be onoAuth. On Mon, May 24, 2010 at 1:57 PM, 140dev 140...@gmail.com wrote: Does this mean that the streaming API will also make the switch from basic authentication toOAuthat the end of June? On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com wrote: OAuthis now enabled onstream.twitter.com. I'll also send a note out to the announce list ---Mark http://twitter.com/mccv On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin aran...@gmail.com wrote: Hi, Is there an ETA for enablingoauthonstream.twitter.com? Thanks, Aaron On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote: OAuthis not enabled onstream.twitter.com. You can try on chirpstream.twitter.com. On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com wrote: I am writing my own c++ basedOAuthlibrary. I know there is liboauth but I like to do things myself to learn. Anyhow I am trying to accesshttp:// stream.twitter.com/1/statuses/sample.xml and I keep getting 401. I have verified pretty much every parameter, and used the tool on http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... to verify my signature is correct. I used twurl to obtain the user access tokens to my account. After doing some reading I'm no longer convinced that thestreaming server even supportsoauth. can you fill me in on the current status ofstream.twitter.com and oauth? thanks! Lucas On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote: Thanks Taylor for the very detailed and helpful response!
[twitter-dev] Delete List Member + OAuth Authorization
Hi all, I've stumbled upon a strange issue with the /:user/:list_id/members method. If we use DELETE as the HTTP method, we get back Could not authenticate you. when we try to delete a member. If we just switch to POST and use _method=DELETE, the call succeeds with the _exact_ same secret tokens etc. So, I'm not quite sure why we're getting an authentication error with DELETE and no error when we use POST (there's no difference in the auth info in the two calls). Has anyone else observed this? M
Re: [twitter-dev] Delete List Member + OAuth Authorization
Hi Milen, When you're using a DELETE HTTP method, are you sending the id=12345 parameter on the query string or in a POST body? It should be in the query string. There's some contention in the universe on whether HTTP DELETEs should accept a body. In our case, like many HTTP servers, we do not. Here's an example of a successfully signed DELETE request: URL http://api.twitter.com/1/episod/virtual/members.xml?id=12345 POST body n/a Signature Base String DELETEhttp%3A%2F%2Fapi.twitter.com %2F1%2Fepisod%2Fvirtual%2Fmembers.xmlid%3D12345%26oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DLnME61XWvwjp3ORhhLd5MMEb9EDO1DeYIsb7HfhoeE4%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1277394877%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0 Authorization Header OAuth oauth_nonce=LnME61XWvwjp3ORhhLd5MMEb9EDO1DeYIsb7HfhoeE4, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877, oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ, oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw, oauth_signature=UKwl3lVQygmKAMsIffFCWlLQaeg%3D, oauth_version=1.0 On Thu, Jun 24, 2010 at 9:02 AM, Milen mi...@thecosmicmachine.com wrote: Hi all, I've stumbled upon a strange issue with the /:user/:list_id/members method. If we use DELETE as the HTTP method, we get back Could not authenticate you. when we try to delete a member. If we just switch to POST and use _method=DELETE, the call succeeds with the _exact_ same secret tokens etc. So, I'm not quite sure why we're getting an authentication error with DELETE and no error when we use POST (there's no difference in the auth info in the two calls). Has anyone else observed this? M
[twitter-dev] How to get location information?
Hi, I am currently working on a project and I require to get the following information by using Javascript: 1. Location information from profile of user. 2. Geolocation provided when tweet is sent from mobile 3. Location information when it is provided by using the IP address when tweet is sent from browser. It would be great if anyone can help me in this matter.. Thanks, VArun Bedi.
[twitter-dev] Re: Geo-caching Without Lat/Long
Great; thanks for the clarification Matt. But I'm still having trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single letter.
So a string like wondering what's happening … will be treated as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert them
into their HTML entity representation to ensure consistency between
clients and reliable storage in the databases. This means, when you
query the API, you may notice the Tweet has more than 140 characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including OAuth
authentication and contextual links to the full Twitter API, and no
login required in order to save API calls.
You can see the same lat/long query here:
http://app.apigee.com/console/5ffbfabd-04c0-4802-a71d-542c23a1ec0e/re...
Hope this is helpful - we are seeking feedback on the tool if you have
any.
Thanks,
Sam
On Jun 11, 9:48 am, Bryan bryan.p...@gmail.com wrote:
Hey Abraham. The above example is dated. My point is appending
max_result=1 onto any verified result results in a 404:
http://hurl.it/hurls/08a6b684b494cab6138754d7b7470d9895968d59/88bbdc8...
is okay, but with max_results=1:
http://hurl.it/hurls/df8773b96e453cfd5426123c3ba4354fc2d96769/6d952ea...
returns a 404
Thanks for the link; that's a very useful tool!
On Jun 11, 11:40 am, Abraham Williams 4bra...@gmail.com wrote:
The lat/long you are passing to the API are in the Yellow Sea so
Twitter is
404ing as it does not have any places near there.
http://hurl.it/hurls/db27e3e9bce56f7f9a8209b935af6a25d5fa5677/2775b26...
Abraham
-
Abraham Williams | Hacker Advocate |http://abrah.am
@abraham |http://projects.abrah.am|http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Fri, Jun 11, 2010 at 07:28, Bryan bryan.p...@gmail.com wrote:
Matt--
Okay thanks for the reply. I'm building a news aggregator so the goal
was to enter the location manually. Still, I'm having trouble with the
geo-coding method. I'm using Abraham's php library and I do the
following:
$location = $connection-get('geo/reverse_geocode',
array('lat' =
'37.75' , 'long' = '122.68'));
echo $connection-http_code;
Which returns 404. $location-id is empty. Any thoughts as to what I'm
doing wrong?
On Jun 11, 9:21 am, Matt Harris thematthar...@twitter.com wrote:
Hey Bryan,
Status updates only accept lat/long or place_id. There isn't a way
of
providing plain text locations for these fields. If you wish to
display a
textual representation of where someone is on your app you would
need to
carry out a reverse geocode first.
I don't know the method you are using to obtain the location but
generally
we see developers use the lat/long returned by the browser or
device.
One thing that might be useful to know is that we perform a reverse
lookup
on the lat/long when we display the tweet, converting it to some
textual
description like SoMa, San Francisco, or from here as
appropriate.
Hope that answers your question,
Matt
On Fri, Jun 11, 2010 at 6:41 AM, Bryan bryan.p...@gmail.com wrote:
Hey everyone, is there a way to geo-tweet with the API without
knowing
the Lat/Long? In other words, can I say San Francisco, CA or
search
for valid place_id's with this name? I'm trying to make my user
interface as user-friendly as possible, and asking for lat/long
for my
userbase won't work. I also want to rely on as few as API's as
possible, so I'd prefer not to run my name through Google's Map
API
and then through the reverse geocode API on twitters. Thanks.
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] Re: Geo-caching Without Lat/Long
Hey Bryan,
Can you share the code you are using to send the Tweet, and if possible the
post body sent by your code.
Thanks,
Matt
On Thu, Jun 24, 2010 at 10:06 AM, Bryan bryan.p...@gmail.com wrote:
Great; thanks for the clarification Matt. But I'm still having trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single letter.
So a string like wondering what's happening … will be treated as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert them
into their HTML entity representation to ensure consistency between
clients and reliable storage in the databases. This means, when you
query the API, you may notice the Tweet has more than 140 characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including OAuth
authentication and contextual links to the full Twitter API, and no
login required in order to save API calls.
You can see the same lat/long query here:
http://app.apigee.com/console/5ffbfabd-04c0-4802-a71d-542c23a1ec0e/re.
..
Hope this is helpful - we are seeking feedback on the tool if you have
any.
Thanks,
Sam
On Jun 11, 9:48 am, Bryan bryan.p...@gmail.com wrote:
Hey Abraham. The above example is dated. My point is appending
max_result=1 onto any verified result results in a 404:
http://hurl.it/hurls/08a6b684b494cab6138754d7b7470d9895968d59/88bbdc8...
is okay, but with max_results=1:
http://hurl.it/hurls/df8773b96e453cfd5426123c3ba4354fc2d96769/6d952ea...
returns a 404
Thanks for the link; that's a very useful tool!
On Jun 11, 11:40 am, Abraham Williams 4bra...@gmail.com wrote:
The lat/long you are passing to the API are in the Yellow Sea so
Twitter is
404ing as it does not have any places near there.
http://hurl.it/hurls/db27e3e9bce56f7f9a8209b935af6a25d5fa5677/2775b26...
Abraham
-
Abraham Williams | Hacker Advocate |http://abrah.am
@abraham |http://projects.abrah.am|http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Fri, Jun 11, 2010 at 07:28, Bryan bryan.p...@gmail.com wrote:
Matt--
Okay thanks for the reply. I'm building a news aggregator so the
goal
was to enter the location manually. Still, I'm having trouble
with the
geo-coding method. I'm using Abraham's php library and I do the
following:
$location = $connection-get('geo/reverse_geocode',
array('lat' =
'37.75' , 'long' = '122.68'));
echo $connection-http_code;
Which returns 404. $location-id is empty. Any thoughts as to
what I'm
doing wrong?
On Jun 11, 9:21 am, Matt Harris thematthar...@twitter.com
wrote:
Hey Bryan,
Status updates only accept lat/long or place_id. There isn't a
way of
providing plain text locations for these fields. If you wish to
display a
textual representation of where someone is on your app you
would need to
carry out a reverse geocode first.
I don't know the method you are using to obtain the location
but
generally
we see developers use the lat/long returned by the browser or
device.
One thing that might be useful to know is that we perform a
reverse
lookup
on the lat/long when we display the tweet, converting it to
some textual
description like SoMa, San Francisco, or from here as
appropriate.
Hope that answers your question,
Matt
On Fri, Jun 11, 2010 at 6:41 AM, Bryan bryan.p...@gmail.com
wrote:
Hey everyone, is there a way to geo-tweet with the API
without knowing
the Lat/Long? In other words, can I say San Francisco, CA
or search
for valid place_id's with this name? I'm trying to make my
user
interface as user-friendly as possible, and asking for
lat/long for my
userbase won't work. I also want to rely on as few as API's
as
possible, so I'd prefer not to run my name through Google's
Map API
[twitter-dev] Re: Geo-caching Without Lat/Long
Certainly:
?php
require_once('twitteroauth.php');
$message = This is an @test … ; // utf(ellipsis)
//$message = This is an @test ... ; // ascii(three periods)
echo $message.br /;
$message = strlen($message) 140 ? substr($message,0,140) : $message;
$connection = new TwitterOAuth(X, X, X, X);
$status = $connection-post('statuses/update', array('status' =
$message));
echo $connection-http_code == 200 ? SUCCESS : FAIL;
?
As you can see, I'm using Abraham's oauth library and my sensitive
data has been sanitized. Thanks again.
On Jun 24, 12:19 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Bryan,
Can you share the code you are using to send the Tweet, and if possible the
post body sent by your code.
Thanks,
Matt
On Thu, Jun 24, 2010 at 10:06 AM, Bryan bryan.p...@gmail.com wrote:
Great; thanks for the clarification Matt. But I'm still having trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single letter.
So a string like wondering what's happening … will be treated as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert them
into their HTML entity representation to ensure consistency between
clients and reliable storage in the databases. This means, when you
query the API, you may notice the Tweet has more than 140 characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including OAuth
authentication and contextual links to the full Twitter API, and no
login required in order to save API calls.
You can see the same lat/long query here:
http://app.apigee.com/console/5ffbfabd-04c0-4802-a71d-542c23a1ec0e/re.
..
Hope this is helpful - we are seeking feedback on the tool if you have
any.
Thanks,
Sam
On Jun 11, 9:48 am, Bryan bryan.p...@gmail.com wrote:
Hey Abraham. The above example is dated. My point is appending
max_result=1 onto any verified result results in a 404:
http://hurl.it/hurls/08a6b684b494cab6138754d7b7470d9895968d59/88bbdc8...
is okay, but with max_results=1:
http://hurl.it/hurls/df8773b96e453cfd5426123c3ba4354fc2d96769/6d952ea...
returns a 404
Thanks for the link; that's a very useful tool!
On Jun 11, 11:40 am, Abraham Williams 4bra...@gmail.com wrote:
The lat/long you are passing to the API are in the Yellow Sea so
Twitter is
404ing as it does not have any places near there.
http://hurl.it/hurls/db27e3e9bce56f7f9a8209b935af6a25d5fa5677/2775b26...
Abraham
-
Abraham Williams | Hacker Advocate |http://abrah.am
@abraham |http://projects.abrah.am|http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Fri, Jun 11, 2010 at 07:28, Bryan bryan.p...@gmail.com wrote:
Matt--
Okay thanks for the reply. I'm building a news aggregator so the
goal
was to enter the location manually. Still, I'm having trouble
with the
geo-coding method. I'm using Abraham's php library and I do the
following:
$location = $connection-get('geo/reverse_geocode',
array('lat' =
'37.75' , 'long' = '122.68'));
echo $connection-http_code;
Which returns 404. $location-id is empty. Any thoughts as to
what I'm
doing wrong?
On Jun 11, 9:21 am, Matt Harris thematthar...@twitter.com
wrote:
Hey Bryan,
Status updates only accept lat/long or place_id. There isn't a
way of
providing plain text locations for these fields. If you wish to
display a
textual representation of where someone is on your app you
would need to
carry out a reverse geocode first.
I don't know the method you are using to obtain the location
but
generally
we see developers use the lat/long returned by the browser or
device.
One thing that might be useful to know is that we perform a
reverse
lookup
on the lat/long when we display the tweet, converting it to
some textual
description like
Re: [twitter-dev] Re: Geo-caching Without Lat/Long
Hey Brian,
I don't know enough about the internals of Abraham's library to know how it
handles UTF-8 characters when generating POST bodies or signature base
strings, but here's an example of successfully tweeting with the UTF-8
ellipsis:
I'm pretty surprised at how the status is encoded in the base string in this
example (kind of cargo culting it), but there may also be other alternate
and valid ways of specifying it. Definitely not intuitive. Here's the
published status: http://twitter.com/oauth_dancer/status/16952668541
URL
http://api.twitter.com/1/statuses/update.xml
POST body
status=Unicode+ellipsis+are+fun:+…
Signature Base String
POSThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.xmloauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3D965MjJOs4kef7MBA8QggxIJHHzyRbMlnQ3WTB7VNV0%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1277405988%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3DUnicode%2520ellipsis%2520are%2520fun%253A%2520%25E2%2580%25A6
Authorization Header
OAuth oauth_nonce=LnME61XWvwjp3ORhhLd5MMEb9EDO1DeYIsb7HfhoeE4,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=UKwl3lVQygmKAMsIffFCWlLQaeg%3D, oauth_version=1.0
Which returns a XML status representation with the ellipsis:
textUnicode ellipsis are fun: #8230;/text
On Thu, Jun 24, 2010 at 11:48 AM, Bryan bryan.p...@gmail.com wrote:
Certainly:
?php
require_once('twitteroauth.php');
$message = This is an @test … ; // utf(ellipsis)
//$message = This is an @test ... ; // ascii(three periods)
echo $message.br /;
$message = strlen($message) 140 ? substr($message,0,140) : $message;
$connection = new TwitterOAuth(X, X, X, X);
$status = $connection-post('statuses/update', array('status' =
$message));
echo $connection-http_code == 200 ? SUCCESS : FAIL;
?
As you can see, I'm using Abraham's oauth library and my sensitive
data has been sanitized. Thanks again.
On Jun 24, 12:19 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Bryan,
Can you share the code you are using to send the Tweet, and if possible
the
post body sent by your code.
Thanks,
Matt
On Thu, Jun 24, 2010 at 10:06 AM, Bryan bryan.p...@gmail.com wrote:
Great; thanks for the clarification Matt. But I'm still having trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single letter.
So a string like wondering what's happening … will be treated as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert them
into their HTML entity representation to ensure consistency between
clients and reliable storage in the databases. This means, when you
query the API, you may notice the Tweet has more than 140 characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including
OAuth
authentication and contextual links to the full Twitter API, and no
login required in order to save API calls.
You can see the same lat/long query here:
http://app.apigee.com/console/5ffbfabd-04c0-4802-a71d-542c23a1ec0e/re.
..
Hope this is helpful - we are seeking feedback on the tool if you
have
any.
Thanks,
Sam
On Jun 11, 9:48 am, Bryan bryan.p...@gmail.com wrote:
Hey Abraham. The above example is dated. My point is appending
max_result=1 onto any verified result results in a 404:
http://hurl.it/hurls/08a6b684b494cab6138754d7b7470d9895968d59/88bbdc8.
..
is okay, but with max_results=1:
http://hurl.it/hurls/df8773b96e453cfd5426123c3ba4354fc2d96769/6d952ea.
..
returns a 404
Thanks for the link; that's a very useful tool!
On Jun 11, 11:40 am, Abraham Williams 4bra...@gmail.com wrote:
The lat/long you are passing to the API are in the Yellow Sea
so
Twitter is
404ing as it does not have any places near there.
[twitter-dev] Re: Link Wrapping and Favorites
Thanks Taylor! You're right -- mentions are working fine, it was a bug on my side. Glad to hear you're on top of getting entities into favorites too. And the search API is another one to cover. On Jun 24, 10:36 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Manton, I see the entities coming through when I request my mentions timeline.. http://api.twitter.com/1/statuses/mentions.xml?include_entities=true Can you verify again that you're not seeing it for the mentions timeline when you include this parameter? Favorites doesn't yet return entities. It's our intention to return entities wherever a tweet is returned; I'll make sure this gets some attention. Thanks! Taylor
Re: [twitter-dev] Re: Link Wrapping and Favorites
The Search API is a much bigger fish to fry :) Rest assured, we're working on it. On Thu, Jun 24, 2010 at 12:10 PM, Manton Reece man...@gmail.com wrote: Thanks Taylor! You're right -- mentions are working fine, it was a bug on my side. Glad to hear you're on top of getting entities into favorites too. And the search API is another one to cover. On Jun 24, 10:36 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Manton, I see the entities coming through when I request my mentions timeline.. http://api.twitter.com/1/statuses/mentions.xml?include_entities=true Can you verify again that you're not seeing it for the mentions timeline when you include this parameter? Favorites doesn't yet return entities. It's our intention to return entities wherever a tweet is returned; I'll make sure this gets some attention. Thanks! Taylor
[twitter-dev] Re: Twitter Places Follow Up
Currently we call the exact same endpoint to get the Tweets from a given place, but we pass the latitude and longitude, rather than the Place ID. The Latitude/Longitude method forces a 1 km radius around the endpoint. So, when we get the tweets via the Place ID method at the same endpoint - will it only show tweets from the actual place or will it show us Tweets from the place and the surroinding 1km radius? On Jun 23, 11:59 am, David Helder da...@twitter.com wrote: Sure, do this: 1) Find the place ID of the Staples Center:http://api.twitter.com/1/geo/search.json?query=Staples%20Centerlat=3... = The place ID is 7893eab4ca4c1efb (second result) 2) Get all tweets from that ID:http://search.twitter.com/search.json?q=place:7893eab4ca4c1efb If you only have 100 places, you could probably do 100 searches and find the best result by hand when there are multiple results. David On Tue, Jun 22, 2010 at 9:35 AM, ELB ebrit...@gmail.com wrote: The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update orhttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Geo-caching Without Lat/Long
Interesting; thank you. I found the solution using your information.
Basically, PHP acts funny with raw utf characters, and in reality I
needed to pass three hex characters like so:
$message =
sprintf(1234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123\xE2\x80\xA6);
//
utf(ellipsis)
Note the three hex characters on the end, and the 139 numbers
proceeding it. This returned a 200 and actually tweeted.
Thanks again everyone.
On Jun 24, 2:05 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hey Brian,
I don't know enough about the internals of Abraham's library to know how it
handles UTF-8 characters when generating POST bodies or signature base
strings, but here's an example of successfully tweeting with the UTF-8
ellipsis:
I'm pretty surprised at how the status is encoded in the base string in this
example (kind of cargo culting it), but there may also be other alternate
and valid ways of specifying it. Definitely not intuitive. Here's the
published status:http://twitter.com/oauth_dancer/status/16952668541
URLhttp://api.twitter.com/1/statuses/update.xml
POST body
status=Unicode+ellipsis+are+fun:+…
Signature Base String
POSThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.xmloauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26
oauth_nonce%3D965MjJOs4kef7MBA8QggxIJHHzyRbMlnQ3WTB7VNV0%26oauth_signature_
method%3DHMAC-SHA1%26oauth_timestamp%3D1277405988%26oauth_token%3D119476949
-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3D
Unicode%2520ellipsis%2520are%2520fun%253A%2520%25E2%2580%25A6
Authorization Header
OAuth oauth_nonce=LnME61XWvwjp3ORhhLd5MMEb9EDO1DeYIsb7HfhoeE4,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=UKwl3lVQygmKAMsIffFCWlLQaeg%3D, oauth_version=1.0
Which returns a XML status representation with the ellipsis:
textUnicode ellipsis are fun: #8230;/text
On Thu, Jun 24, 2010 at 11:48 AM, Bryan bryan.p...@gmail.com wrote:
Certainly:
?php
require_once('twitteroauth.php');
$message = This is an @test … ; // utf(ellipsis)
//$message = This is an @test ... ; // ascii(three periods)
echo $message.br /;
$message = strlen($message) 140 ? substr($message,0,140) : $message;
$connection = new TwitterOAuth(X, X, X, X);
$status = $connection-post('statuses/update', array('status' =
$message));
echo $connection-http_code == 200 ? SUCCESS : FAIL;
?
As you can see, I'm using Abraham's oauth library and my sensitive
data has been sanitized. Thanks again.
On Jun 24, 12:19 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Bryan,
Can you share the code you are using to send the Tweet, and if possible
the
post body sent by your code.
Thanks,
Matt
On Thu, Jun 24, 2010 at 10:06 AM, Bryan bryan.p...@gmail.com wrote:
Great; thanks for the clarification Matt. But I'm still having trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single letter.
So a string like wondering what's happening … will be treated as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert them
into their HTML entity representation to ensure consistency between
clients and reliable storage in the databases. This means, when you
query the API, you may notice the Tweet has more than 140 characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including
OAuth
authentication and contextual links to the full Twitter API, and no
login required in order to save API calls.
You can see the same lat/long query here:
http://app.apigee.com/console/5ffbfabd-04c0-4802-a71d-542c23a1ec0e/re.
..
Hope this is helpful - we are seeking feedback on the tool if you
have
any.
Thanks,
Sam
On Jun 11, 9:48 am, Bryan
[twitter-dev] Incorrect Signature
Hi everyone! I'm working on a Twitter application that uses Twitter API through Twitter4j and authenticates different accounts using OAuth. We are getting an incorrect signature error when trying to perform any post to twitter api (i.e. sending an update, following, etc). I'm using Twitter4j version 2.0.10. Although we are not using the latest version of Twitter4j, my code has been working pretty well for months until last week when I started to get these errors. Any help from you would be much appreciated. Thanks! Joel P.S.: Here goes the exception im getting Caused by: twitter4j.TwitterException: 401:Authentication credentials were missing or incorrect. ?xml version=1.0 encoding=UTF-8? hash request/statuses/update.xml/request errorIncorrect signature/error /hash at twitter4j.http.HttpClient.httpRequest(HttpClient.java:477) at twitter4j.http.HttpClient.post(HttpClient.java:401) at twitter4j.Twitter.updateStatus(Twitter.java:1232)
Re: [twitter-dev] Incorrect Signature
Hi Hoel, Signature validation errors occur for a variety of reasons. We have a few error conditions on the API right now where when under heavy load we might spuriously throw an invalid signature error, but these cases should be rare. To better assist you in your issues, you'll need to dig a bit deeper into the library you are using to extract the OAuth signature base string and your HTTP authorization headers. Also, your POST body on these update requests would be very useful as well as the complete executed URIs you're using. You mentioned you only recently started running into these issues. Does the failure occur for ALL write operations or only sporadically? Thanks, Taylor On Thu, Jun 24, 2010 at 12:59 PM, jc joelcuet...@gmail.com wrote: Hi everyone! I'm working on a Twitter application that uses Twitter API through Twitter4j and authenticates different accounts using OAuth. We are getting an incorrect signature error when trying to perform any post to twitter api (i.e. sending an update, following, etc). I'm using Twitter4j version 2.0.10. Although we are not using the latest version of Twitter4j, my code has been working pretty well for months until last week when I started to get these errors. Any help from you would be much appreciated. Thanks! Joel P.S.: Here goes the exception im getting Caused by: twitter4j.TwitterException: 401:Authentication credentials were missing or incorrect. ?xml version=1.0 encoding=UTF-8? hash request/statuses/update.xml/request errorIncorrect signature/error /hash at twitter4j.http.HttpClient.httpRequest(HttpClient.java:477) at twitter4j.http.HttpClient.post(HttpClient.java:401) at twitter4j.Twitter.updateStatus(Twitter.java:1232)
[twitter-dev] URL-escaping an actual percent sign
Hi all, I'm having a weird experience. I encode my twitter string to send over to twitter. The status string contains something like 50 % off http://bit.ly/bbjQv0; which ends up escaped in the url I'm sending to twitter as: http://twitter.com/home/?status=50%20%25%20off%20http:// bit.ly/bbjQv0. When somebody clicks on the Twitter button, that is submitted to Twitter. However, it appears in the (Firefox) location bar, having become http://twitter.com/home/?status=50%20%%20off%20http://bit.ly/ bbjQv0 - notice the %25 has become just plain % again - and the Twitter page fails to load. If I paste the correctly escaped string into the browser location bar, it goes through fine, the Twitter page loads, with 50 % off http://bit.ly/bbjQv0; in the status field. Anybody experienced this, and/or have a fix? Thanks! Barclay
[twitter-dev] Erroneous return from location-based search
It seems that every time someone checks into the Blue Bottle Coffee location on foursquare, they appear in our location search for St. Louis, MO. This is odd because the people tweeting are usually from Brooklyn or NYC, and the Blue Bottle is in Brooklyn... thus they really should not appear in our searches. Sample tweet: http://twitter.com/naterkane/status/16100616342 Sample tweep: http://twitter.com/naterkane/ [clearly in Brooklyn, NY] Sample search query: http://search.twitter.com/search.atom?rpp=100lang=engeocode=38.627522%2C-90.19841%2C30misince_id= (not sure what the since_id was at the time it arrived... sorry) Foursquare venue shows correct GPS in embedded map page http://foursquare.com/venue/1283426
Re: [twitter-dev] 404 Problem 3 day
Can you share the URLs you are using when connecting? All REST API URLs should have both an api subdomain and a 1 for the version number: For example, you should be using: http://api.twitter.com/1/statuses/user_timeline.xml and NOT http://twitter.com/statuses/user_timeline.xml Taylor On Wed, Jun 23, 2010 at 11:26 PM, iLyas ilyas.osmano...@gmail.com wrote: i cant connect twitter api 3 days . I get follower and following count but not get timeline and other action. What is changing ?
Re: [twitter-dev] Failed to validate oauth signature and token with xauth
Hi there,
Are you still having this issue?
In the past when I've seen other developers having issues accomplishing this
in Javascript, it's come down to an issue in the library used for HMAC-SHA1
and Base64 encoding. While it works in most conditions, there are apparently
some edge cases where it does the wrong thing. I generally don't advocate
using Javascript and OAuth together for a variety of reasons. Have you tried
tracing the request to see exactly the HTTP request being sent to the
server?
Are you writing a browser extension or WebOS app? If the former, how are you
keeping your consumer secret at least somewhat secured?
Have you tried other requests using an access token obtained through other
means?
Taylor
On Thu, Jun 17, 2010 at 11:25 AM, ntortarolo ntortar...@gmail.com wrote:
Hi, i have problem requesting an access_token, i think my source is
right, i dont know where is the problem, i have maken some test with
base_string, oauth_consumer_key and oauth_consumer_secret shown on
http://dev.twitter.com/pages/xauth and i get the same oauth_signature
shown there so i think problem is not there when i use the real
base_string, my oauth_consumer_key and oauth_consumer_secret.
My source is this, i hope someone can help me (to preserve my secret
and key i will put the same as the ones used on
http://dev.twitter.com/pages/xauth)
xauth: function xauth()
{
var username = encodeURIComponent(),
password = encodeURIComponent(),
url= https://api.twitter.com/oauth/access_token;,
key = sGNxxnqgZRHUt6NunK3uw,
timestamp = (new Date()).getTime(),
nonce = Math.random();
var access_token = oauth_consumer_key= + key +
oauth_nonce= + nonce +
oauth_signature_method=HMAC-SHA1 +
oauth_timestamp= + timestamp +
oauth_version=1.0 +
x_auth_mode=client_auth +
x_auth_password= + password +
x_auth_username= + username;
var base_string = POST + encodeURIComponent(url) + +
encodeURIComponent(access_token);
var oauth_signature =
b64_hmac_sha1(5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk,
base_string);
oauth_signature = encodeURIComponent(oauth_signature+=);
var auth_header = 'OAuth oauth_nonce=' + nonce + '' +
', oauth_signature_method=HMAC-SHA1' +
', oauth_timestamp=' + timestamp + '' +
', oauth_consumer_key=' + key + '' +
', oauth_signature=' + oauth_signature + '' +
', oauth_version=1.0';
$.ajax({
url:url,
method: POST,
data: {
x_auth_username: username,
x_auth_password: password,
x_auth_mode: client_auth
},
beforeSend: function(xhr){
xhr.setRequestHeader(Authorization, auth_header);
},
success: function(data){
alert(data);
},
error: function(xhr){
alert(xhr.responseText);
}
}) ;
* What language or library are you using? What versions?
i'm using it on javascript
* What oauth application is this for?
http://twitter.com/apps/edit/181924
Re: [twitter-dev] Access Token
Hi Manjunath, You'll want to read about implementing OAuth in your application at http://dev.twitter.com/auth -- there are some convenient features we offer to acquire an access token for your own account and own application, but you'll still need to implement the bulk of OAuth. Taylor On Wed, Jun 23, 2010 at 11:16 PM, manjunath reddy manjunathredd...@gmail.com wrote: HI I have an requirement of reading all the tweets that has specifed word and replying to that tweeet. I am able to query all the tweets while replying to the tweet i am getting error.Couldnt autheticate the user. Please let me know how can i get the access token for the user. Please help me in resolving this issue. Regards Manjunatha M.N
Re: [twitter-dev] Re: Twitter Places Follow Up
Only tweets from the place, or a place within the place. David On Thu, Jun 24, 2010 at 12:44 PM, ELB ebrit...@gmail.com wrote: Currently we call the exact same endpoint to get the Tweets from a given place, but we pass the latitude and longitude, rather than the Place ID. The Latitude/Longitude method forces a 1 km radius around the endpoint. So, when we get the tweets via the Place ID method at the same endpoint - will it only show tweets from the actual place or will it show us Tweets from the place and the surroinding 1km radius? On Jun 23, 11:59 am, David Helder da...@twitter.com wrote: Sure, do this: 1) Find the place ID of the Staples Center:http://api.twitter.com/1/geo/search.json?query=Staples%20Centerlat=3... = The place ID is 7893eab4ca4c1efb (second result) 2) Get all tweets from that ID:http://search.twitter.com/search.json?q=place:7893eab4ca4c1efb If you only have 100 places, you could probably do 100 searches and find the best result by hand when there are multiple results. David On Tue, Jun 22, 2010 at 9:35 AM, ELB ebrit...@gmail.com wrote: The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update orhttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: Geo-caching Without Lat/Long
Hey Bryan,
Thanks for sharing the solution with the list. Glad it's working for you
now.
Matt
On Thu, Jun 24, 2010 at 12:52 PM, Bryan bryan.p...@gmail.com wrote:
Interesting; thank you. I found the solution using your information.
Basically, PHP acts funny with raw utf characters, and in reality I
needed to pass three hex characters like so:
$message =
sprintf(1234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123\xE2\x80\xA6);
//
utf(ellipsis)
Note the three hex characters on the end, and the 139 numbers
proceeding it. This returned a 200 and actually tweeted.
Thanks again everyone.
On Jun 24, 2:05 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hey Brian,
I don't know enough about the internals of Abraham's library to know how
it
handles UTF-8 characters when generating POST bodies or signature base
strings, but here's an example of successfully tweeting with the UTF-8
ellipsis:
I'm pretty surprised at how the status is encoded in the base string in
this
example (kind of cargo culting it), but there may also be other alternate
and valid ways of specifying it. Definitely not intuitive. Here's the
published status:http://twitter.com/oauth_dancer/status/16952668541
URLhttp://api.twitter.com/1/statuses/update.xml
POST body
status=Unicode+ellipsis+are+fun:+…
Signature Base String
POSThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.xmloauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26
oauth_nonce%3D965MjJOs4kef7MBA8QggxIJHHzyRbMlnQ3WTB7VNV0%26oauth_signature_
method%3DHMAC-SHA1%26oauth_timestamp%3D1277405988%26oauth_token%3D119476949
-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3D
Unicode%2520ellipsis%2520are%2520fun%253A%2520%25E2%2580%25A6
Authorization Header
OAuth oauth_nonce=LnME61XWvwjp3ORhhLd5MMEb9EDO1DeYIsb7HfhoeE4,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=UKwl3lVQygmKAMsIffFCWlLQaeg%3D, oauth_version=1.0
Which returns a XML status representation with the ellipsis:
textUnicode ellipsis are fun: #8230;/text
On Thu, Jun 24, 2010 at 11:48 AM, Bryan bryan.p...@gmail.com wrote:
Certainly:
?php
require_once('twitteroauth.php');
$message = This is an @test … ; // utf(ellipsis)
//$message = This is an @test ... ; // ascii(three periods)
echo $message.br /;
$message = strlen($message) 140 ? substr($message,0,140) : $message;
$connection = new TwitterOAuth(X, X, X, X);
$status = $connection-post('statuses/update', array('status' =
$message));
echo $connection-http_code == 200 ? SUCCESS : FAIL;
?
As you can see, I'm using Abraham's oauth library and my sensitive
data has been sanitized. Thanks again.
On Jun 24, 12:19 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Bryan,
Can you share the code you are using to send the Tweet, and if
possible
the
post body sent by your code.
Thanks,
Matt
On Thu, Jun 24, 2010 at 10:06 AM, Bryan bryan.p...@gmail.com
wrote:
Great; thanks for the clarification Matt. But I'm still having
trouble
actually tweeting UTF-8 characters. If I tweet this:
This is an @test …
without quotes where you can see an actual ellipsis (single UTF-8
character), I get a successful response code (200), but nothing is
actually tweeted. If I tweet this:
This is an @test ...
without quotes where you can see just three dots, I get a
successful
response code (200), and the tweet is actually successful.
On Jun 23, 4:14 pm, themattharris thematthar...@twitter.com
wrote:
To clarify the situation with UTF-8 characters.
Special UTF-8 characters are treated the same as the standard
alphanumeric set, in that we will count each one as a single
letter.
So a string like wondering what's happening … will be treated
as 27
characters (without the quotes).
When we receive a Tweet with UTF-8 characters in it we convert
them
into their HTML entity representation to ensure consistency
between
clients and reliable storage in the databases. This means, when
you
query the API, you may notice the Tweet has more than 140
characters
in it. This is expected and is a result of the UTF-8 conversion.
You can read more about how we count characters on the
dev.twitter
site [1].
Hope that answers your questions,
Matt
1.http://dev.twitter.com/pages/counting_characters
On Jun 11, 3:18 pm, Sam Ramji sra...@apigee.com wrote:
We've built a free tool with similar capabilities but including
OAuth
authentication and contextual links to the full Twitter API,
and no
login required in order
[twitter-dev] Re: mentions API broken?
Never solved this, the mentions still do not turn up. Will put this down to a glitch in the matrix. On Jun 22, 8:54 am, Mark Sievers mark.siev...@gmail.com wrote: Hey Taylor, Thanks for the response. Yup, still seeing the problem for that block of time/mentions, but subsequent mentions are coming through okay. Not causing me any particular distress, just thought I would raise it! I'll keep an eye out and update this thread if anything changes. Cheers M
[twitter-dev] twitter widget modifications
Hello, I want to do some modifications on my twitter widget,to be more specific I want to do some changes on widget.js code...i want no foot on the widget and also want to change the picture and the user name behaviors.I will explain:instead of the name of the user and the username texts,i want only one text,a static text(twitter),that will be rendered indepedent of the user.The same behavior I want to the picture,it will be the twitter logo that will,obviously,rendered indepedent of the user.But there is another solution that I'm thinking to do:instead of the widget design,i want only the updates of the user,the timeline,rendering on a div that is definied to my page. In this case,what is the easiest solution?If anyone can help me,giving some tip of how to do this...anyway,thanks in advance for the attention!
