Yes, the proposed solution sounds a lot like working around a shortcoming of the design with a hack (that needs constant connection and, if I didn't miss the pa

Yes, the proposed solution sounds a lot like working around a shortcoming of the design with a hack (that needs constant connection and, if I didn't miss the part, not actually saves the content, just displays a warning. Why not save the content as a 'semi-anonymous' user, together with the user's session cookie and on the next login tell there's some ghost session lurking around and whether it should be kept?