DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 963,274 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Jan Vlnas
Jan Vlnas

Posted on • Updated on • Originally published at jnv.zone

Saying Goodbye to Reading.am

Back in 2012 I have discovered a small social network. Now, after 10 years and over 5700 links posted, it's going away.

What was Reading?

Reading.am (or just Reading) was all about, well, reading stuff on the web:

Share what you're reading. Not what you like. Not what you find interesting. Just what you're reading.

Reading homepage

Whenever I read something on the web, I used a bookmarklet (or extension, or email) to post the link to Reading.

A screenshot of a web page with Reading's overlay  with "yep", "nope", and "share" buttons

Reading overlay on the page

When I liked the article, I hit β€œYep”. When I hated it, I hit β€œNope”. I could also comment on the page or quote the text on the page. The quoting functionality was particularly subtle: if any text in quotes was found on the page, it was highlighted by the extension.

Reading overlay highlighting a quoted text in the comment

Occasionally, I checked links posted by others. All in a simple chronological feed with no ads, no algorithmic recommendations, and no distracting images.

But there was a twist: When I clicked a link, it was automatically posted into my profile. Including the attribution who pointed me there. And vice versa: it was fun to see who was intrigued by my links.

Screenshot with a link read by three people

Reading also provided a Hooks system to share the posted links into other applications, like Slack, Twitter, Pinboard, and elsewhere.

Screenshot with Reading's Hooks page

This functionality inspired users to start dedicated Twitter accounts for posting their activity from Reading. Following this trend, I made my β€œJan is reading” account. Nowadays, I also post my shares from Pocket and claps from Medium there.

I enjoyed that Reading was unlike typical bookmarking sites. To me, a bookmark feels like a commitment: when I bookmark it, will I return in the future? To which folder do I put that bookmark? How will I tag it?

Reading removed the question β€œShould I bookmark it?” Whenever I spent some time reading an article, posting it was a β€œfire and (mostly) forget” operation.

Maybe you experienced that β€œoh yeah, I read about this” feeling, but couldn't find the article you barely remembered. Reading and my automated Twitter account help me to backtrack my readings.

How did the Reading end?

At the beginning of June, Reading's author Greg Leppert sent out an email about the Reading sunset.

I don't think it came as a surprise to the remaining Reading users. There were no new features since 2016 and every so often, the site was unavailable for multiple days.

Despite all of this, Reading didn't end up like most abandoned communities, collecting dust and spam. Even today, a single day before the sunset, there are people posting links, at least in my corner of Reading.

Reading was a single person project and labor of love. I am grateful to Greg for building this small, but invigorating this community, and it was fun to be part of it.

What's next?

For me, Reading embodied the best of the social web, a true spirit of Web 2.0 (without irony). It was built for people, not for advertisers. The interface was utilitarian and minimalistic, with subtle features ought to be discovered by users –
not shoved in their face through a guided tutorial.

Maybe you think: β€œI could build Reading in one weekend!” β€” and I'd believe you. More power to you! Greg even published the source code for Reading. Will you pick up the torch?

As for me, Reading's sunset inspired me to start a summer project to scratch my itch. StayΒ tuned!

Top comments (0)

Take a look at this:

Settings

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. πŸ›