I agree with mostly everything you've said, except with the the part that implies that if another application (be it Safari or otherwise) deletes my Camino passwords, I'm going to have to just live with it.
Would it be possible for Camino to maintain a backup of all of the passwords it has created, and if they are missing (and not by Camino's doing), prompt the user saying something like "It seems that another application has modified or deleted your Camino Internet Passwords. Would you like to restore them?" It just seems that while having and using a central source for this data is a great idea for many reasons, we're relying on all other applications being well behaved. Having some sort of user friendly way of managing that risk seem like it may be prudent. ~Aric On 10-Mar-08, at 1:51 PM, Stuart Morgan wrote: > > I agree that Safari doesn't do a good job explaining the behavior, but > again, whether or not the behavior itself is defective is a matter of > opinion. Apple is clearly moving to a model where there is a central > repository of certain types of data, and anyone can use or interact > with that store. This is their model for passwords, for calendars, for > todos, for rss subscriptions, for contacts, for cookies, etc. > > I understand your argument, but undermining a primary purpose of the > OS's shared keychain system is not the right answer from our > perspective, any more than it would be the right answer for Camino to > stop using the keychain entirely if some application had a reset > button that deleted *everything* in the keychain (which would be > trivial to write). There are a lot of benefits for users to having > data in shared, interoperable systems, and if every application stops > using those systems as soon as any one application does something > unexpected or undesirable, then the whole model collapses, and users > are locked in to specific applications. > > > The bottom line is that interoperability with the OS system of > password storage (and by extension every application that also does > the right thing) is an explicit feature of Camino, and not one that we > are going to remove just because one client of that shared data > (Safari) has a feature that is not sufficiently explained by that > application. I understand that some people disagree with that position > (heck, some people have asked us to stop using the keychain entirely, > purely on the basis that they don't think we shouldn't share data with > other applications); Camino's built-in password manager may not be the > right password system for those people. > > -Stuart > _______________________________________________ > Camino mailing list > Camino@mozdev.org > https://www.mozdev.org/mailman/listinfo/camino _______________________________________________ Camino mailing list Camino@mozdev.org https://www.mozdev.org/mailman/listinfo/camino
