HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
iamadamdev
bypass-paywalls-chrome
HISTORICAL RECORD2018–2024
iamadamdev / bypass-paywalls-chrome · Not publicly available

bypass-paywalls-chrome

Discover this repository through its Hacker News conversations.

160Distinct people
200Mentions
3Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

The source check is incomplete. Verified examples will appear here.

What people are saying

I just use https://github.com/iamadamdev/bypass-paywalls-chrome and it works well for me.

suhaybh used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:01:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year200 dated mentions

Observed mentions: 2018-12-01 14:11:19 UTC to 2024-12-13 15:52:38 UTC.

02040602018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 24 mentions; 1 submissions, 23 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 56 mentions; 3 submissions, 53 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 52 mentions; 0 submissions, 52 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 31 mentions; 3 submissions, 28 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 29 mentions; 0 submissions, 29 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC24123
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC56353
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC52052
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC31328
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC29029
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC734

What Hacker News says

31 sources

Show HN: A userscript that adds archive URLs below the paywalled HN submissions

This userscript adds archive URLs to the metadata section of HN submissions without breaking the immersion. Here are 2 screenshots: https://imgur.com/a/PdUu6oG GreasyFork: https://greasyfork.org/en/scripts/452024-hacker-news-anti-pa... Source code: https://github.com/MostlyEmre/hn-anti-paywall Now let me overexplain. -Why?- I never liked paywalled articles. I understand where they come from, but I don't like where we cross our paths. This is why I don't use major news aggregators anymore. Instead, I spend my "catching-up-with-the-world-time" on Hacker News. However, Hacker News (HN) also has its fair-share of paywalled articles. (Around 11.6% according to my short-lived, half-assed attempt at measuring it. See my super old data https://hpa.emre.ca/ I tell the story below.) -First try- Around a year ago, when I ran the above experiment, my
Read the rest
goal wasn't to run that experiment. It was during my self-teaching & career-changing process, I decided to build a React HN clone. To make it stand-out from the bunch, I added a paywall feature. It would detect paywalled articles and would add an archive URL into the metadata. The issue with archiving is unless someone archived the link before on the {archiving-project} then the link is most likely not archived. So me sending people to those projects meant nothing. It kinda meant something for me from an ideological standpoint but I assume you are not me. This rubbed me the wrong way. I decided to build a backend (See https://github.com/MostlyEmre/HN-Paywall-Archiver) that would scan the links and automatically to detect paywalls close to real-time and submit paywalled ones to archive.is for archival. I used Nodejs, Firebase, and React. I was -still am- really proud because I believed it was doing public good in terms of digital preservation. Only 1 person needed to run this script to benefit everyone. As an extra, I was curious on how many paywalled articles were being shared, by whom, at what time. So I also created some analytics functionality to gather the data. And later created a UI to present it. HN-Paywall-Archiver was great but I stopped running the backend at some point. Because at that point couldn't find a way to continuously run my backend code on some platform for cheap or didn't try hard enough. P.S. Recently I've been thinking of remaking this version with Cloudflare Workers. -Hacker News Paywall Archiver Userscript- After almost a year, I got into userscripts. Super great super awesome concept. People seem to hate javascript unless it is presented as a userscript. So I decided to get my hands dirty to create a simple solution that solves the paywall issue on HN without breaking any hearts. My solution is not perfect as it had to be simple. But here's the rundown. Pros: - Does not beg for attention. - Simple code, simple concept. - Unintentionally, indicates which submissions are paywalled without you interacting with anything. - Not-yet-archived archive links can make you feel like you are contributing to the society after you click on the "archive this URL" button on project page. - Uses HN html defaults, so I hope it plays well with the HN skins/plugins/userscripts you use. Cons: - It doesn't automatically archive the links. - It uses clone of a static list of paywalled websites sourced from a popular Chrome extension. (https://github.com/iamadamdev/bypass-paywalls-chrome/blob/ma...) So changing the paywall list is slow and manual. - No guarantees of archived links actually having the archive readily available for reading. Though there are currently 3 projects added, so it should be enough for most links. So, there you go. I hope you enjoy it. It can break occasionally due to changes in news.ycombinator code, if you let me know on Twitter, I can fix it ASAP. Otherwise you have to wait until I notice that the script is broken, which can take quite a while as I browse HN on mobile.
63 points · Open discussion

Showing the 15 most recent of 31 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.