I'm guessing the consumer key/secret for the API is given with an expiry date, whether automatic or done after they fail to reach the maintainer to see if they still want access.
Given that Sharky hasn't posted anything on TMO or touched the code in over 2 years, I think it's a safe bet he's moved on. So short of anyone else taking over as maintainer and requesting a new key from Evernote,
The problem as others I think pointed out is that in Nov '12 the Evernote API changed to requires Oauth to authenticate so using username/password from the client will no longer work.
I don't want to get anyone's hopes up but thought I would mention that I have started the process of attempting to add oauth to the code. However it is not trivial and requires upgrading libevernote and thift libraries to the latest versions, then modifying the app code to open the evernote oauth webpage instead of prompting for username/password and ensuring all relevant API calls use the oauth token. Thankfully I can use a Nixnote Qt port for guidance but as Python code is my usual domain compared to Qvernote's C++ it will not be a quick process.
The problem as others I think pointed out is that in Nov '12 the Evernote API changed to requires Oauth to authenticate so using username/password from the client will no longer work.
I don't want to get anyone's hopes up but thought I would mention that I have started the process of attempting to add oauth to the code. However it is not trivial and requires upgrading libevernote and thift libraries to the latest versions, then modifying the app code to open the evernote oauth webpage instead of prompting for username/password and ensuring all relevant API calls use the oauth token. Thankfully I can use a Nixnote Qt port for guidance but as Python code is my usual domain compared to Qvernote's C++ it will not be a quick process.
I hope others would join in.