Feedback: webpage trying to open/Logs/ sync archived element back to Wallabag

[pajd]

Dear Pascal,

First of all, thank you so much for your last version of Plop-Reader, it is a great improvement IMO. I use it absolutely every day and really enjoy it.

Just a bit of feedback:

• quite often, when reading an article and going to the next page, the pocketbook browser opens without warning and attempts to connect to a link probably contained in the page. It can get quite annoying as the function of ebook is to avoid distraction. Is there a way to prevent this?
• after each sync, a Log appears as a new ebook in my library. Although I understand that this can be useful to solve arising issue, is there a way to prevent these logs from appearing?
• when I archive an entry from Plop-reader, it is not taken into account in my Wallabag instance and all changes from the server overwrite changes made inside Plop-reader.

Thanks again for the wonderful app!

[nicosomb]

Hello @pajd!

when I archive an entry from Plop-reader

When you do this action, is your Pocketbook connected to the internet?

[pajd]

Hello @nicosomb!

No, usually, I download the article and then turn off the Wifi. Do you think that this could be the issue, that the action to archive some items when one is offline is not saved and therefore not applied back to the Wallabag server during the next synchronization?

[nicosomb]

I didn't test yet, but maybe that plop-reader don't store actions to execute them when the pocketbook is connected.

[pajd]

Then it would be an issue as I noticed empirically that even when the Pocketbook is connected, if one does not use the Wifi to sync, it disconnects itself rather quickly.

[pmartin]

Hi @pajd,

Thanks for your feedback! It's really nice to read you like and use this app!

the pocketbook browser opens without warning and attempts to connect to a link probably contained in the page. It can get quite annoying

It's indeed quite annoying, I've noticed this a few times. It's not even a matter of "touch" sending events on the wrong page, as it seems to also happen when using the keys to swicth between pages ;'(

Unfortunately, there is not much I can do about this: I'm using the standard EPUB reader with absolutely no customization, exactly like when one is reading a standard EPUB book -- AFAIK, this problem also happens with standard books, BTW.
I know other users (even users who only read books and do not use this app) have reported this, and hope it'll be fixed in a future firmware version...

Log appears as a new ebook in my library. Although I understand that this can be useful to solve arising issue, is there a way to prevent these logs from appearing?

Currently, there is no option to disable logging, as this app is still in development.
I will add an option to enable logging (having it disabled by default) in some future release.
-> I've just created the following issue, to ensure I won't forget: #93

when I archive an entry from Plop-reader, it is not taken into account in my Wallabag instance

Archiving (or any other action done on the device, like starring) is only sent to the server when a synchronization is done. There is no device <-> server communication done at any other time.

The "archived" status is stored locally on the device. And only sent to the server when you run a synchronization -- there is no automatic / background synchronization, not even for statuses.

Reasoning: using wifi eats up battery quite quickly (which is why the firmware disconnects quickly), so I aim to using wifi as least often as possible (as this is a device I use when I'm in holidays, in the train, at the airport, ... places where I cannot charge the device and don't have wifi anyway).

all changes from the server overwrite changes made inside Plop-reader.

When running a synchronization, entries that have been archived on the device should become archived on the server too.
The synchronization process fetches new entries (and/or new statuses) from the server, and then sends new statuses (for entries updated on the device) to the server.

I'm only syncing my device every once in a while (like once every week or two weeks -- before taking a train when going for a week-end or coming back home, usually) and I've not noticed any trouble with this process recently.
Maybe an idea: are the clock on both you server and device configured properly ?