Currency conversion in autoConvert seems to have stopped working.
It appears that the (free) API that the extension uses to fetch currency rates was removed. This has broken currency conversion.
I’ll try and look for a new (free) currency rates API tomorrow (Monday, 22 January). If one is available, I’ll update the extension with it. If I can’t find one, I may have to remove currency conversion entirely.
I’ll update here on the blog on the progress.
Some users are experiencing a bug where the extension frequently asks them to login to Pocket – usually once a day.
This occurs when you use Google login to connect to Pocket. Logging in via
Google->Pocket->AcceleReader leads to frequent time-outs and re-authorisation requests.
Direct login with Pocket doesn’t cause this problem.
I request everyone to sign-in using your Pocket username and password. If you don’t have one, you can create one here.
Bug in the last update requires re-install
I made a mistake while publishing the last extension update on Friday, 14th Feb 2017.
While moving from the old Dropbox API to the new one, I forgot to update settings in my Dropbox developer account. This meant that the extension suddenly stopped working for some users.
I’m sorry for this blunder!
I have resolved the issue from the back-end. However, for those already affected, the only solution, at the moment, is to remove and reinstall the extension.
It will start working normally again.
This is required only if your Todo.txt extension stopped working after the last update. If the extension in your browser is already working normally, you do not need to re-install. It has already been patched.
Update: The issue is caused by pages that use a technology called
react – it was first developed by Facebook.
Due to the way react works, I’m unable to convert text on parts of web pages that use react. However, on websites which only use react for some parts of the functionality, autoConvert will continue to operate as normal on the rest of it.
Still doesn’t work on Facebook, though 😦
I’ve finally been able to diagnose the source of the problem – the Facebook’s BigPipe pagelets.
While Facebook is still waiting to receive, loading and dynamically populate the pagelet divs, Chrome declares the page loaded, and fires up autoConvert. This results in autoConvert working with nodes that wouldn’t be there when the conversion happens (BigPipe will replace them with actual, delayed content).
When that happens, Chrome/autoConvert/Facebook go in a lockup, and everything hangs.
That’s the issue.
Now to figure out a solution.