Working web browser available?

[Rainiorainio]

Hello,
I have a Libra H2O (n873) with the "experimental" web browser that can't display pages in complexity beyond a search page, it seems.

I tried koreader though it doesn't appear to have a web browser.

Is there a way to browser the net on this device?

Thank you!

[Sirtel]

Originally Posted by Rainiorainio

Is there a way to browser the net on this device?

Thank you!

In short, no. Even if you managed to install a full browser, processor and RAM are not good enough for decent web browsing. It's meant for reading books.

You might like an Android eink tablet, like Onyx Boox devices. You can use a browser on those.

[issybird]

Originally Posted by Sirtel

In short, no. Even if you managed to install a full browser, processor and RAM are not good enough for decent web browsing. It's meant for reading books.

Not disagreeing, but want to point out that the browser is good enough for finding and downloading public domain and other DRM-free books on the fly.

[Quoth]

Originally Posted by Rainiorainio

Hello,
I have a Libra H2O (n873) with the "experimental" web browser that can't display pages in complexity beyond a search page, it seems.

Clue is in the "experimental".

Originally Posted by Sirtel

In short, no. Even if you managed to install a full browser, processor and RAM are not good enough for decent web browsing. It's meant for reading books.

Yes.

Originally Posted by Sirtel

You might like an Android eink tablet, like Onyx Boox devices. You can use a browser on those.

However it may not work well due to eink. I have an Android eInk and Kobos and Kindles. The Android eink has Chrome and Firefox from the playstore. Pretty poor. I had a supposed "eink optimised" browser and it was worse.

Originally Posted by issybird

Not disagreeing, but want to point out that the browser is good enough for finding and downloading public domain and other DRM-free books on the fly.

It can be, but I never read PD ebooks (or bought ones) direct from web to kobo, though I've tested it.
Most of the PD ones need: space removed from between paragraphs, smarten punctuation, etc. I do that automatically as I add to Calibre.

Many bought ebooks need line-height and white-space removed from CSS. I have that in the default Calibre converion.

So I even convert epub to epub.

I've now about 6,000+ unread PD on my Kobo and over 50 unread bought books, all loaded via Calibre. So no need to use WiFi on the go and the browser to get an extra ebook.

Also I fix any really messed up ebooks in Calibre. So I never need KOReader either (for all its overrides).

I check cover, title, author, subtitle, series, blurb as a minimum when I add a book to Calibre and set the "Collection" to one of a few dozen major genres.

[issybird]

Originally Posted by Quoth

It can be, but I never read PD ebooks (or bought ones) direct from web to kobo,

I’ve done it. Handy when you want to read a book now and you’re away from your computer.

Most of the PD ones need: space removed from between paragraphs, smarten punctuation, etc. I do that automatically as I add to Calibre.

You’re confusing “need” with “preference”. I have never edited an ebook for formatting. I’m not very fussy and if the formatting is so very bad I can’t tolerate it, I read something else. It’s not something I tend to run into anymore, except in rare cases when a PDF has been converted to epub.

I've now about 6,000+ unread PD on my Kobo

See? Now that I find excessive. I don’t want 6,000 books on my Kobo. I want a largish selection of high priority books and it generally runs between 200 and 250 books. Which would be a couple of years’ reading, if I didn’t read anything else. Which I do. So that’s plenty. When I don’t know what I feel like reading, I can scroll through a somewhat limited number of highly appealing books and see what jumps out at me.

I personally don’t see the point of huge backlogs of books that will never be read and I admit I’m a sinner at that, but I’ve mostly reformed. Just makes it harder to find the gems amid the dross and time spent formatting and curating is good reading time wasted.

Yeah, different strokes. All I’m saying is that don’t dismiss out of hand an option for someone else that doesn’t appeal to you, unless there is truly something inherently wrong with it.

[trott3r]

I found browsing on the eink boox fine but that might be due to having ublock origin extension installed along with blokada. Ad blocker.

[Aleron Ives]

Boox devices also have snappy multicore CPUs and faster screen refresh modes. They aren't really comparable to the devices Kobo puts out, since they're full Android tablets.

[Quoth]

Originally Posted by issybird

See? Now that I find excessive. I don’t want 6,000 books on my Kobo. I want a largish selection of high priority books and it generally runs between 200 and 250 books. Which would be a couple of years’ reading, if I didn’t read anything else. Which I do. So that’s plenty. When I don’t know what I feel like reading, I can scroll through a somewhat limited number of highly appealing books and see what jumps out at me.

I regard it as a portable library. That's why I use the Kobo interface and not KOReader. Closest we can get to a Tardis for books.

I'd never read all the the books in a physical library, nor all the books on my Kobo. I think for the kinds of ebooks I have I can store about 18,000 on the Kobo Sage. It doesn't make it any heavier or slower having about 8,000 ebooks (current) than 8 ebooks.
I can search and it uses title, subtitle, author and series. I can browse collections. I can sort by most recent, author, title etc. I can filter by reading, finished or unread.

I probably won't ever read all the paper books I have either, which is maybe about 3,000. I did turn one bedroom into a library after four of the kids left home.

Reading is my main leisure activity. Has been since about age 10.

[w8l]

For searching and reading webpages from the experimental Kobo web browser, FrogFind is a good website for this:
https://frogfind.com

It's a search engine built originally for old computers that converts webpages into text-only pages.