Jump to content


Level 2
  • Posts

  • Joined

  • Last visited

  • Days Won


idv last won the day on January 29 2018

idv had the most liked content!

About idv

Recent Profile Visitors

1,579 profile views

idv's Achievements



  1. @Nick L. just in case: I managed to confirm that UserStore API calls start to work again if I set one of cookies set by Evernote servers during OAuth procedure: the name of the cookie in my case is web50017PreUserGuid. I guess "web" is prefix here, "50017" is some id specific to each user and/or something else and "PreUserGuid" is a suffix.
  2. Thank you very much! Contacted @EvernoteHelps on Twitter, hope it would actually help.
  3. Since April 24 2020 something has changed in server side Evernote API handling: calls to UserStore (virtually any calls but in particular checkVersion and getUser) started to return with weird error: HTTP status code is 429 which corresponds to "Too many requests" but the error is "OK". This error has ruined two open source Evernote clients on Linux: NixNote2 and Quentier. Both use unofficial C++ implementation of Evernote API, QEverCloud, but it worked fine for several years and then stopped in a single day on which nothing has changed in the library or in the apps. Furthermore, the error also affects people who use official Evernote SDKs according to this stackoverflow question: https://stackoverflow.com/questions/61404638/why-is-there-a-sudden-increase-in-ttransportexception. There's some investigation on the issue here by NixNote2 maintainer: https://github.com/robert7/nixnote2/issues/151#issuecomment-621384522. In particular, it seems that calls to UserStore started to require some cookie in addition to authentication token and that cookie is set during OAuth procedure. I failed to find anything about this in the documentation. One other thing that I noticed is that www.evernote.com suffers from this problem but sandbox.evernote.com doesn't seem to. I know this forum is user supported but I really hope that someone from Evernote backend team could comment on this issue. Is it a bug? Or is it an undocumented new feature? What should Evernote API users change in their apps to continue working with UserStore?
  4. Thanks for the suggestion and the links, I can see that a lot of people want markdown support for Evernote. The hardest part in implementing such support is the conversion between markdown and Evernote's format used to represent notes - ENML. I haven't done the proper research yet but so far it seems only some subset of Evernote's format can be represented in markdown i.e. some notes won't be representable - for example, notes containing references to note attachments within its content (en-media tags). Also notes containing ToDo checkboxes. Alternatively, I could possibly try to somehow extend the markdown format itself to allow at least for some Evernote-specific tags like ToDo checkboxes. I keep markdown support in mind although it is not one of the things which I plan to start doing in the nearest future. If someone would like to jump in and help somehow (for example, by doing the preliminary research of conversion between ENML and markdown), that would be great!
  5. Ok, you get your point then. I can't promise to implement selectable downloaded notebooks in near future but I'll think about how it could be done.
  6. It is best to suggest features directly on GitHub, that makes it more likely these suggestions won't be forgotten. Selectable notebook download does make sense for mobile devices since storage is can indeed be quite limited there. But it's hard for me to believe it's an issue for desktop in 2018.
  7. Quentier is not a new project in the sense of starting from scratch, I've been developing it since mid 2013. I've discussed some connections with Nixnote in this blog post. In short, I don't think I can help improving Nixnote since some of my technical views are very different from what can be found in Nixnote. And besides, it never hurts if the end users have a choice of software solving their tasks.
  8. You might wish to check out another open source alternative that I describe in the neighboring thread. However, note that it's in alpha state now i.e. it's unpolished and too fresh to be considered reliable.
  9. Quentier is a cross-platform (Linux/Windows/Mac) note taking app capable of working as Evernote client. It can also be used for local note taking, without the necessity to even have the Evernote account. Quentier supports such features as: Synchronization of user data (notebooks, notes, tags, saved searches) with Evernote Evernote search syntax can be used for data searching within the local storage Printing of notes and converting them to pdf files Ability to open several notes simultaneously in either tabbed or windowed interface Ability to switch between accounts - both local and Evernote ones Quentier is free software distributed under the terms of GNU GPLv3. A large part of core functionality was delegated to a separate library which is distributed under the terms of GNU LGPLv3. Note that the project is currently in public alpha state and is not yet intended for production usage! Some things might be unpolished while some other things might just randomly break due to some unforeseen circumstances. In order to make the app ready to fulfill the needs of casual users in near future the help of brave people prepared to meet and report bugs and inconveniences is required. So I'm seeking for volunteers willing to take part in testing, bug reporting, developing and co-maintaining this app (as well as its core library). The project has downloads with binaries for all supported platforms (AppImage for Linux) so you can take the binary and tinker with it for a bit. The user documentation is pretty much nonexistent at the moment but there's a brief overview of the app's features which should get you started. Quentier is written in C++/Qt, uses CMake build system, also uses some bits of SQLite, JavaScript and CSS. If you have development skills in these technologies and would like to dive into the project, there's an overview of the app's internals + the detailed guide to building and installing the app's dependencies as well as the guide on building the app's core library and the app itself. There are also some pre-filled issues (ditto for the core library) some of which are marked with "help wanted" and "good first issue" tags - these are intended for new developers coming to the project. In addition to help with testing and development I'd gladly accept and appreciate assistance from someone with good design skills: for one thing, better application icons are needed than what I was able to produce myself. For other things, the overall GUI appearance might need some improvements or their ideas at least. The project has a blog in which I write about various technical and non-technical stuff related to the project in one way or another.
  10. A couple of years ago mgsxx announced the initial release of QEverCloud - the library implementing the Evernote SDK in a Qt-friendly way, using Qt's containers and data types. With QEverCloud you can easily interact with your Evernote account's notes, notebooks, tags and other various info from inside the Qt app using the library. QEverCloud is used by NixNote2, the unofficial Linux Evernote desktop client. About a year ago I took this project over and just recently the 3.0 release has hit the ground. Not much has changed from the functionality POV, my focus was on compatibility and the ease of packaging: the latest version of the library supports both Qt4 and Qt5 branches and within Qt5 it supports the use of either QtWebKit or QtWebEngine for OAuth. I've even created some packages for Linux, for now only for Debian Jessie, Linux Mint 17 and Fedora 24. More packages and packaging recipes for other OS and distros would hopefully follow. Everyone is welcome to try QEverCloud out and provide some feedback - questions, suggestions, problem reports, help with further packaging
  • Create New...