Third, we need to consider our standard TopazPort policy as well as a customizable embargo policy.  That is something like:

 
For objects with history -
 
We make some modifications to the history table so we can store “unapproved” (and thus unseen) edits. Then we edit as we do now, just marking modifications as unapproved if the user isn’t verified. We would need to store in the object the history id of the last approved change, and pull that up at display time. When a user verifies their account, we mark the appropriate edits as approved and remove the “last approved change” id from the object so it takes the current one as valid. We do this just on objects that the user was the last to modify. History would have to only show the approved edits. We might be able to forgo the “approved” flag by remembering that items in history must all have ids that are smaller than the id of the last approved change.