Your "Read Later" list is a graveyard. It is time to stop hoarding.

"You have a tab open right now that you have been meaning to read for three weeks. You have a "Read Later" folder with 500 links you haven't touched since 2023." - how did you know, are you clairvoyant? ;-)

My first instinct was to click the "Save to reading list" button on this article, but through immense willpower I constrained my index finger from going down, and moved the mouse pointer away from that button ...

For me the point is really that, instead of reading all those "important" articles, I get much more satisfaction (in addition to getting in shape) from going outside on a cycling trip, than spending even more hours than I already do sitting on a chair behind a computer monitor ;-)

Awesome tool! I have to admit I also keep saving things “to read later” and… somehow never get back to them.

And I love that thanks to the example article, immortal fame awaits me now 😂

You’re right — too often we add things to a reading list… and then never actually read them. I’ve taken a similar approach with Wallabag (which overlaps with your app in some ways), processing new entries each week through an LLM that sends me a summary of the content, emerging trends, and actionable levers. But I’m curious — I’m going to try your app; it looks interesting.

My bookmarks include Google Translate, GitHub, casual-effects, and CMU Graphics Lab Motion Capture Database. I don't know if the last two sites will be useful, but it's better to let them remain forgotten in my bookmarks. Perhaps if I hadn't read this article, I wouldn't have even remembered them. Moreover, I had already forgotten where my bookmarks were in Brave, so I had to search on Google how to open bookmarks in Brave (shortcut - Ctrl + Shift + O). Surprisingly, saving bookmarks is easier (ctrl+D) than opening them. I'll bookmark my comment so I don't forget the shortcut, lol.

This is an unhelpful overgeneralization.

​I know that feeling well. Eventually, you just have to declare bankruptcy and hit "mark all as read" to save your sanity. I basically tried to build that "mark all as read" logic directly into the tool so I don't have to feel guilty about the pile anymore.

The fragmentation point someone raised above is huge. Reading lists scattered across Dev.to, Medium, LinkedIn, YouTube Watch Later, podcast queues — it's the same hoarding instinct across every medium, not just articles.

What helped me was flipping the model entirely: instead of saving content to consume "later," I started producing content about the topics I cared about. Writing a newsletter forces you to actually synthesize what you've read. Recording a quick podcast episode about a topic cements it way better than a bookmark ever could.

I've been using giv1.com for this — it handles both newsletters and podcasts in one place, so the workflow is: find something interesting, write or record your take on it, publish. The content you create becomes the "proof" that you actually learned something, and your audience holds you accountable to keep showing up.

The Collector's Fallacy dies the moment you shift from consumer to creator. You stop saving everything because you only need material for what you're actively writing about.

This really resonates. The “digital cemetery” line is painfully accurate — I’ve definitely been guilty of confusing saving with learning. I love the resurfacing + spaced repetition angle. That’s real product thinking, not just another bookmark wrapper. And choosing Supabase + React with a privacy-first flow shows solid architectural judgment.

A couple of practical notes from testing it:

1️⃣ When I click “Continue with Google”, I’m getting:

{
  "code": 400,
  "error_code": "validation_failed",
  "msg": "Unsupported provider: provider is not enabled"
}

This usually means Google isn’t enabled in Supabase → Authentication → Providers, or the OAuth credentials (Client ID / Secret) aren’t configured correctly. Worth double-checking:

• Provider enabled in dashboard
• Redirect URL matches exactly (including protocol + domain)
• NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY are correct in production

2️⃣ Some Supabase flows feel unstable (auth/session persistence + route refresh issues). I’d suggest:

• Log supabase.auth.getSession() on app init to verify hydration
• Ensure persistSession: true in client config
• Check for mismatched environment variables between local and Vercel
• Add proper error boundaries around auth flows so raw JSON errors don’t leak to UI

3️⃣ Also, refreshing on non-/ routes returns the default Vercel 404. You should add a SPA rewrite in vercel.json:

{
  "rewrites": [
    { "source": "/(.*)", "destination": "/" }
  ]
}

Overall though — the core idea is strong. The product philosophy is clear. Tightening auth, routing, and Supabase config will make it feel production-grade instead of prototype-level. You’re close — just needs some hardening.

I've realized my Read Later list is more like a safety net than a helpful tool. It's time for me to either delete the links or actually read them

Your "Collector's Fallacy" frame is useful—but I'd push it further. The problem isn't just that saving feels like learning. It's that queuing feels like committing.

Most people treat their read-later list as a vault for unrealized selves—a mausoleum of intentions. Articles saved in the hope that a future version of them will be wiser, more disciplined, more spacious. I don't operate that way. My list stays small because I don't outsource intention to a queue. If something enters my field, it's because it already belongs to the arc I'm walking.

This isn't productivity. It's governance.

I don't begin a project without a completion boundary. I don't save a link unless I know when I'll read it. I don't treat "later" as an expansion of capacity. My practice: if it matters, it gets a slot. If it doesn't get a slot, it doesn't matter.

This is how I maintain continuity. Not by hoarding potential, but by honoring capacity. Not by collecting inputs, but by curating a lineage I can actually finish. My read-later list isn't a graveyard because nothing enters it without a covenant.