Since the old LJ code used 32 bits, and we are using only the first 32 bits (out of 64 bits) i tried to just straight copy the groupmask from the old friends table into the wt_edges table. All the friends (appeared) to be present in their respective groups.
Access (i guess bit 0) was turned on for all of my friends, however the subscribe was not.
Now does subscribe (in the 64 bit version) use bit 61? I would just have the 'subscribe' use bit 30, but then we break the API for any outside clients. Is bit 31 (the reserved bit in 32-bit land) used for anything or was that just set aside for "future expansion" back in the day. If we aren't using bit 31 for anything then I guess I can snag it in the name of the subscribe flag.
However this is going to pose a problem for any sites migrating from 32 -> 64 in the future, but a script to move bit 31 -> 61 would be easy to do globally.
Update for your reading pleasure!
Since the old LJ code used 32 bits, and we are using only the first 32 bits (out of 64 bits) i tried to just straight copy the groupmask from the old friends table into the wt_edges table. All the friends (appeared) to be present in their respective groups.
Access (i guess bit 0) was turned on for all of my friends, however the subscribe was not.
Now does subscribe (in the 64 bit version) use bit 61? I would just have the 'subscribe' use bit 30, but then we break the API for any outside clients. Is bit 31 (the reserved bit in 32-bit land) used for anything or was that just set aside for "future expansion" back in the day. If we aren't using bit 31 for anything then I guess I can snag it in the name of the subscribe flag.
However this is going to pose a problem for any sites migrating from 32 -> 64 in the future, but a script to move bit 31 -> 61 would be easy to do globally.
*sigh*