This filtering is dubious and should not be necessary - if settings come through as "userSettings" which happen to agree with those in the default model, they should indeed be written into the storage. Correspondingly, no settings should appear here which have NOT come from the user. The "exact equality test" is also dubious and commits us to an architecture where each setting consists of a primitive value.