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

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

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

Create account Log in
official_dulin
official_dulin

Posted on

New Button for dev.to, mark article read.

image

A tampermonkey script for marking article read on dev.to. Use IndexedDB to store your read list in your browser. So make sure your browser supports the IndexedDB feature.

Q:Why I want to write this script?

A: I often read articles on dev.to site, dev.to provides three buttons, namely like, unicorn and readinglist. But I want a button to indicate whether the current article has been read, similar to the read function of mailing lists and RSS.

There are some articles that I don't like, unicorn, and don't want to add them to my readinglist. These articles are not useful to me. I want to know if I had read them, That's why I made this button. Just mark this kind of article as read.

Another reason is https://dev.to/mrdulin/why-are-there-duplicate-subscription-emails-sent-to-me-461n

My mail subscription list will be repeated. Even though the subject of some mails is different, the articles pushed are the same, which makes me very inefficient. With this button, I open the article link and see if it has been read. If it's read, directly command + w to close the browser tab

The article you have not read.

image

The article you marked as read.

image

You can export and save the read list to your local file, GitHub Gist, etc...

Install this script from here: https://greasyfork.org/en/scripts/425384-mark-post-read-on-dev-to

Source code: https://github.com/mrdulin/dl-toolkits/blob/master/scripts/mark-post-read-on-devto.js

Top comments (0)

In defense of the modern web

I expect I'll annoy everyone with this post: the anti-JavaScript crusaders, justly aghast at how much of the stuff we slather onto modern websites; the people arguing the web is a broken platform for interactive applications anyway and we should start over;

React users; the old guard with their artisanal JS and hand authored HTML; and Tom MacWright, someone I've admired from afar since I first became aware of his work on Mapbox many years ago. But I guess that's the price of having opinions.