Just installed, working GREAT! Thank you. Now lets do one for the scientific journals.<p>"Supported" sites include :)<p>Foreign Affairs
Newsweek
Reuters
The New York Times
The Washington Post
Barron's
Bloomberg
Business Insider
Forbes
Fortune
Harvard Business Review
The Wall Street Journal
ZeroHedge
Bulletin of the Atomic Scientists
Chemical & Engineering News
Discover Magazine
Interesting Engineering
MIT Technology Review
National Geographic USA
Nautilus
New Scientist
Popular Science
Science
Scientific American
The Scientist
ESPN USA
Sports Illustrated
Medium (custom) domains like (opt-in to custom sites for unlisted)
Better Programming
Towards Data Science
America's Test Kitchen
Axios
Field & Stream
Harper's Magazine
National Review
Outdoor Life
The Atlantic
The Christian Science Monitor
The Intercept
The Daily Beast
The Daily Wire
The Juggernaut
The Nation
The New Atlantis
The New Republic
The New York Review of Books
I appreciate that the author took the initiative to improve upon the original project, yet it's also understandable that the original developer might borrow some of those improvements. After all, that's the essence of open-source—to collaboratively make something better.
Been using the FF version for a long time. If that fails, this bookmarklet works.<p>'javascript:void(open('<a href="https://archive.today/?run=1&url='+encodeURIComponent(document.location)" rel="nofollow noreferrer">https://archive.today/?run=1&url='+encodeURIComponent(docume...</a>))'
It's a good thing you don't have to like someone to use their firefox/chrome extensions because the links in here with their responses are very unlikable.....
What a weird, overly-confrontational message from the fork's author! No need to call someone publishing work for free lazy, ignorant, not the sharpest tool in the shed etc. This is the pointless drama that discourages people from making their code open-source in the first place.<p>Plus, the original repository isn't even licensed <a href="https://github.com/iamadamdev/bypass-paywalls-chrome">https://github.com/iamadamdev/bypass-paywalls-chrome</a> . So magnolia1234 probably forked it illegally after copying the name (although it seems like iamadamdev doesn't mind too much).<p>If there's a basically what amounts to a harassment/spam campaign against iamadamdev on his own repo, no wonder he deletes irrelevant issues to avoid stress.
FWIW I am happy that magnolia1234 forked iamadamdev's repo. I wanted to report that barrons.com is not working with the original repo (<a href="https://github.com/iamadamdev/bypass-paywalls-chrome">https://github.com/iamadamdev/bypass-paywalls-chrome</a>). But I could not. <a href="https://github.com/iamadamdev/bypass-paywalls-chrome/issues/new">https://github.com/iamadamdev/bypass-paywalls-chrome/issues/...</a> was giving the following notice.<p>An owner of this repository has limited the ability to open an issue to users that have contributed to this repository in the past.<p>barrons.com worked out of the box with the new repo (<a href="https://gitlab.com/magnolia1234/bypass-paywalls-chrome-clean" rel="nofollow noreferrer">https://gitlab.com/magnolia1234/bypass-paywalls-chrome-clean</a>).