Liso - Highlight text on any page and turn it into audio.

Hot take here: you are never going to finish your reading list. Not this year. Not ever. And its not because you are lazy (okay, maybe a little; so am I). It is because reading was never the point. The ideas were. Words are just the delivery method for us, and staring at a screen is the slowest, most fragile method we have So I dropped everything to build Liso; now none of us would have to read ever again Highlight anything on the web, an article, a newsletter, a thread, a doc- right-click, and it turns into natural audio in your library in one step. A personal podcast made entirely of the stuff you actually chose to read. My "read later" graveyard of articles, blogs, and posts is now a listening queue I finish on walks, at the gym, doing the dishes. Best part? Close to 0 screen time. The part that gets me in trouble is: I think "read more" is bad advice. "Absorb the ideas you care about, in the format that fits your life" is the real move, and obviously take action on it. For a lot of us, that format is our ears, not our eyes. A few things people always ask: Works on any site with the Chrome extension, or just paste text into the app Offline downloads, resume across devices, Apple-style folders to keep it organized I would genuinely love your most brutal feedback. And I am curious: what is the one thing rotting in your "read later" or "saved for later" pile right now that you know you will never actually open? Drop it below and I will tell you if Liso would have saved you in this. Never read again.

The thing rotting in my saved for later pile is a long technical deep dive on RAG architecture I bookmarked months ago and have opened maybe twice. It is exactly the kind of dense, code heavy writeup that never survives the jump from eyes to ears well, since it leans on diagrams and inline snippets that don't translate to audio. So my honest answer to your own question is Liso probably would not have saved that one specifically, but it would have saved the surrounding context and explanation, which is most of what I actually needed anyway. On the actual product, my real concern is anything code heavy or with tables and diagrams. A lot of what ends up in a reading pile is technical writing, not narrative prose, and text to speech tends to either skip that content awkwardly or read it in a way that makes it meaningless out loud. How does Liso handle a highlighted article that has inline code blocks or a table in the middle of it, does it narrate around them, skip them, or attempt to read them as if they were plain sentences.