1. 22

  2. 27

    I recommend everyone switch to Firefox. Google is only going to get creepier. I finally made the switch to Firefox recently and couldn’t be much happier. I only wish Firefox had a SSB (site-specific browser) feature like Chrome does, as I still have “apps” based on Chrome.

    1. 7

      Yep that or Brave are great options. My only gripe with Firefox is how slow the Google suite is (forced to use it because of work). Perhaps it’s just my experience but Google Meet / Sheets / etc. are noticeably worse on Firefox.

      I doubt this is a fault with Firefox, though.

      1. 9

        You should probably read lobste.rs’s experience with Brave before recommending it: https://github.com/lobsters/lobsters/issues/761, https://github.com/lobsters/lobsters-ansible/issues/45

        I wouldn’t be comfortable using Brave. I would prefer Firefox, or, if absolutely necessary, something like Ungoogled Cromium.

        1. 2

          I’m not super psyched about Brave.

          I turned to Epichrome to make SSBs now that I’m not using Chrome and I’m not sure if I’m happy using it because it depends on Brave.

          1. 1

            If you’re on a Mac, I was always very happy with Fluid to make SSBs.

          2. 1

            Thanks for sharing… didn’t know about either of these; I’ll pass it along to people I know as well, that’s a little scummy…

        2. 4

          Or the Chromium-based Brave which has better privacy by default than Firefox, and you get to use all the Chrome extensions. It has a built-in adblocker, and supports (unlike Chrome/ Firefox) peer-to-peer encrypted sync of passwords, bookmarks, etc. without involving server-side storage.

          1. 18

            So Brave themselves can monetise their users? They haven’t been transparent in the past. Firefox has all of Chrome’s features and a lower memory footprint.

            1. 11

              Hell, this actually affected Lobsters too.

              1. 6

                Wow, I had a low opinion of them, but that’s much worse than I thought. Spoofing other browsers’ user agents explicitly to avoid detection? Scraping the names and photos of site creators to make it look like you’re paying the site creators directly, and pocketing the money? Modifying the content of the website to add affiliate codes to URLs?

                So Brave is literally just a hugely widespread scam then.

          2. 2

            I use Chromium for work stuff, which is all Google suite based, and Firefox for everything else. On the Mac, I use Safari in place of Firefox, but same idea.

            1. 2

              I use Chromium for work stuff, which is all Google suite based

              Out of curiosity, why? Most of my work docs are in Google Docs / Sheets, and they seem to work nicely in Firefox.

              1. 3

                I do the same, more for compartmentalization reasons than anything else. Stuff works fine in Firefox, but it’s nice to keep them separate in a really clear visual way.

                I started doing it before Firefox added containerized tabs though and just kept it out of habit. But I can’t ditch chromium entirely yet because Firefox won’t play audio without pulse.

                1. 1

                  Compartmentalization. I block as many Google things in the browser, because life is too short. I also use Chromium-based SSBs for sites that I do not trust but still visit (Facebook, mostly).

                2. 1

                  Do you use something like 1Password to manage passwords across browsers? What about bookmarks, etc.?

                    1. 2

                      Yep to 1Password; and for bookmarks, I … don’t really keep them? I save stuff to Pinboard that’s interesting, and I keep bookmarks in my Google account for work.

                  1. 2

                    +1. Other reasons to switch that popped-up recently: uBlock works best on Firefox (https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox), Google removed the ClearURLs add on from its store (https://news.ycombinator.com/item?id=26564638).

                  2. 16

                    Welcome to the “no-floc” cohort. In a world full of signal, silence also identifies you.

                    1. 4

                      Reminds me of the advice to not mess with Tor Browser settings beyond the “Safe/Safer/Safest” security sliders. Oh, you turned up NoScript to be just a little stronger? Now NoScript is a fingerprinting vector.

                      Privacy is really hard.

                    2. 3

                      Websites can take steps to protect the privacy of their users by opting out of FLoC, which would be applicable to all their visitors.

                      I don’t understand the implication of this. Does it just mean that my site will be unable to access the cohort information? Is there a point to doing this even if my site doesn’t have any scripts or use cookies? Or does it prevent the browser from recording the fact that they’ve visited my site when it calculates cohort info, regardless of what I do on my site?

                      1. 4

                        Here is a better link for that: https://github.com/WICG/floc#opting-out-of-computation

                        As I understand it – if your site sends this header, then they won’t use your site as a factor in the cohort calculation. So strangely it is opt-out but the website owners have to do it on behalf of their users which just seems so… silly…

                        1. 3

                          Google delegates legal reasonability to website owners.

                          1. 2

                            Yeah, it just seemed to me at least that it should belong with the users themselves rather than a blanket thing that website owners apply to everyone, but maybe I don’t fully understand how this is being implemented.