Like, if I want to refer to a particular chapter, or chat about something or highlight, etc. then it'd make sense to do it in Highlighter.
But to just sit down and read a book, on the beach, I'd want something really plain for my eReader.
That's why I like the idea of not-converting.
Keeping it in notes lets you context-switch.
Like, if you had a zettel in a book with a data table from a different article, you could click on that and go to that article. You could even have an option (also load sources), and then navigate everything offline.
Whereas, conversion would change the link to http and force you off your local cache or relay and back onto the Internet.
You could do that with a long Wiki page, too. Click *read later with sources* and it downloads it and everything one layer back.
It's just event-caching.
@liminal what do you think?
Simple, black and white UI and event caching?
I can research how e-readers handle web browsing.
Yeah was curious about this. Like is it a design constraint or something we explicitely build. Guess ereader performance would decide on that.
I'm not sure that e-readers even have web browsers, typically, and I think their software tends to be pretty closed.
We could develop a simple UI for indextr that lends itself nicely to monochromatic reader views like some browsers have, but I'm not sure if e-readers would ever see it.
My Tolino has a web browser in it. Need it to log into the library website.
Can use it to look at other pages, too. 🤷♀️
Here's the newer Kindle. My Kindle also has a browser.
https://youtu.be/j1ESYDWh5mA?feature=shared
I'm pretty sure Onyx Boox runs straight Android. The Supernote /may/ also be on Android, i know their future releases intend to dual boot linux.
The Fiatjaf example was on a ReMarkable.
do you have a link to that?
note18ye2gvga0tu7nmzqmq5jncnlvpcq32lqpsv2glmpd4uq6thmgeuqm26qu6
Oddbean new post about login | logout