ReaderSharer Restores Sharing Options For New Google Reader [Chrome]

Once upon a time (aka the early 2010s), Google Reader was where serious internet people did serious internet things:
blaze through hundreds of posts with keyboard shortcuts, star the gems, tag the chaos, andmost importantlyshare
links with a tiny but mighty crew of fellow RSS nerds. Then the “new Google Reader” redesign arrived, the interface
got the minimalist makeover, and the old sharing world basically got Thanos-snapped into “+1 and Google+ only.”

If that sentence made your eye twitch in nostalgic rage, you’re exactly who ReaderSharer was built for.
ReaderSharer is a Chrome extension that (at the time) restored classic Reader-style sharing and social navigation
inside the redesigned Google Readerbringing back familiar pieces like “People you follow,” “Your shared items,”
and the one-click sharing flow that made Reader feel like a private newsroom with friends.

What Changed in the “New Google Reader” (And Why People Freaked Out)

Google’s redesign wasn’t just a fresh coat of paint. It was also a philosophical pivot. The official messaging was
“cleaner, faster, nicer to look at,” plus tighter integration with Google+. Under the hood of that announcement
was the big swap: Reader’s built-in social layer (friending, following, shared items, comments) got retired in favor
of Google+ sharing.

The big trade: “Share” became “+1,” and your audience moved

In practical terms, the old “Like,” “Share,” and “Share with Note” workflow was replaced by a +1 action and a
Google+ sharing flow. For people who used Reader’s internal communitywhere you could follow pseudonymous curators,
browse their shared items, and discover new sourcesthat felt like losing the town square and being told,
“Don’t worry, there’s a mall now.”

It wasn’t just convenienceidentity and safety were part of it

A huge part of Reader’s culture was that it allowed sharing with a degree of separation from real-world identity.
When sharing began routing through Google+a product that strongly emphasized real names at the timesome users felt
forced into a tradeoff between community and privacy. In some regions and communities, that tradeoff was more than
philosophical; it could be consequential.

So What Is ReaderSharer?

ReaderSharer was a Chrome extension designed to restore the missing “classic” sharing experience inside the new
Google Reader interface. Think of it as duct tape, but the nice kindthe silver kind that makes you feel like a
capable adult instead of a person who is absolutely going to break something in the next five minutes.

The extension’s core promise was simple: bring back the sharing surface area Google removed, and make the redesigned
interface feel more like the Reader people had built habits around. That included both navigation (where your social
feeds lived) and interaction (the buttons that made sharing quick and frictionless).

What ReaderSharer brought back

• Your shared ecosystem: “People you follow” and “Your shared items” links added back to the left navigation.
• Classic sharing controls: Share buttons restored on each item so sharing didn’t require detouring through Google+.
• Social breadcrumbs: Visible indicators of whether an item had already been shared.
• Better readability: A return toward classic densityless whitespace, friendlier fonts, easier scanning.
• Extras that felt like home: Options like email, keep unread, tagging, and a more complete “item footer” experience.

The “aha” moment: the share feature wasn’t truly dead

One of the most interesting parts of the ReaderSharer story is that it didn’t resurrect sharing from scratch.
It leveraged the reality that Google’s redesign removed the sharing UI, but the underlying capability still existed
in some formmeaning the feature was hidden, not fully gutted. ReaderSharer essentially re-exposed what was still
available, at least for as long as Google kept those backend pieces intact.

How ReaderSharer Worked (Without Magic, Just Product Reality)

If you’ve ever watched a company “remove” a feature, you know the dirty secret: sometimes the feature isn’t removed,
it’s just moved, buried, or deprecated in a way that makes it feel gone to users. That’s what made ReaderSharer possible.
The new Reader experience nudged people toward +1 and Google+ sharing, but the old sharing behavior had enough remaining
scaffolding for a browser extension to hook into.

