-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bloomberg paywall #3
Comments
I just figured it out, it's just a cookie block. If @iamadamdev can just block cookies for |
It's still not fixed after the latest version https://imgur.com/a/b2p9xyb |
Works for me. This extension works best with uBlock Origin.
|
Yep, I'm on uBlock Origin 1.16.4, using BP version 1.2.3. The Bloomberg paywall hits after 10 articles, so make sure you click on 10 things and test it after that. |
I'm on Windows and tested it on Chrome & Firefox. Everytime I visit a bloomberg article it resets it to 9 articles (since it counted the one I just visited as 1 of 10). Are you sure you have Bloomberg selected under options? |
I'm the same as Adam here.
On Mon., 7 May 2018, 4:33 am Adam, ***@***.***> wrote:
I'm on Windows and tested it on Chrome & Firefox. Everytime I visit a
bloomberg article it resets it to 9 articles (since it counted the one I
just visited as 1 of 10). Are you sure you have Bloomberg selected under
options?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG_nCPLPx6_A8sSWSS1f4OiFUWE3qMYdks5tv0INgaJpZM4TwfGS>
.
--
Regards,
Manmeet
|
I reinstalled the extension and it seems like the issue isn't there anymore. Thanks for troubleshooting! Now if we can just get it in the Chrome Web Store so that it auto-updates... |
It was in Chrome Web Store last year, but Google banned it. =( |
* Update background.js * Update README.md * Update options.js * Update background.js
Bloomberg.com has added a paywall. Can you look into blocking it?
The text was updated successfully, but these errors were encountered: