Why Your X Bookmarks Are a Graveyard — and Why That’s a Creator Problem
If you manage social accounts, you live inside the save-for-later loop. You see a thread breaking down the latest TikTok algorithm change, you bookmark it. A growth marketer shares a post-mortem of a viral campaign, you bookmark it. A fellow creator explains how they repurpose long-form YouTube into 14 short-form clips, you bookmark it. The act of saving feels like doing the work. But the reading never happens. The bookmarks tab becomes a landfill of unread potential — a graveyard of insights that could have informed your next video script, your next newsletter, or your next content calendar pivot.
I’ve been there. I’ve run multiple brand accounts and my personal feed is a firehose of valuable threads. The default X bookmarks interface is borderline useless for actual consumption: no search, no prioritization, no way to surface the thing you saved last week when you were trying to remember that one stat about engagement rates. It’s a bucket, not a system.
Enter Totem — a free Chrome extension built by Ankit Sinha that turns your X bookmarks into a clean, article-style reading experience. On the surface, it’s a simple idea: unroll threads, let you highlight and annotate, export to Obsidian or Markdown, and serve you a daily queue of five bookmarks so you actually read them. But underneath, there’s a clever technical choice that makes this sustainable for a free tool, and a design philosophy that treats your saved content with the dignity it deserves.
For creators and social media operators who live on X for research, trend spotting, and community management, Totem isn’t just another read-later app. It’s a workflow correction. Let me walk through why this matters, how it stacks up against the existing options, and where I think it still falls short.
The Problem We All Pretend Doesn’t Exist
I’ll be honest: I’ve tried every method to “process” my X bookmarks. I’ve used Pocket to save individual tweet URLs (clunky, loses thread context). I’ve tried Notion web clippers that embed a single tweet (great for archival, terrible for reading a 20-tweet thread). I’ve attempted a manual weekly review where I open each bookmark tab and copy-paste into a doc (I lasted two weeks). The core issue isn’t storage — it’s friction. The default X bookmarks interface is built for scrolling, not reading. There’s no full-width text, no ability to highlight, no way to search by keyword unless you remember the exact tweet text, and absolutely no reminder to return to what you saved.
For a creator who uses X as a primary research feed — which is most of us in the social media space — this friction translates directly to missed opportunities. That thread about how Later handles Instagram Reels scheduling? You saved it, but you never read it, so you keep guessing your posting times. That case study on Buffer’s organic growth strategy? Buried beneath thirty memes you also bookmarked at 2 a.m.
I’ve seen this pattern in every social media organization I’ve worked with. Community managers save launch announcements and ecosystem updates. Growth marketers save algorithm analyses. Creators save storytelling frameworks. And then the firehose of new content washes over it all. The saving is the dopamine hit; the reading is the delayed work that never arrives.
Totem’s tagline — “Read, don’t scroll” — is exactly the right framing. It positions the tool not as a bookmark manager, but as a reading environment. That shift in mental model is what makes it worth examining.
What Totem Actually Does (and Doesn’t)
Let’s get the feature tour out of the way, but I’ll frame it through the lens of a social media operator’s daily tasks.
Unrolls threads into clean articles. When you open a bookmark via Totem’s new tab page, the entire thread is stitched together into a single, full-width document with proper typography. No infinite feed, no sidebars, no algorithmic distractions. For someone who needs to absorb a 15-tweet analysis of Instagram’s latest algorithm update, this is a massive time-saver. You’re not jumping between tweets, losing context, or fighting the UI.
Highlight and annotate. This is the feature that makes Totem a research tool rather than a pass-through. You can mark lines you want to quote in a future post, or add a note like “use this stat in the next newsletter.” In my experience, the ability to highlight without leaving the reading view is critical for maintaining flow. Readwise Reader does this beautifully for web articles; Totem brings it to threads.
Search everything. The extension indexes your bookmarks and makes them searchable by text. For a creator who remembers “that thread about UTM parameters” but can’t recall who posted it or when, this is gold. The search bar is front and center on the new tab page.
Export to Obsidian or Markdown. This is where Totem gets serious for organized creators. You can export a full thread (including quoted tweets up to one level deep) as a Markdown file with YAML frontmatter that includes the author, handle, saved date, and tags. The maker shows an example in the comments where a thread by Pat Walls about bootstrapping gets exported with headings, blockquotes, and a clean structure. If you use Obsidian for note-taking, you can drop this directly into your vault. For social media teams who run shared knowledge bases in Notion or markdown-based wikis, this export pipeline saves hours of manual formatting.
Daily queue of 5. The default view on the new tab is “Today’s Read” — a curated list of ~5 bookmarks based on recency, partial reads, pinned items, and “old bookmarks gathering dust.” This is the behavioral design piece that most read-later tools get wrong. Pocket gives you a list sorted by date saved; it’s still up to you to choose. Totem says “here are five things we think you should read today.” The maker explains in a comment that the scoring considers “things you started reading, saved recently, pinned, flagged, old bookmarks gathering dust.” That heuristic — especially the “dust” component — is smart. It surfaces content that would otherwise be forgotten.
Technical foundation. The most interesting part of Totem’s design, for anyone who’s built tools around X’s ecosystem, is how it fetches bookmarks. In a comment exchange with a developer who asked about the approach, Ankit explains: “It calls X’s internal web GraphQL endpoint (the same Bookmarks request the site itself makes) by reusing your existing login session. … The one thing that actually moves is the GraphQL query ID, which changes on client bundle deploys. It’s not hard-coded — when it changes, the extension discovers the new one… and retries.” This is important because it means Totem doesn’t scrape the DOM (which would be fragile) and doesn’t require a paid X API tier (which costs thousands per month). It’s a clever hack that keeps the tool free and functional — for now.
How Totem Compares to the Competition
Any operator reading this has likely tried at least two of the following: Readwise Reader, Pocket, Instapaper, or a homegrown system of browser bookmarks. Here’s where Totem fits.
Readwise Reader is the gold standard for serious reading and highlighting across the web. It supports articles, PDFs, newsletters, and even tweets (via a separate integration). But it’s not free ($7.99/month after a trial) and its X integration is not native — you’d need to save individual tweet URLs. Totem is purpose-built for X threads, works entirely through your browser new tab, and is free. It’s not a replacement for Readwise; it’s a specialized tool for a specific input source.
Pocket is free but treats X bookmarks as just another link. You can’t unroll threads natively, and the reading experience for a 20-tweet thread is a single long page with minimal formatting. No highlights, no annotation, no export to Markdown. It’s a bucket, not a reading room.
Browser bookmark folders — which I suspect many creators still use — are even worse. No search, no order, and zero reading friction.
Where Totem shines is in its narrow focus. It doesn’t try to be your whole read-later stack. It says: “You save threads on X. I will make those threads readable, searchable, and exportable, and I will put them in front of you every day.” That constraint is a feature, not a bug.
Why This Matters for Different Types of Creators
### Why X-Centric Creators Should Care More Than LinkedIn Ones
If your primary platform is Instagram or TikTok, you might wonder why you should care about a tool that only works with X bookmarks. Here’s the reality: X remains the beating heart of the creator economy conversation. Algorithm changes are broken there first. Growth tactics are shared in threads before they become blog posts. The people who shape the discourse — Jason Kottke, Lenny Rachitsky, Amanda Natividad — publish there. If you’re a creator on any platform, your research feed is likely X. Totem turns that research feed into something you can actually process.
For community managers who track ecosystem updates, AMA threads, and launch announcements, the export to Obsidian/Notion is a workflow game-changer. Instead of copy-pasting relevant quotes from a 30-tweet thread, you can highlight the key lines, export the whole thing, and link it to your community documentation. One comment on the Product Hunt page mentions using it exactly that way during “launch season.”
For growth marketers who run A/B tests on ad creative or organic hook strategies, Totem’s search feature means you can find that thread about “best times to post on LinkedIn” from three months ago. Without it, that thread is lost to the algorithmic void.
For indie founders who use X as a customer research tool, the daily queue of 5 means you’ll actually read the saved feedback threads instead of just hoarding them.
Where I See Limitations (And Who This Isn’t For)
I’m enthusiastic about Totem’s design, but I have to be transparent about where it falls short — because a tool you can’t rely on is worse than no tool at all.
It’s X-only. The maker confirmed in a comment that there are “no plans yet” to expand beyond X bookmarks. If your primary read-later habit involves saving articles from the web, newsletters, or other social platforms, Totem won’t help. You’ll still need a separate tool for those. That’s fine for a focused tool, but it means Totem solves only one piece of the puzzle.
No summarization. Another comment asked about search and summarise; the maker replied “Search - yes, summarise - no.” For a creator who wants an AI-generated summary of a long thread before deciding whether to read it, Totem offers nothing. Given that many modern read-later tools (e.g., Readwise Reader with AI highlights) are adding this, it’s a gap.
No mobile app. Currently Totem is a Chrome extension that works only in the desktop browser new tab. If you do most of your reading on a phone or tablet, you’re out of luck. The maker hasn’t mentioned mobile plans. Given that many creators scroll X on their phones and bookmark threads there, a mobile reading experience would be critical for long-term adoption.
Dependence on X’s internal endpoint. The clever GraphQL hack is elegant, but it’s not guaranteed to work forever. X (now X Corp under Elon Musk) has a history of breaking third-party tools. The maker explains that the extension discovers new GraphQL query IDs automatically, but that only accounts for one variable. If X changes authentication requirements, rate-limits internal endpoints, or moves to a fully API-only model, Totem could stop working. It’s a free tool, so you’re not paying for it, but you’re also not getting any SLA. If you build a workflow around Totem — say, you rely on the daily queue to plan your content calendar — you need a backup plan.
No collaboration features. For social media teams, sharing bookmarks or highlights across accounts isn’t supported. The export to Markdown is a workaround, but it’s not real-time.
No priority tagging beyond the daily queue. The scoring algorithm picks five items, but you can’t create custom queues (e.g., “show me all bookmarks tagged #community management today”). The search is good, but it’s not a full organization system.
Who it’s not for: Creators who rarely use X. Teams that need a shared read-later tool. Anyone who reads primarily on mobile. Researchers who want AI summarization. And operators who are risk-averse about using a tool that relies on an undocumented internal API.
What I’d Watch / Test Next
If you’re a social media operator reading this, here’s my concrete advice.
1. Install it for a week. It’s a free Chrome extension. Point your new tab page at Totem for seven days. See if the daily queue actually changes your behavior. The real test isn’t “can I read a thread?” — it’s “do I actually want to open my new tab rather than avoid it?” The maker’s design choice to show only 5 reads instead of an overwhelming list is the key behavioral lever. I’d test whether I find myself finishing those five or ignoring them.
2. Test the export pipeline. Highlight three threads from your bookmarks that relate to your content calendar. Export them as Markdown and drop them into your notes system — whether that’s Obsidian, Notion, or a simple folder. Evaluate how much time that saves compared to your current method of copying/pasting. If you’re spending 15 minutes formatting a key thread for a future post, Totem’s export might cut that to 30 seconds.
3. Monitor X’s stability. Use the tool for a month and pay attention to any time it fails to load bookmarks. The maker claims it has “held up really well — hasn’t broken for me at all.” But that’s one user’s experience. As a professional, I’d want to know how often the extension needs to update its GraphQL query ID injection. If it breaks during a busy launch week, you need a fallback. Document your manual bookmark retrieval process as a backup.
4. Consider combining it with a secondary read-later. Keep Pocket or Readwise Reader for non-X content. Use Totem exclusively for X threads. That way, if Totem goes dark, your other reading workflow is unaffected.
5. Advocate for mobile. If Totem proves valuable to you, join the chorus asking for a mobile reading experience. The maker seems open to feedback (“Want to see what it grows into before thinking about what features to add”). The biggest friction for creators is that we save threads on the go but read them on desktop. A mobile companion — even a progressive web app that syncs the same queue — would dramatically increase stickiness.
Totem is a small tool solving a narrow problem, but it’s solving it well. In a landscape where every SaaS tool wants to be your entire operating system, there’s something refreshing about a Chrome extension that just makes X bookmarks readable. For the creators and social media managers who live and die by the threads they save, that might be exactly the quiet reading room they need.
