I keep your ideas on mind.

Can someone else tell me about the zoom (with volume keys) while viewing an entry ?

And now a (not so) little word about the dev :

I'm currently rewriting all the code... When i started this project it was my first "no-web" project for many, many years (i remember delphi and powerbuilder in late 90's) and QT was really new for me (it's not the case for python). So i added code step by step, test after test...

And now the way the application is coded is not very good... a big file with 1000+ lines (and some little others). And views management and data operations are mixed together, althought i have a "operation.py" file and the "libgreader.py".

And with this code it will not be easy to add feature... so i am currently splitting each views in is own file, with another for the controller.

I will also work a lot on the operation system to have at least two threads instead of one (one for retrieving content, another to execute action : mark read, star, share) and to manage opposite operations...

"opposite operations ?" With the current operations manager, if a timeout occurs, the operation is moved from the head of the queue, to the tail, and others are running before it. It can cause problems with state changing. If i mark read an entry (by viewing it) and then mark it as unread, i expect the read operation be done before the unread, but with this system, it a timeout occurs for the read operation, the unread one could be done before the read one and finally the item will be marked as read... I have to manage this.

So this is a lot of work to separate all code and rewrite this operation manager, and i sadly will add new features (i have a lot in stock !) only when these tasks will be done...

I hope you understand this (fyi i think it will take me two or three evenings)

PS : and i'll take this opportunity to comment my code