Possible Duplicate:
please add a key fields to stackauth results

It would be easier if sites each had an ID, it help with keeping track of them, not only in a numerical way (which is generally easier and smaller than using name strings).

Also changes of site names (such as when a site progresses from beta, or decides it's name is not quite right during beta).

Everything else has IDs so why not sites?

Possible Duplicate:
please add a key fields to stackauth results

It would be easier if sites each had an ID, it help with keeping track of them, not only in a numerical way (which is generally easier and smaller than using name strings).

Also changes of site names (such as when a site progresses from beta, or decides it's name is not quite right during beta).

Everything else has IDs so why not sites?

It would be easier if sites each had an ID, it help with keeping track of them, not only in a numerical way (which is generally easier and smaller than using name strings).

Also changes of site names (such as when a site progresses from beta, or decides it's name is not quite right during beta).

Everything else has IDs so why not sites?

Possible Duplicate:
please add a key fields to stackauth results

It would be easier if sites each had an ID, it help with keeping track of them, not only in a numerical way (which is generally easier and smaller than using name strings).

Also changes of site names (such as when a site progresses from beta, or decides it's name is not quite right during beta).

Everything else has IDs so why not sites?