SeaMonkey is changing its app id from the current GUID to the new-style seamonkey@applications.mozilla.org ID for easier handling once it's really used in the application. See the following IRC discussion: <KaiRo> shaver: and if we want to go that way, we should probably do so right now, before people pick up our GUID too much. if it requires too much stuff to change, we probably just should stay with the GUID <shaver> what would you expect to happen with existing extensions, of which I think there are a handful <KaiRo> shaver: well, current (i.e. xpfe-based) extension installation doesn't care about app IDs at all, so there's no harm done there - at least for everything outside of UMO <KaiRo> shaver: as UMO is the only place where our GUID might be really used yet - if it is at all <KaiRo> shaver: so if UMO already has extensions with the SeaMonkey GUID (not Mozilla Suite, which is different) and checks for that one, then we should consider keeping it. if there are none at all (which I suspect is true), we just should switch to seamonkey@application.mozilla.org across the board right now, before any with the GUID are added <mao> KaiRo: flashgot and NoScript use the Seamonkey GUID <mao> KaiRo: but I suspect updating the GUID in the AMO database should suffice (SeaMonkey doesn't qery the update service nor bitches about GUID compatibility, does it?) <KaiRo> mao: no, nothing in SeaMonkey cares about it yet <shaver> yeah, I bet we could do that bug 335268 is about doing so on the SeaMonkey side - I marked it as a dependency, even though it doesn't really block this bug (as long as both bugs get fixed).

umm, let's stop this train for now, we might actually run into more trouble than anticipated if doing this across all SeaMonkey branches. Would UMO support knowing about two different app ids for one base application?

SeaMonkey isn't changing the app ID after all.