1. It initially defaults to showing two facing pages per screen, but the selector shows "Read a chapter as a long scrolled page" as selected. "Fit 2 page side by side in window" is the same and is presumably the actual default. Switching back to "long scrolled page" from that does do what you'd expect. This is fullscreen on a 1920x1080 desktop display.
2. I personally dislike side-by-side views - I find them distracting - but at this size the line length for "long scrolled page" is too long for readability. I'd prefer a "long scrolled page but with shorter lines and bigger margins" option, like Firefox's reader view.
Also, do I need to keep the screen open if I want to save my place in my book? It doesn't seem to save my book or my location when I reload the page.
I think we still need far more/better solutions in the open source e-reading space.
Under many circumstances, some I've been in, none of those are an option, and a browser is all you've got.
Do you know a good list of available readers? I still searching for the one which fit for me. This one could be a good candidate after some polish.
a) To save books in some place online like s3 or gdrive etc.
b) Allowing to use the "bookmark" feature across sessions.
My use case is that sometimes I am reading a EPUB and I have it in my tablet, but sometimes I have my computer, and othertimes I have my phone. Currently I have to download it 3 times to read it and remember the bookmark.
How far did you make it with this? S3 is tricky because they don't offer OAuth so the user basically has to generate an IAM user and access keys and paste them into your app. I'm currently exploring solutions to this problem.
What programming language did you use?
What was the harder part?
Which format was the hardest?
How long did it take you?
Made one that usable for daily use. Comments and suggestion welcome.