Show HN: Built an extension to put an end to paywalls and popups
chrome.google.com
chrome.google.com
This implies that you will, at some point, be charging a fee to remove revenue from other sites. Does this not border on unethical business practice?
Or to sell a wide-range solution to a problem, for which previously only peacemeal solutions were available on the market?
I believe these questions are no different from yours, and that all of those are ethical; if the site needs to keep track of some balance that I would have on that site, they should make me create an account before ever showing an article.
Note that I'm not advocating for piracy / circumvention of DRM, but against the 'you have read your 3 free articles this month, please create an account'-pattern. If you offer free articles without an explicit user account, you should not be suprised that the anonymous user expects those articles to be free and uses workarounds to get past the toll gates.
It's an inherently subjective question.
And to everyone who's complaining about 'stealing revenue': buzz off. It's a user agent, not a vendor agent. Screw these popups and nagware and screw your website which uses them.
If you run your own ad platform from first-party code and you audit the process for ad inclusion as well as the code running the network to ensure only static ads from vetted partners, we're good and I won't block. Otherwise, block.
Blame Forbes. https://www.networkworld.com/article/3021113/forbes-malware-...
https://github.com/easylist/easylist/tree/master/fanboy-addo...
https://github.com/AdguardTeam/AdguardFilters/tree/master/An...
This post is not directed at parent, but the general HN reader who might be tempted to try pophurdle. Use uBlock Origin instead. https://github.com/gorhill/uBlock#installation
Disclosure: Mozilla is partnering with Scroll to create a Scroll Firefox extension ("Firefox Better Web"): https://firstlook.firefox.com/betterweb/
This implies that "soft" blockers like this aren't illegal, which is a topic of debate and to my knowledge hasn't been legally tested.
I dislike paywalls as much as anyone else, but I wouldn't assume that paywall bypasses are kosher. It's not analogous with ad blocking.
No it's not. Nobody is debating this. Even if people were, it's literally impossible to enforce so it doesn't matter (unless your moral conscience is influenced by the law)
Could you explain a bit more about that without having to send you an email?
Data collected (ip, browser..) and for how long for example.
The wording here is weirdly casual and wishy-washy. I'd never pay for this add-on, but if someone is considering helping you alpha test it they might want a little firmer future commitment.
Combined with your answers in this thread I think you should slow down and consider some of the questions and concerns comments have brought up. Your responses are inconsistent and somewhat concerning.
In the true spirit of JavaScript, you just structure it however you damn well please. Well, not completely, usually you have a background page, a popup page with associated scripts, an options page, optional content scripts, etc. You can learn from examples but in general they’re just structured in whatever way the author feels like.
> I find the API very difficult to grok.
That’s surprising because most APIs are really simple as long as you’re comfortable with callbacks. Sometimes there’s a bit of trial and error (messaging might be one pain point when you write your first extension), and sometimes details might slightly differ from the docs as certain features are tightened up (usually in the name of security), but I’ve never encountered anything that defies a bit of debugging.