It would be great boon when developing code on an ez install an then deploying to a different install.

The most common dev scenario is currently this:

• during dev content is created in dev db
• override.ini developed during this phase often rely on node/object ids: ok
• when dev is almost good, dev db is copied over into prod one, where editors do insert real content
• after this switch, override.ini developed and tested on the dev server cannot make use of node/content ids, as these are not the same between dev and prod. This means keeping 2 copies of override.ini and very often creating a custom ini file where ids of important nodes (menus and such) are kept
• if content packaging or ezsyndication is used to copy data between dev and prod servers, the remote_id is kept. It would thus be much easier to develop an override.ini based on remote_id

On a more grand scale, I think adding a unique install identifier to the remote id, as if it was a namespace, would be an excellent idea. This would make for a truly unique id for every ez object even in the context of multiple installs/servers