Sending a reading list without pasting eight links into a chat
A friend asks for the best things I have read on a topic. I spend forty minutes assembling eight unordered links.
I build Markwise, so I am biased. A Space is a set of links you can make public and send as one URL. The reader does not need an account. I am still unsure whether public or one-to-one is the real job.
I will not invent open counts. Mine mostly says no.
Where do you actually send reading lists today?
Markwise is at markwise.app. Free tier. Chrome extension, web app, iOS.
One-to-one sounds like the right first job when a friend asks for recommendations. The helpful unit is probably not just a link, but “why this one” plus a reading-time cue, so the recipient can decide what to open. I’d watch forwards, saves, or a follow-up question rather than raw opens. If the list starts as an AI-made mini-guide instead of eight URLs, the same one-link handoff applies: https://savekit.net/new?utm_source=indiehackers&utm_medium=community&utm_campaign=daily_share_20260928&utm_content=reading_list_handoff
I’d treat these as two adjacent jobs, but start with one-to-one. When someone asks for recommendations, they need a small answer they can trust, not a public collection they must browse.
Let each link carry one sentence on why it is included plus a reading-time cue, and make the shared page feel like a five-minute brief. The metric I’d watch is whether a recipient returns, forwards it, or creates a list themselves—not opens. Those actions tell you whether a Space is a useful handoff or merely a prettier link dump.
That framing resonates. Starting one-to-one keeps the handoff focused, and the sentence plus time cue makes the list feel intentional. I like the return/forward/create signal too—it feels closer to a useful handoff than an open count.