Liss

I have uninstalled, deleted databases, deleted caches, rebooted computers and devices, reinstalled, and it still does not work. Out of six different options (three web versions, legacy app, new app, and iOS) I have five different versions of the database and nothing I do appears to change any of them. For those of you who appear to think I'm an idiot: Yes, I have submitted a support ticket. Given the holiday, I was (obviously wrongly) hopeful that someone here may have run into this issue and resolved it so that I can resolve it rather than waiting for support to respond. I have worked as a software developer for decades and done technical support in the past, so I'm not exactly fresh off the technology farm. There is clearly something very, very broken.

Actually all IS lost because the none of the above will sync properly to iOS, and they are so inconsistent as to render the entire ecosystem unreliably unusable.

So there appear to be three web clients. The 'classic' one, the 'new classic' one, and the 'new new' one. The classic one has all of the correct notes, organized properly, and matches what I see in my desktop version of Evernote Legacy with the exception that it has one new note (added via web clipper) that will not sync to my desktop. The "new classic" version also has the correct notes and matches the version above. The "new new" one (with the home page) is...a disaster. It has thousands of notes that have been deleted from other version. It has entire notebooks and stacks that should no longer exist. Loading any new notebook just spins for...well, I gave up after an hour or so. If Evernote stores everything in a common database, and each version should be polling that database for content, why does the latest and (cough ahem cough) "greatest" (morbid laugh) version not match anything else? Where is it getting all of this old ***** and (more importantly) how do I make it GO AWAY so that (as I suspect) the "new fancy" Evernote stops choking everything else from syncing properly?

It WASN'T broken, but EN decided to BREAK it. It doesn't "feel good" because it goes against a number of logical user interface conventions, breaks logical workflow habits for a large number of users, and IS NOW BROKEN.