Pictor

As Premium user that stongly relies on the clipping ability of Evernote to store information, images and documents, I cannot risk to discover just after weeks, months or years, that Evernot did not store the information shown in a webpage/article. This creates a consistent damage to my work, and forces me (and any other user) to verify from beginning to end every single page that is being clipped, in order to feel safe that the content is actually being stored. We aren't talking big medias here, but of image format, as we have many since the beginning of the 90's. As (also) a softwar

Am curious what's your new ship? Evernote is a great app, but its lack of real encryption, and some other annoyances, make me look elsewhere.

Is there a solution for this? I can't install Evernote on my working computer, because it indexes everything from my private Evernote account. It's a really common use case. There must be an option to prevent that.

It is not a page problem. Web Clipper on Chrome (over macOS) doesn't clip anything anymore. At all. The clipper popup appears, I can select the content, assign tags, etc. But the Syncing will never start the progress-% bar, nor it will ever succeed at storing anything. "Syncing" will go on forever, till the tab is closed. Checking the `background.html` page of the browser extension I can see that the Javascript failure is: > Message did timeout In the Network tab of the DevTools over the background.html page I cannot see any request failing (404 or others). Eve

Since the sandboxing it is under the "Library/Containers" and "Library/Group Containers" folders, instead of the "Library/Application Support". Logs are in: /Users/<username>/Library/Containers/com.evernote.Evernote/Data/Library/Application Support/com.evernote.Evernote Database is in: /Users/<username>/Library/Group Containers/Q79WDW8YH9.com.evernote.Evernote/CoreNote/accounts/www.evernote.com/ The trick of pressing the Option-key works just if pressing the key before clicking the Help menu. That is non-standard respect to the usual behaviour on macOS.