eric99

assuming that no unsynced notes are on the client 🤔

I did a small test: I extended an enex file with a noteId property. I then imported this note in another evernote notebook. Everything went fine as expected because ENEX is an XML format. XML is designed to be extendable without breaking anything. And they could always provide an additional option in the enex exporter whether to provide the noteId or not (the same as you can already specify which metadata should be exported). <note> <noteId>12345</noteId> <title>test note</title> <created>20230310T213530Z</created> <updated>20230310T213604Z</updated> /<note> Conclusion: it is perfectly possible to extend ENEX with a note Id. This is fully backwards compatible. This is the only extension needed to enable export of note links!

Indeed, why are these fundamental problems still there with a team of hundreds of employees working on just one product for 20 years? Compare this to Joplin or obsidian with a few engineers building the same product...

Yeah, very sad for anyone who uses note links because there is no backup or export provided (apart from the windows legacy html export)

Sure, this github project is a python utility currently designed to help the transition from Evernote to another service, but this code is a very good starting point for your own code. It already does a big part of the job. Do you intend to write it yourself? Maybe, you may join this github project to write an extension for evernote import?

I'm glad you ask because few people on this forum seem to realize that note links are completely lost when moving your ENEX to another account. This is a serious limitation. What's the point of improving the notelink infrastructure as long as the links are lost during export? This was already discussed 10 years ago but nothing changed so far: https://discussion.evernote.com/forums/topic/24557-import-old-notebooks-into-evernote-using-enex-loses-all-note-links/ EN may easily solve this as follows: save the note id in the ENEX file (this is perfectly possible without breaking the format, because ENEX is an XML file (X stands for extendable) when importing into a new account, the note ids in the note links should be substituted by the newly created ones (as you describe) There is one bright spot: the HTML export in the legacy windows client (not the mac) keeps the note links intact by using relative hyperlinks to other notes in the export folders. You may fully navigate to other notes or any note attachment in your exported html database. It behaves as your own private website! Unfortunately, this isn't implemented in any other legacy or V10 HTML export. To further answer your question: Yes, it is possible to write a python or java program using the Evernote API to restore the notelinks in the new account: This may be a good start: https://github.com/msbentley/everlink When I have more time, I'll look at it in more detail Please, let us know how it proceeds

The internal link contains a Universally Unique Identifier. See https://dev.evernote.com/doc/reference/Types.html : "Typedef: Guid Base type: string Most data elements within a user's account (e.g. notebooks, notes, tags, resources, etc.) are internally referred to using a globally unique identifier that is written in a standard string format. For example:"8743428c-ef91-4d05-9e7c-4a2e856e813a"The internal components of the GUID are not given any particular meaning: only the entire string is relevant as a unique identifier" For more details about GUIDs see also: https://en.wikipedia.org/wiki/Universally_unique_identifier

This is what happens on mid range android phones all the time, with delays of 1 minute or more. I'm surprised that it occurs on a S22, one of the most powerful phones on the market. The problem is not so much that syncing itself takes a long time, but that the foreground sync blocks the entire app for minutes until the note is closed. To prevent data loss, you need to keep the app open until the note has been saved. Therefore, the android app can't be used for quick note taking anymore, the very feature that made evernote so succesfull in the begin years. So, before increasing the price of the product, BS should first fix these fundamental race condition bugs in the mobile apps. Why should we pay for a crappy app?

At the other hand, this could have changed Evernote's future 9 years ago. It was a revolutionary idea for a note taking app at that time...

And how long do you have to wait before the note is actually closed when this happens (in the worst case) ?

Evernote intended to do it about 9 years ago and the whole evernote community strongly objected for privacy reasons. So EN buried their plans immediately...

Sure, this is what HTML is all about! But, not according Evernote V10 engineers. I reported this bug 2 years ago, and reminded them several times over the years. I always got the same answer that they are "working diligently" on implementing a basic hyperlink 🙄

Out of curiosity, I asked Bing AI for a summary of the transcript, I must admit I'm surprised! James is a customer of Evernote who is concerned about the price increase of the service. Evernote Support is Renier, who tries to explain the reasons for the price increase and the benefits of the service. James is not satisfied with the explanation and accuses Evernote of being unethical and greedy. Evernote Support does not answer James’ questions about the percentage of the increase and the different rates for different customers.

Hmm, this seems to be summarized by chatGPT: where do you read in the transcript a price increase of 80% or more (apart from your own speculations) ?

They probably confuse US Dollar with your currency, New Zealand Dollar? 10.50 New Zealand Dollar = €6.08 which seems to be the normal price...

Yes, I live in Belgium

No, I still see the same price for my next payment on sept 2023 : € 59,99 (personal)

Yeah, I always wondered how this heavy elephant could compete against these agile competitors with only a couple of employees like joplin (1 developer), obsidian (4)...

The good news is, we already have a lot of glitches for 2 years, so that can only get better 🙂

If you've tested the beta sync system, what's your experience with it?

So, have you ever used it yourself?

Hopefully Bending Spoon developers are more experienced in concurrent programming techniques

What exactly do you mean by "remains in beta"? Was it intended to be released now? I'm sure that concurrent editing is much more challenging than the simple sync we have now, and that is already a disaster.

I know that the mac implementation is poor, but Legacy windows HTML export is perfect: the note links are relative links to the proper html notes in the folder hierarchy and all resources can be navigated from within the notes. It really behaves like your own private website. Also, different from the bloated V10 html, the legacy is very compact and readable. Now, more than 2 years later, V10 developers are still "working diligently" at coding a basic html link. Please electron developers, If you don't know how to do it, have a look in the legacy windows implementation, you can learn a lot about basic web technology... If legacy would be stopped before this is fixed in V10, I'll be forced to quit immediately to safeguard my precious data