Jump to content

Shadoninja

Level 2
  • Posts

    16
  • Joined

  • Last visited

Posts posted by Shadoninja

  1. Syncing before and after you make changes to a note is a workaround. And workarounds are a great way to deal with issues until devs get around to a real fix. If free users were allowed to access a note's history, this wouldn't be such a big issue. If free users were allowed to file bugs, posing on this forum would not be the best thing to do. But right now, people are losing data for a reason that should not be happening. This issue needs attention and the users need to speak out about it the best they can. 

  2. 45 minutes ago, jefito said:

    Expand on this, please?

    When a browser loads up a note, it will also receive an ETag from the server. This ETag will be a hash of some unique information about the note in Evernote's DB. An example of an ETag would be to hash the note's DateUpdated value and the note's ID. Whenever the browser sends an update request to the server, it sends the most-recently-received ETag with it. The server then recalculates the hash on its own and compares the server-sided ETag with the user-provided ETag. This definitively proves that the browser either did or did not have the most up-to-date information at the time of sending an update request.

    For example, if you changed the note on your phone, then hopped back on your computer (which has the tab open to that note from earlier) and tried to edit that note, the server will quickly determine that the browser's update request was out of date. At this point, the devs can do whatever they want: force a refresh of the user's browser, give the user a prompt that asks them if they want to overwrite, etc.

  3. If you edit your notes at work or on your phone then come home to a stale Chrome tab and make another change without thinking, everything earlier in the day will be lost. I came to this forum to bring this up, and noticed another post referencing this same issue has already been gaining traction. I replied to that, but decided a second thread is worth posting. This is not an acceptable behavior from the Evernote API. I can give you a suggestion on how to fix this that I personally implemented on my own REST server if anyone from the Evernote team wants to hear it. Please prioritize this change. 

    • Like 1
×
×
  • Create New...