• 1 Post
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 31st, 2023

help-circle







  • I don’t think there is any proven results, but I think the reason the EFF prefers Braves decision is the philosophy that there are so many data points that it could be possible to link you to it using the ones not standardized by anti fingerprinting.

    Like ways to incorrectly describe someone. One describes a guy correctly but generically. One describes a guy with a lot of detail but the wrong race and two feet too short.



  • What, social lives? Get outta here with that nonsense and be a hobbit like the rest of us :)

    Seriously though, if you’re thinking on a phone I’d reccomend just creating a second profile instead of getting a whole new device. The apps won’t be running when the profile is running, and as a bonus you can usually restrict the profile’s permissions. Also consider checking out web wrappers (e.g. frost) or PWAs.

    On a desktop you can always just use the web version, bonus points if you auto clear cookies or have a separate profile.

    Edit: if you already have a spare then that might work better than profiles.









  • I doubt they’re doing anything to secerative in the background. Not a fan of Bat or their affiliate link scamdle, but also not a fan of Firefox’s ads, telemetry, trademark claims against Firefox forks, and accepting Google money for bad defaults - as I’m not a fan of Vivaldi being closed source and their adblock that doesn’t block all ads.

    Brave is great for somebody who doesn’t know/want to configure defaults beyond optionally disabling Bat. If you can then Firefox & derivatives might give a better experience.

    Brave is also Chromium based, but being a heavy fork it doesn’t hold onto the worst parts, making it more alright.


  • That, and like others mentioned their flexibility, plus the fact that they’re fairly reliable (maybe less than some good Iaas providers but a fair bit more than your consumer vps places). Moments ago I went to the hetzner site to check them out and got:

    Status Code 504 Gateway Timeout

    The upstream server failed to send a request in the time allowed by the server. If you are the Administrator of the Upstream, check your server logs for errors.

    Annoying if it’s you nextloud instance down for a minutes, but a worthy trade off if you’re paying 1/4 of the price. Extremely costly for big business or even risking peoples’s lives for a few different very important systems.