[twitter-dev] Re: Twitpocalypse Announcement
Hi Matt, Could you also let us know how you increment tweet numbers. It is not constantly linearly incremented from 1, is it. That would mean there are over 2 billion tweets in the system, which isn't. On Sat, Jun 13, 2009 at 1:52 AM, Matt Sanford m...@twitter.com wrote: Hi there, That is indeed what I meant. We are planning to skip some ids to force the 2^32 change during business hours. Twitter itself should be fine but I originally announced this to the list so people could make sure they'll also be fine. There is no change to the format of responses and the number will continue to grow upward. This was just fair warning that you might have used the Rails default definition (or some other method) that relies on signed 32-bit integers. The 'decide to do this' part is deciding to do this now by skipping ids rather than let it occur naturally 12 hours from now when people have been up for 24-hours and might not be at their best. Let's not allow the 'insulting' vagueness devolve into insulting tone, please. We're working on co-ordinating internally to do this at 21:00 GMT but like all things involving groups of people we may run a little late. Sometime after 21:00 GMT this is still planned. We'll update @twitterapi when the exact time comes. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 12, 2009, at 1:06 PM, Stuart wrote: 2009/6/12 J. Adam Moore jadammo...@gmail.com: So do I just allocate as many bits as I can in my database to the id field and hope that it doesn't ever run out? I'm confused why you just announced that. Okay, so an overflow is happening. Is that your fault? Is this fixable on your end, my end. Is this just for people who are using 32-bit signed ints to store ids? Decide to do what? Roll it over like an odometer or increase the field size? Forgive me for being an idiot, but 'decide to do this' is just about vague enough to be insulting. I was happily under the assumption that this problem was considered long, long ago when the field size was initially chosen by who I also assumed to be smart people. I read it as we're considering skipping a bunch of IDs so we hit the limit during today rather than sometime over the weekend. That way there will be people at Twitter able to react to support issues that might arise. As for what developers should do I think it's pretty obvious. If you're using a signed 32-bit integer to store tweet IDs you need to change that ASAP because judgement day is coming!!! -Stuart -- http://stut.net/projects/twitter On Jun 12, 10:23 am, Matt Sanford m...@twitter.com wrote: Hi all, The overflow of the 32-bit signed integer value for status ids (a.k.a The Twitpocalypse [1]) is fast approaching. The current estimate is around tomorrow at around 11am GMT, or 3:00am Pacific time in the case of Twitter. There is some discussion internally about accelerating things so we'll be in the office and able to cope. Nobody is their freshest at 3:00am, not to mention it would be nice to not have apps broken throughout the weekend if one-person developer teams don't notice. No decision has been made yet but I wanted to get something out to you all so you know what's going on in the event we decide to do this. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] -http://www.twitpocalypse.com/ -- Regards, Lakshman becomingguru.com lakshmanprasad.com
[twitter-dev] Re: Twitpocalypse Announcement
Dan, If you're using an unsigned integer, you won't see problems until the 4.2billionth tweet. If you're using a signed integer (which you don't need to, will there ever be NEGATIVE tweets?), you'll see it at the twitpocalypse. Thanks for playing. - Tom On Jun 12, 4:52 pm, Dan Udey d...@cdslash.net wrote: They're bumping it up so that if you're doing something silly (like using an unsigned integer to store the ID), you can find out and fix it. For an automatically incrementing ID, using a signed integer makes no sense, so this is a good chance for shortsighted developers to find and fix their bugs. An overflow will only happen if the developer of a given app has made a careless mistake. All Twitter is doing is triggering the event that will break careless developers' apps on a Friday, instead of breaking careless developers' apps on a Saturday. On Jun 12, 12:08 pm, J. Adam Moore jadammo...@gmail.com wrote: So do I just allocate as many bits as I can in my database to the id field and hope that it doesn't ever run out? I'm confused why you just announced that. Okay, so an overflow is happening. Is that your fault? Is this fixable on your end, my end. Is this just for people who are using 32-bit signed ints to store ids? Decide to do what? Roll it over like an odometer or increase the field size? Forgive me for being an idiot, but 'decide to do this' is just about vague enough to be insulting. I was happily under the assumption that this problem was considered long, long ago when the field size was initially chosen by who I also assumed to be smart people. On Jun 12, 10:23 am, Matt Sanford m...@twitter.com wrote: Hi all, The overflow of the 32-bit signed integer value for status ids (a.k.a The Twitpocalypse [1]) is fast approaching. The current estimate is around tomorrow at around 11am GMT, or 3:00am Pacific time in the case of Twitter. There is some discussion internally about accelerating things so we'll be in the office and able to cope. Nobody is their freshest at 3:00am, not to mention it would be nice to not have apps broken throughout the weekend if one-person developer teams don't notice. No decision has been made yet but I wanted to get something out to you all so you know what's going on in the event we decide to do this. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] -http://www.twitpocalypse.com/
[twitter-dev] Well done, Twitter
Minimal damage, and the website is still up and running. I think we can call this a situation well-handled.
[twitter-dev] Available Twitter Curl with PHP Functions
Hello, Can anyone tell me the available twitter curl with php functions. Any sort of document will do...
[twitter-dev] Twitpocalypse II: this time it's unsigned
So how long until status ids reach 4294967296, breaking the apps that were fixed today by changing signed to unsigned? Taking twitter's growth rate into account I think it's less than a year away. --- Jef
[twitter-dev] Re: Twitpocalypse II: this time it's unsigned
So how long until status ids reach 4294967296, breaking the apps that were fixed today by changing signed to unsigned? Taking twitter's growth rate into account I think it's less than a year away. I'll bet the Twoffice has a pool running on this RIGHT NOW. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Never say never again. -
[twitter-dev] Re: OAuth 1.0a changes and PIN-based authentication shipped
Hi Doug, After reading your post I passed the oauth_callback parameter when requesting a token but I keep getting 'Failed to validate oauth signature and token'. It works as soon as I take out the callback parameter. I am using .NET and here is my GET request please advise if I am missing something, I am fairly new to this. http://twitter.com/oauth/request_token?oauth_callback=http://www.g-softsolutions.com/twittvine.aspx/filerid/1oauth_consumer_key=qBDgyqMk8pnbpW6SdrEwoauth_nonce=945410oauth_signature_method=HMAC-SHA1oauth_timestamp=1244916785oauth_version=1.0oauth_signature=pqy70Jq1ayEfDYnIgThUpJM8zwc%3d thanks, Nizar On Jun 9, 6:23 pm, Doug Williams d...@twitter.com wrote: Today we deployed code that implemented the changes that accompanied the update to the 1.0a OAuth specification. LuckyCal has a great article on the subtle differences that come with the update [1] so please peruse this article if you are getting 401 errors with your implementation. Callbacks for non-desktop apps are now supported with these rules: - When making the call to request_token [4] (server-to-server), you can pass oauth_callback=[url here] - The response from request_token will contain oauth_callback_confirmed=true to confirm we received it. - The user will be sent to twitter.com as usual - When the user is finished they will be redirected to the URL provided in the first step along with a new parameter, oauth_verifier [1] - The call to access_token [5] to exchange the request token for an access token MUST contain the oauth_verifier parameter as sent in the redirect. - If you want to use your pre-configured callback, then do not include a oauth_callback parameter. - If you want to force the PIN-based solution, send oauth_callback=oob with your request to oauth/authenticate Additionally, as a couple developers have already noticed, we deployed the code that implemented PINs for desktop apps originally mentioned by Matt. Please review the linked documentation [2] and discussion [5] and let us know what questions you have. If you find that your browser-based OAuth application is returning a PIN as if it were a desktop app, then remove the oauth_callback=oob parameter from your signature, if it exists. 1.http://blog.luckycal.com/?p=121 2.http://apiwiki.twitter.com/Authentication 3.http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-request_t... 4.http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-access_token 5.http://groups.google.com/group/twitter-development-talk/browse_frm/th... Thanks, Doug
[twitter-dev] Notifications property of users
What is the type of the notifications property on users? Sometimes I get null, leading me to think it oughta be a string, though I've seen false come back too. It's confusing the hell out of my JSON deserialization, especially because I'm working in a statically typed language (C#). Is it a tri-state boolean (true, false, null), or is it a string that sometimes might read false?
[twitter-dev] Re: Messaging users who have authorized my app via oauth
Nothing provided specifically for applications. You could do @-replies like you mentioned. Also if you have write access for them you can follow an app notifications account that you created and send them DMs. Of course for this you should notify them before they authorize that you will add the account to their friends list. Abraham On Fri, Jun 12, 2009 at 18:13, chachra sumit.chac...@gmail.com wrote: Hi, Are any special api calls available to an app that has been authorized (a connection has been made by the user) via oauth? Am wondering on the lines of a Facebook notification. How do I notify (one way is via an @user public message) securely/privately to that user? To send a direct message that user would have to follow me/my account? Cheers! Sumit -- Abraham Williams | Community | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: oauth problem - whats wrong here? - I always get a 401 error - oauth 1.0a problem?
Am 11.06.2009 um 19:02 schrieb Jochen Kaechelin:
def self.consumer
# The readkey and readsecret below are the values you get during
registration
OAuth::Consumer.new(X, , { :site=http://
twitter.com })
end
def sign_in
@request_token =
UsersController.consumer.get_request_token(:oauth_callback =
http://dev.gissmog.de/callback
)
session[:request_token] = @request_token.token
session[:request_token_secret] = @request_token.secret
redirect_to @request_token.authorize_url
return
end
def callback
@request_token =
OAuth::RequestToken.new(UsersController.consumer,
session[:request_token], session[:request_token_secret])
@access_token = @request_token.get_access_token(:oauth_verifier
= @request_token.params[oauth_verifier])
@response = UsersControllerroller.consumer.request(:get, '/
account/verify_credentials.json', @access_token, { :scheme
= :query_string })
Thanx.
Rails 2.3.2, oauth gem 0.3.5
Hmmm ... Ups ... I think I'am the only one who's not able to handle
the new oauth1.0a mechanism Shit!!!
[twitter-dev] Re: Twitpocalypse Announcement
All Tweetshrap users, please update TwitterStatus object to use long for InReplyToStatusId property. Otherwise you will be getting overflow errors. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of mozTom Sent: Friday, June 12, 2009 11:34 PM To: Twitter Development Talk Subject: [twitter-dev] Re: Twitpocalypse Announcement Dan, If you're using an unsigned integer, you won't see problems until the 4.2billionth tweet. If you're using a signed integer (which you don't need to, will there ever be NEGATIVE tweets?), you'll see it at the twitpocalypse. Thanks for playing. - Tom On Jun 12, 4:52 pm, Dan Udey d...@cdslash.net wrote: They're bumping it up so that if you're doing something silly (like using an unsigned integer to store the ID), you can find out and fix it. For an automatically incrementing ID, using a signed integer makes no sense, so this is a good chance for shortsighted developers to find and fix their bugs. An overflow will only happen if the developer of a given app has made a careless mistake. All Twitter is doing is triggering the event that will break careless developers' apps on a Friday, instead of breaking careless developers' apps on a Saturday. On Jun 12, 12:08 pm, J. Adam Moore jadammo...@gmail.com wrote: So do I just allocate as many bits as I can in my database to the id field and hope that it doesn't ever run out? I'm confused why you just announced that. Okay, so an overflow is happening. Is that your fault? Is this fixable on your end, my end. Is this just for people who are using 32-bit signed ints to store ids? Decide to do what? Roll it over like an odometer or increase the field size? Forgive me for being an idiot, but 'decide to do this' is just about vague enough to be insulting. I was happily under the assumption that this problem was considered long, long ago when the field size was initially chosen by who I also assumed to be smart people. On Jun 12, 10:23 am, Matt Sanford m...@twitter.com wrote: Hi all, The overflow of the 32-bit signed integer value for status ids (a.k.a The Twitpocalypse [1]) is fast approaching. The current estimate is around tomorrow at around 11am GMT, or 3:00am Pacific time in the case of Twitter. There is some discussion internally about accelerating things so we'll be in the office and able to cope. Nobody is their freshest at 3:00am, not to mention it would be nice to not have apps broken throughout the weekend if one-person developer teams don't notice. No decision has been made yet but I wanted to get something out to you all so you know what's going on in the event we decide to do this. Thanks; Matt Sanford / @mzsanford Twitter Dev [1] -http://www.twitpocalypse.com/
[twitter-dev] Re: Twitpocalypse II: this time it's unsigned
am I the only one that left the statud id as a string in my code? I didn't feel the need to convert it. On Jun 13, 1:10 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: So how long until status ids reach 4294967296, breaking the apps that were fixed today by changing signed to unsigned? Taking twitter's growth rate into account I think it's less than a year away. --- Jef
[twitter-dev] Re: OAuth 1.0a changes and PIN-based authentication shipped
I have tried encoding the callback url, I have even tried changing the oauth_verison to 1.0a and I even tried with signature type of PLAIN_TEXT but to no avail. Has anybody done this successfully in .NET. I would really appreciate any help thanks. I am not sure if this is implemented yet on twitter's end??? On Jun 13, 3:31 pm, Abraham Williams 4bra...@gmail.com wrote: Try encoding the callback URL first. For example: oauth_callback=http%3A%2F% 2Fprinter.example.com%2Frequest_token_ready This example is from:http://oauth.googlecode.com/svn/spec/core/1.0a/drafts/3/oauth-core-1_... On Sat, Jun 13, 2009 at 13:19, Nizar niza...@gmail.com wrote: Hi Doug, After reading your post I passed the oauth_callback parameter when requesting a token but I keep getting 'Failed to validate oauth signature and token'. It works as soon as I take out the callback parameter. I am using .NET and here is my GET request please advise if I am missing something, I am fairly new to this. http://twitter.com/oauth/request_token?oauth_callback=http://www.g-so... thanks, Nizar -- Abraham Williams | Community |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: [OT]: Trouble with DM's on Twitter website
On Sat, Jun 13, 2009 at 9:09 PM, Scott Elcombpse...@gmail.com wrote: On Sat, Jun 13, 2009 at 8:21 PM, Scott Elcombpse...@gmail.com wrote: Hi all, Sorry if this comes across as a newbie question. Well guess it was a newbie thing - I didn't realize this was a simple support question; I have not yet come across this information in any documentation. My searches have not been exhaustive, quite obviously. My most sincere apologies for the noise. -- Scott Elcomb http://www.psema4.com/ @psema4
