The Open Book Project
github.com
github.com
At the moment, KOReader[1] runs on Kindle, Kobo, PocketBook, and many other e-readers – and is completely open-source.
I still use it over the default kobo software, but I really wish it was better.
This looks like a great alternative, I've installed it and am excited to get a chance to try it out.
Since I bought a reasonably open Kobo recently, I feel the main pain point with eRaeders though is actually getting something to read on them. A dozen stores with DRM exist and the few sites without DRM naturally have limited selection. Also reading pdfs is really not great, yet converting them seems also unreasonably hard. So the problems seems not to be the hardware only, but the whole stack from hardware over software to content.
Still, an open eink device could be fun and can certainly be used for more than just reading books.
Pretty sure Calibre gives you the ability to convert to open formats.
I don't think that will change unless we, as consumers, decide to reject DRM.
With that said, we failed with pretty much every other DRM format, the notable exception being iTunes audio, where Apple had enough market presence to be able to say No. Kobo doesn't, and it is extremely unlikely that Amazon would die on that hill, given that the Kindle doesn't even support open formats at the moment.
If you read English, and to some degree other languages as well, you can find books in the same place you find pirated movies (actually in more places since the file size is small)
As a bonus I can use the app KyBook 3 for ePub files and adjust margins and so on to make better use of the screen space. My Kindle Paperwhite doesn’t display any more text per page than a phone.
Obviously an iPad Mini has drawbacks compared with an ereader in terms of battery, weight, and ability to read in sunlight. The ideal device for me is probably one of those 8” Android eink devices.
Two more points—you can process PDFs for a Kindle pretty well with the k2pdfopt program. Closed-source and conmand line, but it works.
Also popsockets on the back of small tablets and readers are great.
Making a custom kernel/distribution for existing devices would be a better way to go. The Open Inkpot project tried this years ago, but never really got anywhere.
It's low-hanging fruit though: compared to what projects like lineageOS are doing, this is very doable.
And if this Open Book project ever gets usable hardware out, they'll still have to take on the software side.
Really off topic and a little bit self serving to mention this: as an author, I stopped publishing physical books because I like to be able to easily update material and my eBooks are released under a Creative Commons license in three file formats with no DRM. I encourage my readers to share my books.
https://goodereader.com/blog/reviews/onyx-boox-max3-review
Quite pricey though.
In what sense are they not? My first thought when hearing the word "book" is of a particular template of contents and layout that could be instantiated on paper or on a digital device; I guess I'm thinking of something like an ISBN, rather than a specific physical artifact. And that's pretty much the same concept that comes to mind when I hear "ebook".
What is the difference that you're thinking of?
EDIT: in other words, I suppose that my concept of a book is based on the usual interpretation of the question "Have you read that book?"
But, ebook readers are cheap and easy to use (if bought used), even kindle's amazon. Since you have a kindle e-mail address you can just use an app to convert every non-kindle-format file into a compliant one, that's it if you don't want to use Calibre via USB or WebServer. I use eBooker on my Android phone.
Though to be honest I much prefer my 12” ipad pro with high refresh rate for reading papers.
Converting pdf files to epubs is unreliable and often just produces garbage. Calibre may be open source but it seems to be controlled by just one person. pdf2html seemed to be making some nice progress but now seems to be not maintained any more.
In a perfect world we'd have completely open, maintained and well-known conversion software and reader software. There doesn't seem to be a Linux or Firefox in this category.
a few people have got it running on the kobo but the install process seems a bit tricky. there's also the option of using an android based eink and then maybe sideloading the syncthing apk.
the other thing I like about this idea is that i could continue reading a book on my phone or computer if I was really stuck, or if I forgot to charge my ereader... which I do quite a lot
I've been involved with eBooks for over 15 years. It began when my then employer decided all IT staff members should have PDAs. A Handspring Visor Deluxe running Palm OS 3.1 appeared on my desk. I started looking for stuff that would assist in my work as a Sysadmin.
An early discovery was Plucker - a desktop program and Palm client. Plucker was designed to spider websites, and convert what it grabbed into something that could be viewed on the Palm device. A good deal of the documentation for stuff I dealt with was in HTML, and Plucker desktop could convert locally stored HTML files to versions viewable on the PDA. I could carry a documentation library in my pocket.
It was a hop, skip, and jump to realizing I could read other things as well, and a good bit of Project Gutenberg and other things issued under licenses that permitted it joined the party. (I still have about 4K converted Plucker documents in a 7Z archive.)
While I still have a working PDA, the next step was a 7" Android tablet. A variety of eBook viewers for Android existed. My choice was the open source FBReader for Android. I had previously used a version of FBReader written in C under Windows and Linux. FBReader for Android was a Java port, but worked pretty much the same was. The win for FBReader was multiple format support. I prefer ePub, but FBReader can display Mobi, FB2, and a few other things native, and display PDFs, DjVu files, and CBR/CBZ files using plugins. Effectively, I didn't have to care what format a book was in. On the old PDA, I could read a variety of formats too, but each had a dedicated viewer app, and I had to remember which book was in which format displayed by what program. FBReader on Android was a breath of fresh air.
I do not use eInk devices. I understand the advantages - they are battery friendly, and viewable out of doors. But too much of the content I read requires color support. A color LCD screen is a requirement.
I also need a device that can do other things besides display eBooks. There are limits to what I want to carry around when traveling. I already take a laptop and a cell phone. A device that displays eBooks, but can do other things in a pinch like check email, Look Stuff Up, or display MS Office files is a major plus. (I do not use a phone for that. The stuff I tend to view needs a larger screen size than a practical phone can have.)
And while I prefer open source, I am not wedded to it. I will cheerfully pay for closed source software if there isn't an open source offering that does whatever I require, or there is, but the closed source version is simply better. (And a major part of "better" is UX. Open source software tends to have less than optimal user interfaces. The folks who wrote the programs wrote good code for performing the function, but are not UX designers.) I feel the same about open source hardware.
This is a worthy effort, and I wish it all success, but I think it appeals to a rather small niche market. Amazon, Kobo, and the like are not exactly threatened. ______ Dennis