Yeah but its a permanent solution.

On Mar 26, 5:06 pm, Mark McBride <mmcbr...@twitter.com> wrote:
> UUIDs are 128 bit integers.  Moving from 64 to 128 bits is likely far more
> disruptive than the proposed scheme.
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Fri, Mar 26, 2010 at 2:01 PM, Nigel Legg <nigel.l...@gmail.com> wrote:
> > If the since_id api calls will work against this, it might be a solution...
>
> > On 26 March 2010 20:58, Donny V. <don...@gmail.com> wrote:
>
> >> Why don't you just use GUIDs as your id and then just add a timedate
> >> attribute stamp and call it a day.
> >> That would give you a unique id and also give your tweets an order.
>
> >> 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.
>
> >  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.

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.

Reply via email to