int64 for uids and new album/photo id format

Feb 9, 2009 at 9:31 PM
Edited Feb 9, 2009 at 9:34 PM

Currently, uids are int32s in the FDT;  it also looks like some work will need to take place to address a new id format for albums/photos:

With the addition of features like internationalization and Facebook Connect, we have seen a significant increase in user growth and engagement. As a result of this growth, we'll start to issue uids greater than 2^32 in a few months. We wanted to remind developers that uids should be stored using 64-bit integers, as documented at Since all current uids passed to applications are less than 2^32, developers may have inferred a 32-bit uid format. We are making this announcement so that any such developers have time to migrate code and databases before the first 64-bit uid is sent to applications.

At the same time, we wanted to let you know that the format for album ids and photo ids will be changing from 64-bit integers to strings (max: 50 characters). Note that all existing ids will be backwards compatible. This change is to better support the site's current growth.

I don't mind making these changes but I'm guessing the first is straightforward enough not to warrant a contribution and the second is complex enough to warrant further discussion? :)
Feb 16, 2009 at 7:25 PM
Not sure about FDT v1, but in v2 uids are 64bit already:

        // Summary:
        //     User Id
        public long uid { get; set; }