This is why ReaderSharer felt so satisfying: it didn’t just add a buttonit restored a habit. Sharing in Reader used to be
a one-click reflex. Without it, the act became a multi-step chore. ReaderSharer tried to put sharing back where it belonged:
right under the thing you just read, when your brain is still yelling, “SEND THIS TO MY PEOPLE!”

Installing ReaderSharer in Chrome (Plus the “Don’t Be Weird” Checklist)

Back when ReaderSharer was actively circulating, installing it was straightforward: find it in the Chrome extension ecosystem,
install, refresh Google Reader, and you’d see the restored navigation links and item-level buttons.

Quick safety sanity-check (still relevant for any extension)

1. Review permissions: If an extension needs access to every site you visit “just because,” pause and investigate.
2. Check reputation signals: Reviews, update history, and whether the extension has a clear purpose and documentation.
3. Use the least powerful tool that works: If a stylesheet tweak solves your problem, you may not need a full-feature extension.
4. Remember the lifespan problem: Extensions that depend on specific site internals can break when the site updates.

ReaderSharer was deeply tied to a specific era of Google Reader’s interface and underlying behavior. That’s both why it worked
and why tools like it are always a little fragile: the moment the platform owners truly remove the backend endpoints, the party’s over.

How to Use ReaderSharer Like a Pro (Not Like a Link Cannon)

The best thing about classic Reader sharing wasn’t “posting.” It was curation. Reader wasn’t trying to be your megaphone.
It was trying to be your filterand ReaderSharer helped restore that vibe.

Workflow 1: The “Tiny Editorial Board”

You and a few friends follow each other, and you share items with notes that explain why the link matters. The note is the secret sauce:
“Read this,” is fine. “Read this because it contradicts yesterday’s claim and the data table is wild,” is how you build trust and context.

Workflow 2: The “Personal Knowledge Archive”

Many people used “Shared Items” like a lightweight bookmarking system, but with better recall because it was tied to their reading flow.
ReaderSharer’s restored buttons made it easy to build a timeline of what you found importantwithout switching tools mid-scroll.

Workflow 3: The “Save for Later That Actually Happens”

Classic Reader habits were built around speed: mark as read, keep unread, star, tag. If you’re scanning during a break,
“Keep unread” is basically you telling Future You, “I promise this is not a lie.” Putting these controls back in your face
helps you build a real follow-through loop.

The Backlash Context: Why a Chrome Extension Became a Big Deal

ReaderSharer didn’t become interesting because it was technically complex. It became interesting because it arrived at a moment when
users felt like a product they depended on had been redesigned for someone else. Heavy Reader users didn’t just lose buttons;
they lost an internal social graph, a discovery engine powered by people, and an identity model that didn’t always demand “real name, please.”

That’s why “Sharebros” became a thing, why petitions popped up, and why people started building replacements. The reader community wasn’t
huge, but it was intensemade up of power users who spent serious time in the product and used it as a daily information operating system.
When those users revolt, they do it with spreadsheets, scripts, and browser extensions. It’s adorable and terrifying.

The Google+ gravity well

The redesign moment also captured a broader web-era tension: RSS was open-web infrastructure, while big social platforms were walled gardens.
Moving sharing out of Reader and into Google+ felt like pushing an open-web habit into a proprietary social feed. For people who used Reader
specifically to avoid algorithmic feeds and platform incentives, that felt like being asked to drink water… out of a soda machine.

Troubleshooting: When “Restored” Isn’t “Perfect”

Even in its heyday, tools like ReaderSharer lived on shifting ground. Google could tweak the interface or underlying behavior and suddenly
features would glitch. If something felt off, common culprits were:

• UI conflicts: Google’s own interface updates overriding the extension’s injected elements.
• Broken item actions: Share/like hooks changing, causing buttons to appear but not execute reliably.
• Unread/read weirdness: Reader’s checkbox and “mark as unread” behaviors sometimes behaving inconsistently across views.

