[twitter-dev] No Results returned
We seem to have been getting an error with the search API whereby results aren't returned for a few minutes at a time... This happened one day last week, and again this evening.. anyone else noticing this?
[twitter-dev] Single user OAuth example with Python
The page http://dev.twitter.com/pages/oauth_single_token has single user OAuth examples for several languages. Is there an example for Python?
[twitter-dev] Re: API method: favorites/create returns This method requires a GET.
I had the same issues. The descriptions on the Twitter API Wiki (http://apiwiki.twitter.com/Twitter-REST-API-Method:-favorites %C2%A0create) and on the new Twitter DEV portal (http:// dev.twitter.com/doc/post/favorites/create) are contradicting each other. The correct one is the one on the Wiki. The one described on the DEV portal, as you said, comes back with an error message if you use POST (and asks for GET). When you use GET it comes back with a not authorized error. Cheers Georgios On May 2, 9:22 am, taketo1o24 taketo1...@gmail.com wrote: Hello, I have a question about the favorites/create method. Here:http://dev.twitter.com/doc/post/favorites/create, it says that this method support POST, but I get HTTP status: 400 with the error message: This method requires a GET. I tried accessinghttp://.../favorites/create?id=[status_id] with the POST data, but still got the same error. Then I triedhttp://.../favorites/create/[status_id].xml, then the request was normally accepted. Is this the correct way to use this method? ( ... I don't think it should be)
[twitter-dev] Retweet count for status?
Hi, I noticed that http://search.twitter.com/search?q=Lakers+OR+%23Lakers is returning a recent retweets count which is neat. I can see this in the search API, but I can't see where this would be in the normal API. I'd like to call a specific status and see the retweet count. Is there a way to do this (short of executing a search for the specific tweet)? Cheers Tim
[twitter-dev] Rate limit vs followings limit?
I'm writing a little app and I need to know how to get followers limit so I display a warning message and user won't get banned For some reason I thought Rate limit is Followings limit but discovereg yesterday it is not true http://api.twitter.com/1/account/rate_limit_status.xml What's the call I need to make to see how many Followings limit user has/I have? Thanks
[twitter-dev] Re: Can our twitter app call /oauth/revoke?
oAuth Core 1.0 Service Providers SHOULD allow Users to revoke Access Tokens. Without this end-point it's impossible for users to disconnect a twitter account. If a user links the wrong account then wishes to remove this link they their only option is a lot of navigation to twitters controls. -Ben
[twitter-dev] What determines which @replies are visible in my Friends' Timeline?
Sorry if this is a newbie question, but... When looking at my tweets (on my home screen on the web), I see that some @replies of people that I follow are visible. I thought that these show up if I follow both users. From http://twitter.zendesk.com/forums/10711/entries/14023 : People will only see replies in their home time line if they are following both the sender and recipient of the update. I've tried following two users, who do not follow me, who have been having a conversation recently via @replies. It seems to me that only the @replies that are from the *more recently followed* of the two users are showing up on my Home screen. Can anyone duplicate this? Am I missing something? Are the rules that govern what @replies show up in my friends' timeline documented somewhere? Thanks in advance, Burton
[twitter-dev] Re: How to find the frequency of communication between 2 users?
You can get up to 1600 updates for each user (3200 limit!) and compare XMLs but watch your Rate limits http://api.twitter.com/1/account/rate_limit_status.xml Other approach is to use something like TweetGreed with search for both users but there's a 100 updates limit - basically is you have 100 between you - invite and if less - don't
[twitter-dev] invalid response from
The oauth_version parameter as response from an access_key request (https://api.twitter.com/oauth/access_token) is wrongly returned; it now returns something like this: oauth_version=1.0oauth_token=130421609- lnF0m7YLuI0TRXPAWdPaLqjmlQ65Dx7aXE7N1ri0 It is probably a little thing for Twitter to fix though ;) Cheers! Mark
Re: [twitter-dev] @Anywhere and Usernames (15+ chars) question
Hi Arnaud, As you guessed, historically, there was a time when Twitter screen names were longer than 15 characters, though that's no longer the case. Taylor On Sat, May 1, 2010 at 6:26 AM, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Enjoying a free Saturday afternoon, I was playing with @Anywhere and I noticed something quite strange related to Twitter Usernames. The @Anywhere documentation says A Twitter screen name is an '@' symbol followed by 1 to 20 alphanumeric characters, including underscores The problem is… I thought a Twitter Username could not exceed 15 characters? Try to create / change your username to something longer than 15 chars: you can’t. But @Anywhere JS is still trying to add Hovercards to these strings (@15+ chars) that cannot match any Twitter User. Is it a bug? A confusion with “Real Names”? A necessity because of a previous policy (can’t remember if you could create 15+ chars Usernames in the past)? Or do you plan to allow usernames longer than 15 chars in a near future? Was just wondering :)
[twitter-dev] Re: @Anywhere and Usernames (15+ chars) question
Taylor, Are there still usernames left in the Twitter system that are longer than 15 characters? Is the historical maximum 20? On May 3, 10:29 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Arnaud, As you guessed, historically, there was a time when Twitter screen names were longer than 15 characters, though that's no longer the case. Taylor On Sat, May 1, 2010 at 6:26 AM, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Enjoying a free Saturday afternoon, I was playing with @Anywhere and I noticed something quite strange related to Twitter Usernames. The @Anywhere documentation says A Twitter screen name is an '@' symbol followed by 1 to 20 alphanumeric characters, including underscores The problem is… I thought a Twitter Username could not exceed 15 characters? Try to create / change your username to something longer than 15 chars: you can’t. But @Anywhere JS is still trying to add Hovercards to these strings (@15+ chars) that cannot match any Twitter User. Is it a bug? A confusion with “Real Names”? A necessity because of a previous policy (can’t remember if you could create 15+ chars Usernames in the past)? Or do you plan to allow usernames longer than 15 chars in a near future? Was just wondering :)
Re: [twitter-dev] Using Oauth and @anywhere together
I'm sorry I don't wanna recieve twitter-dev email any more. how can I stop this kind of email? So many email ... it's so hard... to me... :) thank you for your suffer... On Mon, May 3, 2010 at 8:41 AM, paloalto sungh...@gmail.com wrote: Using both Oauth and @anywhere in my application requires two separate login. Is there a way to link these authentication together so that only one login is required? -- 살아있는 매순간들마다 의미있는 순간의 연속으로 살아드릴 수 있길... Making the most of every opportunity... (Eph 5:16a niv )
Re: [twitter-dev] Re: @Anywhere and Usernames (15+ chars) question
I believe the historical maximum was indeed 20 -- and yes, the usernames still exist. On Mon, May 3, 2010 at 7:42 AM, Adam Green 140...@gmail.com wrote: Taylor, Are there still usernames left in the Twitter system that are longer than 15 characters? Is the historical maximum 20? On May 3, 10:29 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Arnaud, As you guessed, historically, there was a time when Twitter screen names were longer than 15 characters, though that's no longer the case. Taylor On Sat, May 1, 2010 at 6:26 AM, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Enjoying a free Saturday afternoon, I was playing with @Anywhere and I noticed something quite strange related to Twitter Usernames. The @Anywhere documentation says A Twitter screen name is an '@' symbol followed by 1 to 20 alphanumeric characters, including underscores The problem is… I thought a Twitter Username could not exceed 15 characters? Try to create / change your username to something longer than 15 chars: you can’t. But @Anywhere JS is still trying to add Hovercards to these strings (@15+ chars) that cannot match any Twitter User. Is it a bug? A confusion with “Real Names”? A necessity because of a previous policy (can’t remember if you could create 15+ chars Usernames in the past)? Or do you plan to allow usernames longer than 15 chars in a near future? Was just wondering :)
Re: [twitter-dev] Using Oauth and @anywhere together
Right now the auth tokens used in each framework and incompatible with each other. We're working on bridging the gap but don't have a timeframe for it yet. Taylor On Sun, May 2, 2010 at 4:41 PM, paloalto sungh...@gmail.com wrote: Using both Oauth and @anywhere in my application requires two separate login. Is there a way to link these authentication together so that only one login is required?
Re: [twitter-dev] Re: API method: favorites/create returns This method requires a GET.
We'll get this fixed up on the dev portal. Thanks for pointing it out. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Sun, May 2, 2010 at 6:15 PM, Georgios kapero...@gmail.com wrote: I had the same issues. The descriptions on the Twitter API Wiki (http://apiwiki.twitter.com/Twitter-REST-API-Method:-favorites %C2%A0create) and on the new Twitter DEV portal (http:// dev.twitter.com/doc/post/favorites/create) are contradicting each other. The correct one is the one on the Wiki. The one described on the DEV portal, as you said, comes back with an error message if you use POST (and asks for GET). When you use GET it comes back with a not authorized error. Cheers Georgios On May 2, 9:22 am, taketo1o24 taketo1...@gmail.com wrote: Hello, I have a question about the favorites/create method. Here:http://dev.twitter.com/doc/post/favorites/create, it says that this method support POST, but I get HTTP status: 400 with the error message: This method requires a GET. I tried accessinghttp://.../favorites/create?id=[status_id] with the POST data, but still got the same error. Then I triedhttp://.../favorites/create/[status_id].xml, then the request was normally accepted. Is this the correct way to use this method? ( ... I don't think it should be)
Re: [twitter-dev] Retweet count for status?
Hi Tim, There's currently no way to get this count without significant use of the API in most contexts. At this time, we only offer the retweet count for popular tweets results on the search.twitter.com API: http://dev.twitter.com/doc/get/search Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Sun, May 2, 2010 at 6:12 PM, Tim Bull tim.b...@binaryplex.com wrote: Hi, I noticed that http://search.twitter.com/search?q=Lakers+OR+%23Lakers is returning a recent retweets count which is neat. I can see this in the search API, but I can't see where this would be in the normal API. I'd like to call a specific status and see the retweet count. Is there a way to do this (short of executing a search for the specific tweet)? Cheers Tim
Re: [twitter-dev] Single user OAuth example with Python
I'll write one up in Python for you today. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Sun, May 2, 2010 at 2:17 PM, Moshe C. mos...@gmail.com wrote: The page http://dev.twitter.com/pages/oauth_single_token has single user OAuth examples for several languages. Is there an example for Python?
[twitter-dev] Re: Getting error 6 on geo/nearby_places
Thanks Raffi, somehow my test coordinates were odd, I admit.
When will places all over Germany be available? Neither my home town
nor the next big city is listed, while a small village I had been
visiting recently is listed.
I also hate staring at Unable to locate you. Try again beneath the
tweetbox on twitter.com... while Google Maps finds me perfectly.
mynetx
On May 3, 6:46 am, Raffi Krikorian ra...@twitter.com wrote:
looking at the coordinate you are passing in (37.996163, -127.441406) --
that's in the pacific ocean. i don't think our rockdove database has
anything for that location
On Sun, May 2, 2010 at 12:58 PM, mynetx myne...@googlemail.com wrote:
I am getting this:
{errors:[{code:6,message:No data available for the given
coordinate}],query:{type:nearby_places,url:http://
api.twitter.com/1/geo/nearby_places.json?
query=lat=37.996163accuracy=0autocomplete=falselong=-127.441406granula
rity=neighborhood,params:
{coordinates:{coordinates:
[-127.441406,37.996163],type:Point},query:,accuracy:
0,autocomplete:false,granularity:neighborhood}}}
when trying to locate ANY pair of latitude and longitude, as well as
with locating my own IP address.
What am I doing wrong?
--
Raffi Krikorian
Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Retweet count for status?
If you have a specific status and want to get retweet information about it you can call: http://dev.twitter.com/doc/get/statuses/retweets Abraham On Sun, May 2, 2010 at 18:12, Tim Bull tim.b...@binaryplex.com wrote: Hi, I noticed that http://search.twitter.com/search?q=Lakers+OR+%23Lakers is returning a recent retweets count which is neat. I can see this in the search API, but I can't see where this would be in the normal API. I'd like to call a specific status and see the retweet count. Is there a way to do this (short of executing a search for the specific tweet)? Cheers Tim -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Upcoming changes to userstream preview
Userstream previewers:
Coming soon there will be a number of changes that may impact applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate statuses and DMs. We'll be
wrapping direct messages in a higher level direct_message object,
e.g.
{direct_message=
{created_at=Wed Apr 28 14:56:31 + 2010,
sender_screen_name=user1,
sender=
{profile_background_tile=false,
name=User1,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/user1_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
[twitter-dev] Re: Upcoming changes to userstream preview
1. What's the approximate date for the oAuth rollout? 2. Will I be able to connect to both userstreams and sample from the same Twitter account at the same time? I don't see a need to connect to 'filter', since most of the interesting 'filter' functionality is available in 'userstreams'. Right now, I have multiple test accounts - one for sample and one for each variant of filter that I use. I'd like to ditch those. I'm sure Twitter would like to see as few test accounts as possible cluttering up the space as well.
[twitter-dev] Re: Tons of Connection Refused
John, Sorry, I should have update this thread. It was the ThePlanet.com outage that affected me. On May 3, 2:21 am, John Kalucki j...@twitter.com wrote: Did this happen to start at 10pm PST / 05:00 UTC? On Sun, May 2, 2010 at 10:16 PM, Dewald Pretorius dpr...@gmail.com wrote: I'm getting tons of connection refused errors. What's going on? The API status is till giving a 100% up indicator.
[twitter-dev] Tweeting from PHP backed will also require OAuth in the upcoming changes?
Hi guys, Quick question that hunts me and can't find an answer. I'm using this line of code to post tweets to my account direclty from my website $host = http://twitter.com/statuses/update.xml? status=.urlencode(stripslashes(urldecode($message))) and posting it with curl with my user/password Will this still going to work after Twitter upcoming June requirement for Oauth. It's unclear to me. Thanks, Paul
Re: [twitter-dev] Problems getting Twitter @anywhere up and running...
It's also possible that it's your local machine doesn't trust the root CA.
If you are on Windows and managed via domain controller/group policy, it's
possible your domain admin has set which root CA's your machine trusts by
default.
if your web site trying to use @anywhere isn't also on your intranet, try
testing it from home.
You may also have luck on your work machine if you can add the equifax root
CA to your certificate store.
On Fri, Apr 16, 2010 at 4:43 PM, Isaac Hepworth is...@twitter.com wrote:
Looks like you're using a proxy server which doesn't trust the Equifax root
certificate.
Is the proxy server under your control?
Isaac
On Fri, Apr 16, 2010 at 8:14 AM, techno wade.woj...@gmail.com wrote:
I am trying to do the most basic procedure possible here... yet seems
I have some sort of network related issue.
I am doing a basic:
twttr.anywhere(onTwitterLoaded);
function onTwitterLoaded(twitter) {
alert(!!!);
}
In my head I have:
script type=text/javascript src=http://platform.twitter.com/
anywhere.js?id=MYAPIKEYv=1http://platform.twitter.com/anywhere.js?id=MYAPIKEYv=1
/script
When I watch the traffic, I see the following:
GET http://platform.twitter.com/anywhere.js?id=MYAPIKEYv=1
GET http://platform0.twitter.com/1/javascripts/client.js
GET http://platform1.twitter.com/1/javascripts/client.bundle.js
CONNECT https://api.twitter.com/ (Status Failed, Failure:
SSLHandshake: Received fatal alert: unknown_ca) CONNECT
https://oauth.twitter.com/
(Status Failed, Failure: SSLHandshake: Received fatal alert:
unknown_ca)
Any idea what this is all about? Maybe my companies network setup/
firewall preventing those connections?
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
--
Josh Cohen - jos...@gmail.com
http://facebook.com/joshrcohen
http://twitter.com/joshco
[twitter-dev] Re: Tweeting from PHP backed will also require OAuth in the upcoming changes?
Hi Paul, Posting status updates using Basic Auth like that won't work any more after 6/30. You'll need to use a PHP oAuth class (there are a few of them at http://dev.twitter.com/pages/oauth_libraries#php) as well as register an oAuth app. Best, Y On May 3, 3:17 pm, Paul A. hellodev@gmail.com wrote: Hi guys, Quick question that hunts me and can't find an answer. I'm using this line of code to post tweets to my account direclty from my website $host = http://twitter.com/statuses/update.xml? status=.urlencode(stripslashes(urldecode($message))) and posting it with curl with my user/password Will this still going to work after Twitter upcoming June requirement for Oauth. It's unclear to me. Thanks, Paul
Re: [twitter-dev] Re: Upcoming changes to userstream preview
1) Mark can comment on oAuth. It's soon, but we've some static in the pipeline that needs to get grounded out before oAuth can go out. 2) Continue to use stream.twitter.com for service to service integrations. User Streams clusters, currently chirpstream.twitter.com and for a little while betastream.twitter.com, are already tuned for user consumption and thus already have much lower track and loc, limits, cannot do follow, etc. User streams clusters are likely to also have a different delivery latency distributions (wider), login latency distributions (skewed much longer and much wider) and overall uptime (lower at first). We haven't decided if we're going to dedup connections between cluster types yet. A very small number of test accounts per developer: don't worry about it. -John On Mon, May 3, 2010 at 11:38 AM, M. Edward (Ed) Borasky zzn...@gmail.com wrote: 1. What's the approximate date for the oAuth rollout? 2. Will I be able to connect to both userstreams and sample from the same Twitter account at the same time? I don't see a need to connect to 'filter', since most of the interesting 'filter' functionality is available in 'userstreams'. Right now, I have multiple test accounts - one for sample and one for each variant of filter that I use. I'd like to ditch those. I'm sure Twitter would like to see as few test accounts as possible cluttering up the space as well.
Re: [twitter-dev] Re: Getting error 6 on geo/nearby_places
we're definitely working through the issues involved launching bigger data
sets - the data sets that we're publicly supporting right now is the united
states.
On Mon, May 3, 2010 at 10:05 AM, mynetx myne...@googlemail.com wrote:
Thanks Raffi, somehow my test coordinates were odd, I admit.
When will places all over Germany be available? Neither my home town
nor the next big city is listed, while a small village I had been
visiting recently is listed.
I also hate staring at Unable to locate you. Try again beneath the
tweetbox on twitter.com... while Google Maps finds me perfectly.
mynetx
On May 3, 6:46 am, Raffi Krikorian ra...@twitter.com wrote:
looking at the coordinate you are passing in (37.996163, -127.441406) --
that's in the pacific ocean. i don't think our rockdove database has
anything for that location
On Sun, May 2, 2010 at 12:58 PM, mynetx myne...@googlemail.com wrote:
I am getting this:
{errors:[{code:6,message:No data available for the given
coordinate}],query:{type:nearby_places,url:http://
api.twitter.com/1/geo/nearby_places.json?
query=lat=37.996163accuracy=0autocomplete=falselong=-127.441406granula
rity=neighborhood,params:
{coordinates:{coordinates:
[-127.441406,37.996163],type:Point},query:,accuracy:
0,autocomplete:false,granularity:neighborhood}}}
when trying to locate ANY pair of latitude and longitude, as well as
with locating my own IP address.
What am I doing wrong?
--
Raffi Krikorian
Twitter Platform Team http://twitter.com/raffi
--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
[twitter-dev] I use http message to send request _token but Receive allways Unauthorized
pstrBase = POST URLEncode(Request_token_URL) _ oauth_callback%3D URLEncode(http:// www.mydomain.com/) _ %26oauth_consumer_key%3D Consumer_Key _ %26oauth_nonce%3D pstrTimer QP70eNmV _ %26oauth_signature_method%3DHMAC_SHA1 _ %26oauth_timestamp%3D pstrTimer _ %26oauth_version%3D1.0 Calculate the signature using HMAC-SHA1 (i check the algorithm with an example in twitter help) with this base and Consumer_secret + Post message: POST https://api.twitter.com/oauth/request_token HTTP/1.1 Host: api.twitter.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv: 1.9.1.9) Gecko/20100315 Firefox/3.5.9 Content-Type: application/x-www-form-urlencoded Content-Length: 232 Connection: keep-alive oauth_callback=http%3A%2F%2Fwww.mydomain.com%2Foauth_consumer_key= + Consumer_secret + oauth_nonce=63899QP70eNmVoauth_signature=pO802kFfXwaAOlq8PbcNqVbtvU4=oauth_signature_method=HMAC_SHA1oauth_timestamp=63899oauth_version=1.0 Always i receive HTTP/1.1 401 Unauthorized and Failed to validate oauth signature and token Can anyone help me, please. What is wrong? Thanks.
Re: [twitter-dev] Re: Tweeting from PHP backed will also require OAuth in the upcoming changes?
You can checkout this page describing using a script to post to a single Twitter account: http://dev.twitter.com/pages/oauth_single_token One of the examples is for my PHP library: http://github.com/abraham/twitteroauth Abraham On Mon, May 3, 2010 at 13:04, YCBM youcannotb...@gmail.com wrote: Hi Paul, Posting status updates using Basic Auth like that won't work any more after 6/30. You'll need to use a PHP oAuth class (there are a few of them at http://dev.twitter.com/pages/oauth_libraries#php) as well as register an oAuth app. Best, Y On May 3, 3:17 pm, Paul A. hellodev@gmail.com wrote: Hi guys, Quick question that hunts me and can't find an answer. I'm using this line of code to post tweets to my account direclty from my website $host = http://twitter.com/statuses/update.xml? status=.urlencode(stripslashes(urldecode($message))) and posting it with curl with my user/password Will this still going to work after Twitter upcoming June requirement for Oauth. It's unclear to me. Thanks, Paul -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Search API or Streaming API?
If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
Re: [twitter-dev] An odd scenario I can't solve
You could wrap span with an ID around the string with the @screen_name in it. and have @Anywhere only trigger on that ID. You should also be able to use jQuery selectors to only closely match the content you want hovercarded. Something like: T(td#content p.center).hovercards(); I think should work. http://api.jquery.com/category/selectors/ Abraham On Thu, Apr 29, 2010 at 15:35, Matt McGee m...@mattmcgee.com wrote: Hi everyone. Hope you'll be kind to a non-programmer here. :-) I think I have an unusual circumstance involving the use of @anywhere on my web site. The site in question is called @U2. Yep, been using the @ symbol on our site since 1998 and it's all over the place. The specific problem I'm having can be seen on this page: http://www.atu2.com/news/larry-mullen-stars-in-canadian-movie.html I'm using the hovercards and you can see the author's name correctly brings up her hovercard for @tassoula. I'm calling the javascript to only show hovercards in this main content window, so that the headings on the right (@U2 Blog Posts, @U2 Calendar, etc.) won't be linked. But ... as you can see in the first sentence of the article, the mention of our site name is also linked to a hovercard for @U2. There's no Twitter account in that name. (The band should own it but doesn't.) Is there any way to solve for this? Thanks in advance. Matt -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
