Quote:
Originally Posted by varaonaid
Is there anything that will allow reading location to be shared across devices? Whether it's Calibre itself (I read a post last night where David was going work on a new version on the server that allowed reading directly via a browser and there inference was that reading location would be saved), a third party app, out whatever, I don't care. I'm finding there are so many aspects to think through when setting this up it's making my head spin. I don't want to find out that I didn't plan for something that causes incompatibility in the future and kids of work changing direction. I truly appreciably your help and the knowledge that you're sharing with me. It's a huge help and blessing.
|
Syncing reading positions is app dependent. Most apps can do it, but they do it in their own way. For example, Moon+ (which I use) syncs reading positions via Dropbox and possibly other cloud providers.
Kovid (not David) is indeed working on adding a web reader to the new content server. It will be able to store reading positions. I don't *know* that the positions will be by user, but it is hard to imagine that Kovid would do something else. That said, reading using a browser on a phone or a tablet isn't a particularly good idea. It requires connectivity. Performance depends on the cell network speed. It won't be "app like".
FWIW: I run a content server for my family. The server, which is a "Virtual Private Server" (VPS) provided by Linode, runs in a data center in London, serving my immediate family (wife and kids) in three countries on two continents. It uses a dropbox-synced copy of my library so the users see my changes when I make them. I run the calibre content server, started using the command line, behind Apache as described in the calibre docs so that I get per-user login. I use a VPS so that I am not required to keep a computer running at home open to the internet, and so that someone else is responsible for keeping the computer up 24/7. Three family members run CC exclusively, fetching books through it. The fourth sometimes uses an iDevice and accesses the content server directly from whatever app he uses.
FWIW squared: Kovid's new content server implementation will support per-user login. CC already supports the new content server.