[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-08-01 Thread Andrew Badera
On Fri, Jul 31, 2009 at 8:15 PM, John Adams wrote: > > > On Jul 31, 2009, at 4:04 PM, Andrew Badera wrote: > > but why not go with 128 bit decimal/floating point precision datatypes to >> begin with, and never have this issue? if anyone says "overhead" I'm gonna >> whack 'em like a popup weasel.

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Vincent Nguyen
@John Adams How do you know it will be ok till 58821? How many new twitter user sign-up each days? I just do a google and 2^64 = *1.84467441 × 1019*I don't know how you calculater which days? We can not know how many news user will register twitter? 2009/8/1 John Adams > > > On Jul 31, 2009, at

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread John Adams
On Jul 31, 2009, at 4:04 PM, Andrew Badera wrote: but why not go with 128 bit decimal/floating point precision datatypes to begin with, and never have this issue? if anyone says "overhead" I'm gonna whack 'em like a popup weasel. in this day and age of CPU cycles and RAM, you might as wel

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Andrew Badera
On Fri, Jul 31, 2009 at 7:07 PM, Abraham Williams <4bra...@gmail.com> wrote: > Srew it. Go with 1024 bit unsigned int! > > Hey, if the common frameworks and languages of the day supported it, sure, why not?

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Nick Arnett
On Fri, Jul 31, 2009 at 3:59 PM, John Adams wrote: > > On Jul 31, 2009, at 3:37 PM, Josh Roesslein wrote: > > Well 64 bit should last for a while. Curious how long it will be until 128 >> bit will be required. >> > > > > Mathematica tells me: > "Fri 24 Sep 58821 22:55:00" Darn it - I was plann

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Abraham Williams
Srew it. Go with 1024 bit unsigned int! Abraham On Fri, Jul 31, 2009 at 18:04, Andrew Badera wrote: > On Fri, Jul 31, 2009 at 6:59 PM, John Adams wrote: > >> >> On Jul 31, 2009, at 3:37 PM, Josh Roesslein wrote: >> >> Well 64 bit should last for a while. Curious how long it will be until >>>

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Andrew Badera
On Fri, Jul 31, 2009 at 6:59 PM, John Adams wrote: > > On Jul 31, 2009, at 3:37 PM, Josh Roesslein wrote: > > Well 64 bit should last for a while. Curious how long it will be until 128 >> bit will be required. >> > > > > Mathematica tells me: > "Fri 24 Sep 58821 22:55:00" > > I think you'll be f

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread John Adams
On Jul 31, 2009, at 3:37 PM, Josh Roesslein wrote: Well 64 bit should last for a while. Curious how long it will be until 128 bit will be required. Mathematica tells me: "Fri 24 Sep 58821 22:55:00" I think you'll be fine for a long time at 64 bit. -john --- John Adams Twitter Operations

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Zac Bowling
Just store everything in strings and give up :-) Zac Bowling On Fri, Jul 31, 2009 at 3:37 PM, Josh Roesslein wrote: > Well 64 bit should last for a while. Curious how long it will be until 128 > bit will be required. >

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Josh Roesslein
Well 64 bit should last for a while. Curious how long it will be until 128 bit will be required.

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Chad Etzel
The first Twitpocalypse involved the tweet ID's moving past the highest 32-bit *signed* integer (which is 2,147,483,647). This time around the tweet ID's will move past the highest 32-bit *un*signed integer (which is 4,294,967,295). Developers should make sure the code they are using to store/ma

[twitter-dev] Re: Twitpocalypse: The Second Coming is on the horizon

2009-07-31 Thread Dean Collins
Huh? I thought this issue was resolved already? My developer for www.MyTwitterButler.com said he solved this problem back in June? Am I missing something? Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googleg