5 ms·

Meanwhile me laughing in Firefox. I hope no one here is surprised by this G was more and more anti ad-blocking for years now. This is only natural conclusion

Meanwhile me laughing in Firefox. I hope no one here is surprised by this G was more and more anti ad-blocking for years now. This is only natural conclusion after u are a de-facto browser monopoly.

Craighead 7y ago
Is it better to send all dns requests to a private company that harbors and protects racists and pedophiles?
gnom69 7y ago
Google captcha makes some sites almost unusable on firefox if you dare to resist fingerprinting for full traceability. https://news.ycombinator.com/item?id=20147015 https://news.ycombinator.com/item?id=20147015
- romanovcode 7y ago
  Can you surpass it by faking user-agent and pretend to be Chrome?
  - GuB-42 7y ago
    It is not about Chrome vs Firefox. It is about how much information they can get about you. The idea behind the "I am not a robot" captcha is that if you act like a human, then you don't need to be shown pictures for further confirmation. The more you allow tracking, the more info they have to figure it out. A big one is being logged in to your Google account. Having access to all your history really helps. And because Chrome heavily encourage you to setup a Google account, Chrome users are more likely to be logged in than Firefox (or other) users. Spoofing your user-agent is likely to be worse. If you have a Chrome user-agent but your browser don't act like Chrome, that's a big red flag. Bots often spoof their user agents.
- pmlnr 7y ago
  I see recaptcha, I walk. There's nothing else I can do. BTW if I turn on 1st party isolation in FF, I keep feeding the fire hydrant monster for hours.
  - mcv 7y ago
    Sites with recaptcha should be boycotted as much as possible. It's a stupid, annoying test.
    - PuffinBlue 7y ago
      They're getting garbage in with the service too - about the last dozen (at least) or more times I've had to do it you can clearly see that one of the options is what the AI thinks should be the answer, but isn't. But if you don't select it before clicking 'verify' it gives you a little 'please select all taxis' or whatever. No AI, that's just a car, not a taxi. But who cares, I just click anyway and feed bullshit in and in a few years it'll think everything is a taxi.
ethagnawl 7y ago
> This is only natural conclusion after u are a de-facto browser monopoly. ... and (probably?) the world's largest ad broker.
AsusFan 7y ago
You won't be laughing for long, I believe. See this FAQ: https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/ https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest... Note how they say: "We have no immediate plans to remove blocking webRequest and are working with add-on developers to gain a better understanding of how they use the APIs in question to help determine how to best support them." "No immediate plans" is weasel-speak, as is "[we] are working with add-on developers". If Mozilla was dead sure that they weren't going ahead with it, they would say so, unequivocally. And I remind you that Mozilla "worked with add-on developers" when they unilaterally decided to drop XUL and go ahead with web extensions, while failing to include support for APIs that developers said they needed to support functionality that their add-ons provided. IMHO, adoption of manifest v3 is not a matter of "if" but rather "when".
- tasogare 7y ago
  I don’t understand why you are downvoted because Firefox is a Google funded browser. One day they’ll have to compromise or find a real business model.
- hendersoon 7y ago
  Mozilla will certainly support manifest v3 to maintain Chrome compatibility. That was never in question. The question is whether Mozilla _removes_ support for webRequest like Google did. And you're right, they weaseled their way out of answering that question.
- plopz 7y ago
  You just have to look at how they don't support addons in their new mobile browser to see their true intentions.
  - bn7t 7y ago
    Addon support will be available in Firefox Preview. This has been clarified.
- dessant 7y ago
  Mozilla is free to implement Manifest v3, while preserving the webRequest API in its current state. Maintaining the blocking abilities of the webRequest API would not introduce any incompatibilities with Chrome extensions, because they simply would not use that part of the API.
ibejoeb 7y ago
Just tried updating to the latest firefox on MacOS Catalina and I get: >“Firefox Software Update.app” can’t be opened because Apple cannot check it for malicious software.

Meanwhile me laughing in Firefox. I hope no one here is surprised by this G was more and more anti ad-blocking for years now. This is only natural conclusion after u are a de-facto browser monopoly.

Craighead 7y ago

Is it better to send all dns requests to a private company that harbors and protects racists and pedophiles?

gnom69 7y ago

Google captcha makes some sites almost unusable on firefox if you dare to resist fingerprinting for full traceability. https://news.ycombinator.com/item?id=20147015 https://news.ycombinator.com/item?id=20147015

romanovcode 7y ago
Can you surpass it by faking user-agent and pretend to be Chrome?
- GuB-42 7y ago
  It is not about Chrome vs Firefox. It is about how much information they can get about you. The idea behind the "I am not a robot" captcha is that if you act like a human, then you don't need to be shown pictures for further confirmation. The more you allow tracking, the more info they have to figure it out. A big one is being logged in to your Google account. Having access to all your history really helps. And because Chrome heavily encourage you to setup a Google account, Chrome users are more likely to be logged in than Firefox (or other) users. Spoofing your user-agent is likely to be worse. If you have a Chrome user-agent but your browser don't act like Chrome, that's a big red flag. Bots often spoof their user agents.
pmlnr 7y ago
I see recaptcha, I walk. There's nothing else I can do. BTW if I turn on 1st party isolation in FF, I keep feeding the fire hydrant monster for hours.
- mcv 7y ago
  Sites with recaptcha should be boycotted as much as possible. It's a stupid, annoying test.
  - PuffinBlue 7y ago
    They're getting garbage in with the service too - about the last dozen (at least) or more times I've had to do it you can clearly see that one of the options is what the AI thinks should be the answer, but isn't. But if you don't select it before clicking 'verify' it gives you a little 'please select all taxis' or whatever. No AI, that's just a car, not a taxi. But who cares, I just click anyway and feed bullshit in and in a few years it'll think everything is a taxi.

ethagnawl 7y ago

> This is only natural conclusion after u are a de-facto browser monopoly. ... and (probably?) the world's largest ad broker.

AsusFan 7y ago

You won't be laughing for long, I believe. See this FAQ: https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/ https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest... Note how they say: "We have no immediate plans to remove blocking webRequest and are working with add-on developers to gain a better understanding of how they use the APIs in question to help determine how to best support them." "No immediate plans" is weasel-speak, as is "[we] are working with add-on developers". If Mozilla was dead sure that they weren't going ahead with it, they would say so, unequivocally. And I remind you that Mozilla "worked with add-on developers" when they unilaterally decided to drop XUL and go ahead with web extensions, while failing to include support for APIs that developers said they needed to support functionality that their add-ons provided. IMHO, adoption of manifest v3 is not a matter of "if" but rather "when".

tasogare 7y ago
I don’t understand why you are downvoted because Firefox is a Google funded browser. One day they’ll have to compromise or find a real business model.
hendersoon 7y ago
Mozilla will certainly support manifest v3 to maintain Chrome compatibility. That was never in question. The question is whether Mozilla _removes_ support for webRequest like Google did. And you're right, they weaseled their way out of answering that question.
plopz 7y ago
You just have to look at how they don't support addons in their new mobile browser to see their true intentions.
- bn7t 7y ago
  Addon support will be available in Firefox Preview. This has been clarified.
dessant 7y ago
Mozilla is free to implement Manifest v3, while preserving the webRequest API in its current state. Maintaining the blocking abilities of the webRequest API would not introduce any incompatibilities with Chrome extensions, because they simply would not use that part of the API.

ibejoeb 7y ago

Just tried updating to the latest firefox on MacOS Catalina and I get: >“Firefox Software Update.app” can’t be opened because Apple cannot check it for malicious software.