AlbertR

Done. Good idea! @all-others-here: We all should go to Evernote for Windows Requests (Versions 10.0 and above) to collect our needs!

Fortunately I have such a dino captured 😉 There is no explicit 'never' option - but you are able to simply uncheck all modes:

Because that frees up some of their engineers - who are maintaining dual access - to concentrate on other things? No supporter has to maintain Legacy issues. Closing down Legacy does not free any support staff. Next weeks there will be no chance to concentrate on other things. Huh - hard words. But true. 👍

Can you give us some examples from your experience? Sort by Reminder Dates in normal note lists - NOT in Reminder tab that... somtimes causes EN to hang up if it is active and you click on a Favorite often is not available at all Display and sort Reminder Done Times in normal note lists Display normal note lists all the time If you click on a Favorite note, the list goes away (note occupies complete main window except left pane) If you navigate to a note from outside EN, the list goes away (...) updated:day-1 is not reliable: Doesn't show notes updated today But shows notes from many years in the past left pane doesn't support colored tags and notebooks Favorites cannot be placed as a separate line above left and right pane Text, attachments and images cannot be placed in one line together Attachments do no more show their created and updated time

Yep - but a first reason for falling behind is firing core support and dev teams. Struggling against newly upcoming (upset, hysterical, ...) customers might be handled by robots. But request coming from well known, paying for a long time and cooperative users should be handled with some priority. 😤 Why don't they work on queued tickets before fireing new "improvements" like closing Legacy?

You're right - but it was my choice to enhance my workflows with EN's great app and service. Nobody forced me to stop/reinvent my older (not really fancy) workflows. In the past years my hope was (and truely is) that EN10 will continue to bring EN10 to a level, we all are used to use with older versions. Me too - and I'm proud to be one the 1% users 👍 But if they are that acribic with counting our usage preferences, they should know that I'm already on EN10 to figure out it's "advantages" 🤔 IIRC they also stated before some months, that only 2% (or was it 5%? - correct me if I' wrong) of all users use tags. <sarcasm> Is it really worth to care for these few idiots in future? </sarcasm> I hope to get similar counts on API usage. I hope to get similar counts on Tasks. But coming back to today's eMail and Blog post... It's in fact OK - but comes late in that clearness - and with one annoying hint: Back up your notes. Consider backing up all your notes as ENEX files before updating. ... Why? Backing up my notes to EN's task! If I do it locally, I'll lose all my internal links if I ... easily re-upload any content back into Evernote... But OK, it's a Blog post that might be corrected silently the next days 😉.

How many folk should perform an action that is not available?

Sorry, cannot reproduce your problem. It works correct even if I use exactly your text as an example note... EN strips all special characters from text before indexing it to support later searches. When searching, the same is done: All special characters are removed from a search string to enhance search results. If you have "https://www.cettire.com" within you text, you can find "https", "www", "cettire" and "com" only. If you are searching for "https://www.cettire" you search for "https" AND "www" AND "cettire". In both cases, you should find your note with no problem.

Yeah! That's the point that helps us being patiently in good hope... But as long as our workflows keep broken, we'll insist on either Legacy availability or EN10 being able to replace it. Regarding @Net-config's in depth post above: couldn't have said it better. And sorry @PinkElephant - simply calm down with boring tips to forward complaints to feedback channels on an eMail base. We're a user forum to discuss all arguments around EN as a service - not only to answer trivial question around EN10. EN as a service provider should offer a way to keep good paying customers work as usual forEver. (und du weißt, was ich damit meine 😉)

Yep. Just installed EN10.77.3 to check for the news. And yes - I can place two images side be side on a line. But that's all 😞 (*) Attachments occupy a who line (not only a standardized width card to show type, name and changed date) - why? It's impossible to place text beside (before or after) an image - why? An image or attachment-card should be a simple item (like a character) on a line. If you place the cursor just before an type - input should appear just before the attachment. If you place the cursor just behind - input should apprea just behind. I thank that's not that difficult 😤. Every text processing app (including Legacy) work this way... (*) good news around that: They seem to work on it 😉 👍

Sorting numbers within strings is a difficult task. We (as developers of an eCad system) often had requirements to sort strings like =A1+P7.1-K17:a and =A1+P24.2-K4:b. Internally you have to split the string to substrings containing only numbers and only other characters (simplyfied). Resulting table of substrings has to be sorted alphabetical in character columns and numerical in numerical columns. By doing so, 7 comes before 24 . So EN works correct even in this sophisticated area 😉 But this is not true. If EN has to sort strings like "003-test+2" and "03-test+1" it fails: first number 3 is identical. Second string "-test" is identical. Last numbers +2 and +1 should sort as +1..+2. But the notes are listed as 003-test+2 03-test+1 At the end it sorts along its own rules - that are not documented anywhere... Best idea so solve this is to insert leading or trailing "0"s according to your sorting needs.

THX for your in-detail description so far in your Blog. I for myself cannot agree with all your topics (i.e. that EN cannot link notes) and whether it will be somewhat cheaper that EN. 8€/month + Zapier (free?) to implement an eMail-Inbox? I also had some tests with Obsidian and found the learning curve too complicated to recommend it for non-IT-insiders. But your idea to rework all notebooks and thereby delete some note is a good one - I call this work "gardening" my notes 😉

I know (and got many other such in the past). But the last stated "have passed it on to our developers" - which was new 😉

THX for this short timeline. It shows what many here forgot: V10 is not an idea of BS - see also Behind the Scenes: Uniting the Evernote Apps - Behind the Scenes Series - Evernote User Forum from February 2020 - sure after some months of work that have been passed before the video (*) With BS the focus seems to change to fance UI "enhancements". Base idea was great. (*) Interessting: Hasn't been @Shane D. an empolyee in the past? Now he's shown as a Level-5 forum member whereas some other appear as "Ex Employees" (like @Ian Small with his Teams account...

Yep - there where not changes in API with RTE - and that's the problem. 😤 - with all the gone free users it should be possible to widen (or remove) the Rate limit (at least for Professional and Teams accounts 😉) API access cannot be per App because it runs on server site. So "Account" means "User" - supporter is right (or was there a possibility to access the API on clients in former days?) Yep - but the it was a joy to get an answer from a developer (or 3rd level support) 🙂

Either I do not understand your need - or you have not seen Ctrl-F8 or Ctrl-F7 😉

And: Allow us to open notes from outside EN in a new note window - like Legacy had an option: Is the worst choice ever - we loose the important note list - why?

Yeah, me too 👍. I got tree similar eMails on different open ticket within 2 minutes last friday. All stating that my points have been moved to development now. Either they moved support activities to development or development cares for fixes now or ...? 🤔

Oh what a pity... I got an answer from support. Not as I hoped - but a good explanation of the current situation: The rate limit applies to the total number of API requests for a specific user. The limits are typically adequate for common applications, especially if they are optimized to reduce the number of API calls. You can learn more about limits and best practices here. For your particular application, I recommend you stagger your requests across multiple hours. I forwarded this to developers of Make and noted that Filterize didn't have exactly this problem in the past. Maybe this motivates Make's devs to get better 🙏 - or contact EN to re-think their limits...

Whow, interresting 👍. I'll try it sometimes later 😞

Seems like a simple bug that causes the note editing sub-windows within the note editing main-window. Not a big problem... There are other (more important) situations, in that space is wasted: Line height within note lists, before and after tables, space between images (or attachments) and text that should be displayed on one line, ...

Yep - that would be a problem to many, many people (including me). On the other hand the new pricing and streamlined internal organization will help to continue the service in future. Regarding support: I got a sign of life for 3 open ticket last Friday - OK, not the solution (looks like a triggered machine message). But someone decided to give this sign, so he/she believes in beeing able to answer in near future 🙏.

I remain with EN and there's not need to transfer data. I think the price is acceptable for a stable service over many years. Count your time to find a better solution and convert these hours and days to € or $. This money is saved with EN 😉

That's a sure sign of a corrupted local database because tags are stored not directly with the notes. And if only changed notes re-appear, it seems like an internal list of "recent changes" that's mis-interpreted in any way... I hate reinstalling any software to wipe problems the software causes itself - but Revo Uninstaller might help because it surely remove all EN fragments (including the local database).

Since RTE many API users have problems. Filterize gave up (closed now). Make often shows "RTE room open" together with "RATE_LIMIT_REACHED". With IFTTT and Zapier I did only small tests - but with no problem so far. Maybe not tested enough 😉. From my point of view EN should talk to API service providers because they offer things that are not available at EN directly. It may help to widen EN's user base...