The bigger lesson: when a product owner is actively steering users away from a workflow, third-party tools can restore it temporarily,
but they can’t guarantee it indefinitely. ReaderSharer was a bridge, not a forever-home.

Why This Still Matters (Even If You’re Not Using Google Reader Anymore)

ReaderSharer is basically a fossil from a pivotal moment in how we consume information online. It represents a philosophy:
people want control over what they read, how they organize it, and how they share itwithout being forced into a single social network’s
identity rules or engagement mechanics.

Modern feeds are often optimized for retention, not comprehension. RSS readers (and Reader-style tools) are optimized for intentionality.
The mini-drama around Google Reader’s social features and the DIY solutions that followed are reminders that “a feed” is not just a list of links.
It’s a workflowand workflows are personal. Break them, and people will either leave or start coding.

Final Take

ReaderSharer was the kind of tool that only shows up when users care enough to fight for a workflow. It wasn’t trying to reinvent news.
It was trying to restore a simple, powerful behavior: read something great, add a thought, and share it with the right peoplequickly,
quietly, and without turning your reading life into a Google+ recruiting event.

In the history of the open web, ReaderSharer is a footnote. But it’s a meaningful onebecause it proves that when platforms move on,
users don’t always follow. Sometimes they patch.

Experiences From the ReaderSharer Era (500+ Words of “Yep, I Remember That”)

If you were a heavy Google Reader user when the redesign landed, you probably remember the exact emotional sequence. First: confusion.
“Where did my buttons go?” Second: bargaining. “Okay, maybe +1 is basically the same thing.” Third: rage, usually triggered by the moment
you realized you couldn’t casually browse your friends’ shared items anymorebecause that wasn’t just content, it was your people.

A typical Reader morning used to be beautifully mechanical. Coffee. Open Reader. Hit “J” like it owed you money. Scan headlines.
Expand the few that looked promising. Star the one you’ll reference later in an argument. Tag the long read you swear you’ll finish.
Then share the gemthe one link that made you sit up straighterbecause your tiny circle would appreciate it, and because the note you added
(“This paragraph is a masterclass in being politely furious”) was half the fun.

After the redesign, that same morning routine felt like walking into your favorite diner and finding the menu replaced by a sign that says,
“We now only serve smoothies, and you must call your smoothie a ‘+1.’” Sure, you could still eat. But the place didn’t feel like it was built
for you anymore. Sharing became performative instead of practical. The act of curating for a small, specific group became tangled up in a broader
social network identity and audience model. Suddenly, the question wasn’t “Is this worth sharing?” It was “Do I want this tied to my profile,
my circles, my name, my everything?”

That’s why ReaderSharer felt like relief. Not because it was flashy, but because it restored the low-friction moment that made Reader special:
the instant you finished reading, before the feeling faded, you could share and move on. You didn’t have to context-switch into a different
product’s logic. You didn’t have to transform your link into a “post.” You didn’t have to choose between your reading flow and your social graph.
You just did the thing you’d always donenow with a quiet sense of victory, like you’d found a secret door back into the old building.

It also brought back a certain kind of internet intimacy that’s harder to find now. Reader sharing wasn’t about dunking on strangers or chasing
likes. It was about, “Hey, you specifically will care about this.” The smallness was the point. Your shared items were like a running
correspondence: a trail of ideas and links that said, “This is what my mind has been chewing on lately.” When you could browse “People you follow”
again, it wasn’t just a feedit was a relationship map.

And yes, there was drama. There were petitions and protest vibes and hashtags that were both earnest and hilariously nerdy. But underneath the jokes
was a serious truth: the tools we use to read shape what we notice, what we remember, and what we pass along. When ReaderSharer restored those sharing
options, it wasn’t resurrecting a button. It was resurrecting a way of paying attention.

If you weren’t there, it might sound like an overreaction. If you were, you know: it was never “just RSS.” It was how you organized the internet.
And for a little while, ReaderSharer let you keep doing it your way.