[twitter-dev] Re: User tag inside users/show
Excellent, thanks guys seems to be working fine now :) On May 6, 4:07 am, Sami sami.ben.romdh...@gmail.com wrote: How long does it take for the change to propagate. My application is still down along with every application using the twitter4j java library Thanks
[twitter-dev] OAuth User Numbers for Apps
Hi Guys
With the new developer portal up and running, is there any timeframe
for bringing back the authenticated user stats for apps, and are there
any plans to improve the reporting in this regard (so, active users in
the past 30 days on top of 'all-time authenticated users')? We're
currently assessing the relative user numbers for @socialiteapp and
given that the http://twitter.com/oauth_clients/details/{client ID}
URL is perma-fail-whaling (previously it used to work after 10 minutes
or so), we'd love to be able to see some details on the apps
authenticated user numbers.
Thanks!
Nik
--
Nik Fletcher
Support / QA Manager, Realmac Software
@nikf
[twitter-dev] Re: users/show bug with nested user object
How long should this fix take to propagate around, Taylor? I still see a user with just an id property and nothing else when I call users/ show. Matt On May 6, 11:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod- Hide quoted text - - Show quoted text -
[twitter-dev] JSONObject[created_at] not found.:{id:116439936}
I used the component twitter4j-core-2.1.2 and it worked properly. I've implemented on the production site. Today, after a few days that worked correctly produces this error: JSONObject [created_at] not found.: (Id: 116439936) I did some testing and I have observed that requests such as getId (), which is required Credentials and Rate Limited, produces an error as I stated above but when required as UpdateStatus () Rate Credentials required but not limited, functioning properly. Through the method I getRateLimitStatus () if I had problems with rate limited but that is like ip account as there are no problems. What can I do Thanks for your help. Alfredo
[twitter-dev] Re: User tag inside users/show
I'm still seeing this problem on statuses as recent as 5/6 @ 7:45 AM UTC, or three hours ago for me. For example, as of this moment, http://api.twitter.com/1/users/show/shanselman.xml is exhibiting this issue. On May 5, 8:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text - - Show quoted text -
[twitter-dev] Re: User tag inside users/show
The problem persists for me and a lot of my users. If I visit this URL: http://api.twitter.com//1/users/show.xml?screen_name=mabster ... I see a user element embedded in the status section with only an ID. Do others not see that? How aggressive is the caching? It's been hours since it was apparently fixed. Cheers, Matt On May 6, 4:37 pm, Rich rhyl...@gmail.com wrote: Excellent, thanks guys seems to be working fine now :) On May 6, 4:07 am, Sami sami.ben.romdh...@gmail.com wrote: How long does it take for the change to propagate. My application is still down along with every application using the twitter4j java library Thanks- Hide quoted text - - Show quoted text -
[twitter-dev] Re: users/show bug with nested user object
Seems like the cache has still not cleared. Regards, Rohit On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: User tag inside users/show
Still not working here... (based in London if that helps). On May 6, 7:37 am, Rich rhyl...@gmail.com wrote: Excellent, thanks guys seems to be working fine now :) On May 6, 4:07 am, Sami sami.ben.romdh...@gmail.com wrote: How long does it take for the change to propagate. My application is still down along with every application using the twitter4j java library Thanks- Hide quoted text - - Show quoted text -
[twitter-dev] How to check the access tokens before directing to a sign in /allow, deny page?
Hi,
I have a twitter application and I want to check the following
scenario.
A user logged into his twitter account and already granted permissions
to make status notes through another application.
When user hits the connect button, the navigation directs to Allow/
Deny page which he already confirmed. I want this to by pass and
automatically allowed the user to update the status notes in their
twitter wall.
I used the following code and it doesn't work as expected. Could you
please help me to solve this?
const string requestUrl = http://twitter.com/oauth/request_token;;
// This is the URL to exchange the request token for an
access token
const string accessUrl = http://twitter.com/oauth/
access_token;
// This is the URL to access a protected resource; in this
case,
// the authorized user’s timeline
const string userTimeline = http://twitter.com/statuses/
user_timeline.xml;
// This is your application’s consumer key
const string key = key;
// This is your application’s consumer secret
const string secret = secret;
// This is the URL to send a user for authorization
const string authorizeUrl = http://twitter.com/oauth/
authorize?oauth_token=;
// Retrieve and parse the request token
var response = OAuth.GetRequestToken(requestUrl, key,
secret);
var collection = HttpUtility.ParseQueryString(response);
var requestToken = new { Token = collection[0],
TokenSecret = collection[1] };
// At this point, your application must wait for the user
to return
var url = String.Concat(authorizeUrl,
Uri.EscapeDataString(requestToken.Token));
string value = OAuth.GetAccessToken(accessUrl,
key,
secret,
access token of a
user,// this is a unique value for a user
access token secret of
the user); // unique value for a user
// above method doesn't give me the the required value in fact, it
gives an error calledthis method needs to call with request
tokens
I want the following 4 lines of code to be executed only if the
user hasn't granted permissions or not logged in
Process proc = new Process();
proc.StartInfo.FileName = iexplore;
proc.StartInfo.Arguments = url;
proc.Start();
// Exchange the request token for the access token after
user approval
response = OAuth.GetAccessToken(accessUrl,
key,
secret,
requestToken.Token,
requestToken.TokenSecret);
while (String.IsNullOrEmpty(response.Trim()))
{
response = OAuth.GetAccessToken(accessUrl,
key,
secret,
requestToken.Token,
requestToken.TokenSecret);
}
if (response.Contains(screen_name))
{
collection = HttpUtility.ParseQueryString(response);
var accessToken = new { Token = collection[0],
TokenSecret = collection[1] };
// Get the user timeline using OAuth credentials
response = OAuth.GetProtectedResource(userTimeline,
GET,
key,
secret,
accessToken.Token,
accessToken.TokenSecret);
OAuthTokens accToken = new OAuthTokens();
accToken.AccessToken = collection[0].ToString();
accToken.AccessTokenSecret = collection[1].ToString();
accToken.ConsumerKey = key;
accToken.ConsumerSecret = secret;
TwitterStatus TweetStatus = new
TwitterStatus(accToken);
TweetStatus.Update(test message);
}
[twitter-dev] Re: User tag inside users/show
My application is still not working? I use Twitter4j and it is still giving a problem. Regards, Rohit On May 6, 11:37 am, Rich rhyl...@gmail.com wrote: Excellent, thanks guys seems to be working fine now :) On May 6, 4:07 am, Sami sami.ben.romdh...@gmail.com wrote: How long does it take for the change to propagate. My application is still down along with every application using the twitter4j java library Thanks
[twitter-dev] Re: User tag inside users/show
We still see this issue on every request at http://streamd.in , Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: User tag inside users/show
Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: User tag inside users/show
i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: users/show bug with nested user object
It's taking a long time. We're investigating possible means to hasten the resolution and any other reasons the cache might not be resolving. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 3:17 AM, rohit mrro...@gmail.com wrote: Seems like the cache has still not cleared. Regards, Rohit On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
Re: [twitter-dev] OAuth User Numbers for Apps
Hi Nik,
Long-term, we'd really like to offer more stats for developers on
dev.twitter.com.. The user count was specifically removed from the new dev
portal for the fail whale reason you noted -- applications with a large
number of associated access tokens cause issues right now when sourcing
data. There's really no timeframe for more stats right now though.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, May 6, 2010 at 2:34 AM, Nik Fletcher nik.fletc...@gmail.com wrote:
Hi Guys
With the new developer portal up and running, is there any timeframe
for bringing back the authenticated user stats for apps, and are there
any plans to improve the reporting in this regard (so, active users in
the past 30 days on top of 'all-time authenticated users')? We're
currently assessing the relative user numbers for @socialiteapp and
given that the http://twitter.com/oauth_clients/details/{client ID}
URL is perma-fail-whaling (previously it used to work after 10 minutes
or so), we'd love to be able to see some details on the apps
authenticated user numbers.
Thanks!
Nik
--
Nik Fletcher
Support / QA Manager, Realmac Software
@nikf
Re: [twitter-dev] JSONObject[created_at] not found.:{id:116439936}
You might be experiencing some issues due to a bug that is slowly purging itself from our systems. Judging by the error, your JSON parser is stopping because it was trying to coerce a user node that only had an id into some other construct, and it's refusing to do so without a created_at field descending from the user node. The bug we have going through the system is such that on a users/show call, we are embedding a user node in the status object that is embedded in the user node. The bug has been fixed but its impact has not. We're working to clear this up as quickly as we can. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 3:30 AM, Alfredo Baraldi alfredo.bara...@gmail.comwrote: I used the component twitter4j-core-2.1.2 and it worked properly. I've implemented on the production site. Today, after a few days that worked correctly produces this error: JSONObject [created_at] not found.: (Id: 116439936) I did some testing and I have observed that requests such as getId (), which is required Credentials and Rate Limited, produces an error as I stated above but when required as UpdateStatus () Rate Credentials required but not limited, functioning properly. Through the method I getRateLimitStatus () if I had problems with rate limited but that is like ip account as there are no problems. What can I do Thanks for your help. Alfredo
[twitter-dev] Re: OAuth support and reformatted DMs live on user streams
Hey guys, a couple questions/remarks on the new user streams features: 1) OAuth I have no problem using the stream with BasicAuth, nor using the REST API with OAuth. However I'm always getting 401s with OAuth on the stream, even though Zac's fork or earlybird works flawlessly. Just to try and locate the problem I tried signing the request with the official noob tool at http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ and sending the header with curl (with fiddling with spaces, tabs newline just in case, and even the realm value - just because earlybird's impl doesn't send it), and I still can't login. While my own code signing matches the parameters this tool outputs (and works on api.twitter.com) it doesn't match what the ruby gem generates, even when using the same timestamp and nonce, so I was suspecting some difference in the base string. (I don't know Ruby, or how to get the Base String there, but there's apparently a signature_base_string method, and it did seem to have all the oauth params in the query string) 2) +1 on the user burping at the beginning :) 3) Are the deletion notices going to be hydrated too ? ATM it's a little raw. While it's understandable for the status not to be there since it's just been deleted, maybe the full JSON user could be there instead of just its id ? Thanks Rémy @lqd On May 6, 12:41 am, Mark McBride mmcbr...@twitter.com wrote: Ok. The query string OAuth variant should be working now. We only support HMAC-SHA1 (just like twitter.com does) for signature methods, and don't have plans to support other schemes. ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 3:21 PM, John Kalucki j...@twitter.com wrote: We should probably just burp the whole user object out at connection start. On Wed, May 5, 2010 at 3:12 PM, Zac Bowling zbowl...@gmail.com wrote: Hydrated message support in earlybird! http://github.com/zbowling/earlybird/ OAuth in query string doesn't work and only HMAC-SHA1 signature (unless you only allow plaintext over SSL) but its fine. One feature request would be an inital event with the users credentials just like how the user's social graph comes down initially. Right now I don't know the user's screen_name unless I also hit api.twitter.com or he tells me on the command line. With that I could drop the dependency on the twitter gem. Zac Bowling @zbowling On Wed, May 5, 2010 at 10:54 AM, Mark McBride mmcbr...@twitter.com wrote: It should support both. Can you send me a direct email with a URL that you tried? ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 10:38 AM, Zac Bowling zbowl...@gmail.com wrote: My fork of earlybird works: http://github.com/zbowling/earlybird/ Fixing it to support hydrated objects. One thing is that it doesn't appear to support query string passed OAuth params but if I pass it as authentication headers it works. Zac Bowling On Wed, May 5, 2010 at 10:31 AM, Mark McBride mmcbr...@twitter.com wrote: OAuth support on betastream is live now. This is different OAuth implementation than we use on twitter.com, so if you find any rough edges please let us know quick like. The changes to make direct messages more distinguishable from tweets has also been pushed. This will probably require some changes in parsing logic when dealing with DMs. ---Mark http://twitter.com/mccv
[twitter-dev] Re: How to check the access tokens before directing to a sign in /allow, deny page?
Hello, First off I'm curious as to what language this is. A quick glance suggests javascript. Also what libraries are you using? Regarding the actual auth workflow, what exactly is the process that you are utilizing? Is it a callback URL or pin based auth? You call OAuth.GetRequestToken, but I don't see how you pass the return value of this to OAuth.GetAccessToken. - Konpaku Kogasa
[twitter-dev] Re: users/show bug with nested user object
Just as a follow-up, I've just seen a userid/user again while doing a verify_credentials.json call after I've retweeted some user. The userid/user entry is inside the status entry of the calling user's user entry. Oh, complex. It's like: user status retweeted_status.../retweeted_status userid/user /status /user Here's the link to the data: http://data.mobileways.de/brokentweet.txt Ole -- Jan Ole Suhr s...@mobileways.de On Twitter: http://twitter.com/janole On 6 Mai, 15:18, Taylor Singletary taylorsinglet...@twitter.com wrote: It's taking a long time. We're investigating possible means to hasten the resolution and any other reasons the cache might not be resolving. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 3:17 AM, rohit mrro...@gmail.com wrote: Seems like the cache has still not cleared. Regards, Rohit On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: JSONObject[created_at] not found.:{id:116439936}
Hi, A snapshot build which workarounds the issue is now available. http://groups.google.com/group/twitter4j/browse_thread/thread/5f96af5eb7b9d141 Cheers, Yusuke On May 6, 10:39 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: You might be experiencing some issues due to a bug that is slowly purging itself from our systems. Judging by the error, your JSON parser is stopping because it was trying to coerce a user node that only had an id into some other construct, and it's refusing to do so without a created_at field descending from the user node. The bug we have going through the system is such that on a users/show call, we are embedding a user node in the status object that is embedded in the user node. The bug has been fixed but its impact has not. We're working to clear this up as quickly as we can. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 3:30 AM, Alfredo Baraldi alfredo.bara...@gmail.comwrote: I used the component twitter4j-core-2.1.2 and it worked properly. I've implemented on the production site. Today, after a few days that worked correctly produces this error: JSONObject [created_at] not found.: (Id: 116439936) I did some testing and I have observed that requests such as getId (), which is required Credentials and Rate Limited, produces an error as I stated above but when required as UpdateStatus () Rate Credentials required but not limited, functioning properly. Through the method I getRateLimitStatus () if I had problems with rate limited but that is like ip account as there are no problems. What can I do Thanks for your help. Alfredo
Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams
#1 Mark can help. #2 I filed a story for later triage. #3 What would the use case be for hydrating status deletion notes? For display purposes, I can see them being used to remove tweets - but displayed tweets should be indexed by status_id. What else might you want to display when a following deletes a displayed tweet? You also could keep the user object that was sent with the status, if needed. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, May 6, 2010 at 6:39 AM, lqd remy.ra...@gmail.com wrote: Hey guys, a couple questions/remarks on the new user streams features: 1) OAuth I have no problem using the stream with BasicAuth, nor using the REST API with OAuth. However I'm always getting 401s with OAuth on the stream, even though Zac's fork or earlybird works flawlessly. Just to try and locate the problem I tried signing the request with the official noob tool at http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ and sending the header with curl (with fiddling with spaces, tabs newline just in case, and even the realm value - just because earlybird's impl doesn't send it), and I still can't login. While my own code signing matches the parameters this tool outputs (and works on api.twitter.com) it doesn't match what the ruby gem generates, even when using the same timestamp and nonce, so I was suspecting some difference in the base string. (I don't know Ruby, or how to get the Base String there, but there's apparently a signature_base_string method, and it did seem to have all the oauth params in the query string) 2) +1 on the user burping at the beginning :) 3) Are the deletion notices going to be hydrated too ? ATM it's a little raw. While it's understandable for the status not to be there since it's just been deleted, maybe the full JSON user could be there instead of just its id ? Thanks Rémy @lqd On May 6, 12:41 am, Mark McBride mmcbr...@twitter.com wrote: Ok. The query string OAuth variant should be working now. We only support HMAC-SHA1 (just like twitter.com does) for signature methods, and don't have plans to support other schemes. ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 3:21 PM, John Kalucki j...@twitter.com wrote: We should probably just burp the whole user object out at connection start. On Wed, May 5, 2010 at 3:12 PM, Zac Bowling zbowl...@gmail.com wrote: Hydrated message support in earlybird! http://github.com/zbowling/earlybird/ OAuth in query string doesn't work and only HMAC-SHA1 signature (unless you only allow plaintext over SSL) but its fine. One feature request would be an inital event with the users credentials just like how the user's social graph comes down initially. Right now I don't know the user's screen_name unless I also hit api.twitter.com or he tells me on the command line. With that I could drop the dependency on the twitter gem. Zac Bowling @zbowling On Wed, May 5, 2010 at 10:54 AM, Mark McBride mmcbr...@twitter.com wrote: It should support both. Can you send me a direct email with a URL that you tried? ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 10:38 AM, Zac Bowling zbowl...@gmail.com wrote: My fork of earlybird works: http://github.com/zbowling/earlybird/ Fixing it to support hydrated objects. One thing is that it doesn't appear to support query string passed OAuth params but if I pass it as authentication headers it works. Zac Bowling On Wed, May 5, 2010 at 10:31 AM, Mark McBride mmcbr...@twitter.com wrote: OAuth support on betastream is live now. This is different OAuth implementation than we use on twitter.com, so if you find any rough edges please let us know quick like. The changes to make direct messages more distinguishable from tweets has also been pushed. This will probably require some changes in parsing logic when dealing with DMs. ---Mark http://twitter.com/mccv
[twitter-dev] Re: users/show bug with nested user object
I'm still seeing the errant userid/user node at noon EST. On May 6, 10:03 am, janole s...@mobileways.de wrote: Just as a follow-up, I've just seen a userid/user again while doing a verify_credentials.json call after I've retweeted some user. The userid/user entry is inside the status entry of the calling user's user entry. Oh, complex. It's like: user status retweeted_status.../retweeted_status userid/user /status /user Here's the link to the data:http://data.mobileways.de/brokentweet.txt Ole -- Jan Ole Suhr s...@mobileways.de On Twitter:http://twitter.com/janole On 6 Mai, 15:18, Taylor Singletary taylorsinglet...@twitter.com wrote: It's taking a long time. We're investigating possible means to hasten the resolution and any other reasons the cache might not be resolving. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 3:17 AM, rohit mrro...@gmail.com wrote: Seems like the cache has still not cleared. Regards, Rohit On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: User tag inside users/show
This appears to still be broken. It affects anyone using the TweetSharp library as well. There's a workaround (http:// tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but hopefully it will be fixed soon so that we don't have to redeploy with the workaround. On May 6, 5:23 am, Raffi Krikorian ra...@twitter.com wrote: i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: User tag inside users/show
We're working on getting this fixed as soon as we can. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 9:12 AM, irhetoric karst...@microsoft.com wrote: This appears to still be broken. It affects anyone using the TweetSharp library as well. There's a workaround (http:// tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but hopefully it will be fixed soon so that we don't have to redeploy with the workaround. On May 6, 5:23 am, Raffi Krikorian ra...@twitter.com wrote: i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams
Did you adjust the timestamp in that tool? The hosebird implementation tolerates at most a 5 minute clock skew... in other words if it receives a timestamp that is 5 minutes older (or newer) than the current time, it rejects the request. ---Mark http://twitter.com/mccv On Thu, May 6, 2010 at 6:39 AM, lqd remy.ra...@gmail.com wrote: Hey guys, a couple questions/remarks on the new user streams features: 1) OAuth I have no problem using the stream with BasicAuth, nor using the REST API with OAuth. However I'm always getting 401s with OAuth on the stream, even though Zac's fork or earlybird works flawlessly. Just to try and locate the problem I tried signing the request with the official noob tool at http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ and sending the header with curl (with fiddling with spaces, tabs newline just in case, and even the realm value - just because earlybird's impl doesn't send it), and I still can't login. While my own code signing matches the parameters this tool outputs (and works on api.twitter.com) it doesn't match what the ruby gem generates, even when using the same timestamp and nonce, so I was suspecting some difference in the base string. (I don't know Ruby, or how to get the Base String there, but there's apparently a signature_base_string method, and it did seem to have all the oauth params in the query string) 2) +1 on the user burping at the beginning :) 3) Are the deletion notices going to be hydrated too ? ATM it's a little raw. While it's understandable for the status not to be there since it's just been deleted, maybe the full JSON user could be there instead of just its id ? Thanks Rémy @lqd On May 6, 12:41 am, Mark McBride mmcbr...@twitter.com wrote: Ok. The query string OAuth variant should be working now. We only support HMAC-SHA1 (just like twitter.com does) for signature methods, and don't have plans to support other schemes. ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 3:21 PM, John Kalucki j...@twitter.com wrote: We should probably just burp the whole user object out at connection start. On Wed, May 5, 2010 at 3:12 PM, Zac Bowling zbowl...@gmail.com wrote: Hydrated message support in earlybird! http://github.com/zbowling/earlybird/ OAuth in query string doesn't work and only HMAC-SHA1 signature (unless you only allow plaintext over SSL) but its fine. One feature request would be an inital event with the users credentials just like how the user's social graph comes down initially. Right now I don't know the user's screen_name unless I also hit api.twitter.com or he tells me on the command line. With that I could drop the dependency on the twitter gem. Zac Bowling @zbowling On Wed, May 5, 2010 at 10:54 AM, Mark McBride mmcbr...@twitter.com wrote: It should support both. Can you send me a direct email with a URL that you tried? ---Mark http://twitter.com/mccv On Wed, May 5, 2010 at 10:38 AM, Zac Bowling zbowl...@gmail.com wrote: My fork of earlybird works: http://github.com/zbowling/earlybird/ Fixing it to support hydrated objects. One thing is that it doesn't appear to support query string passed OAuth params but if I pass it as authentication headers it works. Zac Bowling On Wed, May 5, 2010 at 10:31 AM, Mark McBride mmcbr...@twitter.com wrote: OAuth support on betastream is live now. This is different OAuth implementation than we use on twitter.com, so if you find any rough edges please let us know quick like. The changes to make direct messages more distinguishable from tweets has also been pushed. This will probably require some changes in parsing logic when dealing with DMs. ---Mark http://twitter.com/mccv
[twitter-dev] Slow response to twitter updates for a third party app
Hi, I am developing a third party application for posting updates to Twitter for users of my site. I find that the time to post a tweet from my website varies greatly during the day (from 20 seconds to 1 second). I have verified, this long delay is due to a slow response from Twitter. On the other hand, posting an update from another third party website takes only from 6 sec to 1 sec during the day. So my question is: Does Twitter allocate different priorities to third party applications? If yes, what can I do to get a higher priority for updates from my website. Thanks, Raj Kumar
[twitter-dev] UPDATE: Embedded user object issue
Hi Folks, Wanted to give everyone an update on this issue that's continuing to effect certain API clients: Though we deployed a fix last night for the issue, certain idiosyncracies in our caching system have made the fix moot for a large percentage of our API output traffic. We are in the process now of coaxing the cache away. Thanks for your continued patience! Taylor -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: User tag inside users/show
Any ETA? We need to know how long, and propagation time, or we will have to deploy a workaround. It's been about 24 hours now, and t is affecting our customers. Thanks, Melissa, Awareness On May 6, 12:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working on getting this fixed as soon as we can. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 9:12 AM, irhetoric karst...@microsoft.com wrote: This appears to still be broken. It affects anyone using the TweetSharp library as well. There's a workaround (http:// tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but hopefully it will be fixed soon so that we don't have to redeploy with the workaround. On May 6, 5:23 am, Raffi Krikorian ra...@twitter.com wrote: i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: User tag inside users/show
We think this should be all resolved out within the next few hours -- already hearing reports of some relief for a number of Twitter clients. We're slowly expiring the cache on several objects in the system to clear this up rather than waiting for them to clear on their own. This has to be done with great care. Thanks for the patience and apologies for the effect this has on your users. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 1:01 PM, melissa melissaleff...@gmail.com wrote: Any ETA? We need to know how long, and propagation time, or we will have to deploy a workaround. It's been about 24 hours now, and t is affecting our customers. Thanks, Melissa, Awareness On May 6, 12:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working on getting this fixed as soon as we can. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 9:12 AM, irhetoric karst...@microsoft.com wrote: This appears to still be broken. It affects anyone using the TweetSharp library as well. There's a workaround (http:// tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but hopefully it will be fixed soon so that we don't have to redeploy with the workaround. On May 6, 5:23 am, Raffi Krikorian ra...@twitter.com wrote: i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] TCL oAuth
I currently have been working on an application under TCL to post my twitter timeline, direct messages, profile information and such (almost a full TCL app) for my IRC eggdrop bot. I've been using the Basic Authentication method and I've just read come 6/30 I won't be able to use this method any longer. Has anyone come across an oAuth library for TCL that I can look into using so I can continue to work on this project of mine and not have it die when the Basic Auth method dies here soon? If you are interested in what I have ATM, my code can be found here: http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/master/twitter.sb6 Any help for the conversion will be greatly appreciated.
Re: [twitter-dev] TCL oAuth
I have written an OAuth client in Tcl for Twitter Karma, but it's in no condition to open source at the moment. However, I can tell you that the sha1 package (for sha1::hmac) works, and the base64 package (for base64::encode) too. OAuth really isn't that hard to implement, really. And, from the sounds of it, you don't even need a full OAuth consumer implementation, just a working access token for your account - perhaps there's a simple utility out there that you can feed your consumer key and secret into and have it output your access token that you can then use. On 5/6/10 5:01 PM, Dustin wrote: I currently have been working on an application under TCL to post my twitter timeline, direct messages, profile information and such (almost a full TCL app) for my IRC eggdrop bot. I've been using the Basic Authentication method and I've just read come 6/30 I won't be able to use this method any longer. Has anyone come across an oAuth library for TCL that I can look into using so I can continue to work on this project of mine and not have it die when the Basic Auth method dies here soon? If you are interested in what I have ATM, my code can be found here: http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/master/twitter.sb6 Any help for the conversion will be greatly appreciated. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] TCL oAuth
Can't help much with a TCL implementation, but once you've registered an application you can view the application record on dev.twitter.com and click on a button called My Access Token to get the access token and access token secret for your account from your application's perspective, which simplifies the I just need my access token use case considerbly. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 6, 2010 at 2:48 PM, Dossy Shiobara do...@panoptic.com wrote: I have written an OAuth client in Tcl for Twitter Karma, but it's in no condition to open source at the moment. However, I can tell you that the sha1 package (for sha1::hmac) works, and the base64 package (for base64::encode) too. OAuth really isn't that hard to implement, really. And, from the sounds of it, you don't even need a full OAuth consumer implementation, just a working access token for your account - perhaps there's a simple utility out there that you can feed your consumer key and secret into and have it output your access token that you can then use. On 5/6/10 5:01 PM, Dustin wrote: I currently have been working on an application under TCL to post my twitter timeline, direct messages, profile information and such (almost a full TCL app) for my IRC eggdrop bot. I've been using the Basic Authentication method and I've just read come 6/30 I won't be able to use this method any longer. Has anyone come across an oAuth library for TCL that I can look into using so I can continue to work on this project of mine and not have it die when the Basic Auth method dies here soon? If you are interested in what I have ATM, my code can be found here: http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/master/twitter.sb6 Any help for the conversion will be greatly appreciated. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: users/show bug with nested user object
Also still seeing this as at 6th May 11:23pm GMT.
[twitter-dev] what's wrong with my xAuth code ???
every time i get failed to validate outh token and signature :(
here's my simple code
var username = username,
password = password,
url=
https://api.twitter.com/oauth/access_token;,
key = key,
timestamp = +new Date,
nonce = thisismynoncce + timestamp;
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(token_secret,
base_string);
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);
}
})
[twitter-dev] Re: users/show bug with nested user object
Over time I've learned it is a best practice to check the integrity of a returned Twitter object despite the fact that the HTTP response code is 200.
[twitter-dev] Re: share user account activity data?
Hello, John. Thank you for the referral to Spritzer. I will re-structure my data model to benefit from its activity indications. I have throttled back and will approach you directly when I have production code serving Twitter users. I have 100,000 opt-ins and 3,000 paying customers for two data products (LJMindMap and Radar) on LiveJournal.com. I also produce results for academics studying social network patterns there, but I am a commercial provider of individualized social graph services for users, not for studies. Regards, John Dempsey On Mar 26, 6:55 am, John Kalucki j...@twitter.com wrote: Stop doing this. You are stressing the system and producing questionable results. You run a very high risk of blacklisting. Also, there are many many existing studies that go over this same ground of active users and break the data down in painstaking detail. Instead, take the Spritzer sample feed on the Streaming API if you must collect this data. This feed will, over time, give you a very accurate picture of active accounts, which I think you mean tweeting accounts. Many users are active without tweeting, or without even ever logging in to Twitter. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 26, 2010 at 12:38 AM, mcfnord mcfn...@gmail.com wrote: I'd love a list of id's for active accounts and another list of id's for inactive ones, by some sensible criteria of activity. Publishing this is in twitter.com's interest, admittedly for that large first and second crawl. I'm calling this for everyone: http://twitter.com/friends/ids.xml/?user_id=12345 And I need to call it again after some time passes to determine activity. Maybe there's a good alternative? I'm not belly-aching about the two complete canvases, but I think i calculated that it takes my whitelisted application 145 days to complete from now, consuming its full allotment of 20k every hour of every day. Is that right? well it's close. I'm very new to the scene so please tip me off if there's a shortcut datasource that reports inactive accounts, so i can dial api traffic about inactives way back. i'd love a bulk appraisal of account activity/inactivity as a binary condition or in any other flavor (status update is another sensible source as an activity inference). all clues appreciated. thanks cats! john To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text -
[twitter-dev] Re: User tag inside users/show
I'm back up -- thanks for the quick response. On May 6, 1:36 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We think this should be all resolved out within the next few hours -- already hearing reports of some relief for a number of Twitter clients. We're slowly expiring the cache on several objects in the system to clear this up rather than waiting for them to clear on their own. This has to be done with great care. Thanks for the patience and apologies for the effect this has on your users. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 1:01 PM, melissa melissaleff...@gmail.com wrote: Any ETA? We need to know how long, and propagation time, or we will have to deploy a workaround. It's been about 24 hours now, and t is affecting our customers. Thanks, Melissa, Awareness On May 6, 12:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working on getting this fixed as soon as we can. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 9:12 AM, irhetoric karst...@microsoft.com wrote: This appears to still be broken. It affects anyone using the TweetSharp library as well. There's a workaround (http:// tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but hopefully it will be fixed soon so that we don't have to redeploy with the workaround. On May 6, 5:23 am, Raffi Krikorian ra...@twitter.com wrote: i'm currently looking into this now. On Thu, May 6, 2010 at 4:51 AM, Rich rhyl...@gmail.com wrote: Yep looks like I spoke to soon, many of my users are still seeing this issue. I've actually handled it but Apple are now taking about a week to approve updates On May 6, 6:50 am, Raul raulr...@gmail.com wrote: We still see this issue on every request athttp://streamd.in, Also all other apps that use twitter4j are experiencing this issue. On May 5, 6:04 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: This should now be fixed, though it may take a little while for the cache to completely clear the labyrinth. Let us know if you're still having wide spread problems. Thanks! Taylor On Wed, May 5, 2010 at 2:27 PM, Rich rhyl...@gmail.com wrote: Cool, thanks Raffi, I was more concerned if it was intentional rather than a bug :) Of course we all get unintentional bugs from time to time On May 5, 10:21 pm, Raffi Krikorian ra...@twitter.com wrote: my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) or...@orianmarx.com wrote: Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: How to check the access tokens before directing to a sign in /allow, deny page?
Hi, Thanks for the response. I'm using C#.NET and this is all inline coding. However, yesterday I found a way to check the token values from a protected resource, It worked fine for me with slight database programming to store and retrive the twitter generated access tokens. Libraries I used to call Twitter API, - Wrox.Auth library - Twitterizer Chathura On Thu, May 6, 2010 at 7:27 PM, Konpaku Kogasa kogasa.l...@gmail.comwrote: Hello, First off I'm curious as to what language this is. A quick glance suggests javascript. Also what libraries are you using? Regarding the actual auth workflow, what exactly is the process that you are utilizing? Is it a callback URL or pin based auth? You call OAuth.GetRequestToken, but I don't see how you pass the return value of this to OAuth.GetAccessToken. - Konpaku Kogasa
[twitter-dev] Re: TCL oAuth
I was lookin at maybe doing Out-of-band/PIN Code Authentication. However, I don't see much documentation on how to go about doing this. On May 6, 4:48 pm, Dossy Shiobara do...@panoptic.com wrote: I have written an OAuth client in Tcl for Twitter Karma, but it's in no condition to open source at the moment. However, I can tell you that the sha1 package (for sha1::hmac) works, and the base64 package (for base64::encode) too. OAuth really isn't that hard to implement, really. And, from the sounds of it, you don't even need a full OAuth consumer implementation, just a working access token for your account - perhaps there's a simple utility out there that you can feed your consumer key and secret into and have it output your access token that you can then use. On 5/6/10 5:01 PM, Dustin wrote: I currently have been working on an application under TCL to post my twitter timeline, direct messages, profile information and such (almost a full TCL app) for my IRC eggdrop bot. I've been using the Basic Authentication method and I've just read come 6/30 I won't be able to use this method any longer. Has anyone come across an oAuth library for TCL that I can look into using so I can continue to work on this project of mine and not have it die when the Basic Auth method dies here soon? If you are interested in what I have ATM, my code can be found here: http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/maste... Any help for the conversion will be greatly appreciated. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: TCL oAuth
I don't think going about using my access token would be a viable solution as I have no way of keeping those tokens secret. On May 6, 4:58 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Can't help much with a TCL implementation, but once you've registered an application you can view the application record on dev.twitter.com and click on a button called My Access Token to get the access token and access token secret for your account from your application's perspective, which simplifies the I just need my access token use case considerbly. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 2:48 PM, Dossy Shiobara do...@panoptic.com wrote: I have written an OAuth client in Tcl for Twitter Karma, but it's in no condition to open source at the moment. However, I can tell you that the sha1 package (for sha1::hmac) works, and the base64 package (for base64::encode) too. OAuth really isn't that hard to implement, really. And, from the sounds of it, you don't even need a full OAuth consumer implementation, just a working access token for your account - perhaps there's a simple utility out there that you can feed your consumer key and secret into and have it output your access token that you can then use. On 5/6/10 5:01 PM, Dustin wrote: I currently have been working on an application under TCL to post my twitter timeline, direct messages, profile information and such (almost a full TCL app) for my IRC eggdrop bot. I've been using the Basic Authentication method and I've just read come 6/30 I won't be able to use this method any longer. Has anyone come across an oAuth library for TCL that I can look into using so I can continue to work on this project of mine and not have it die when the Basic Auth method dies here soon? If you are interested in what I have ATM, my code can be found here: http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/maste... Any help for the conversion will be greatly appreciated. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
