We should be more careful. 1 in 30,000 is a pretty good chance to not get found out, but when it comes to videos with smaller viewcounts, we should not be allowing them to be shared.

Also we should do something about the tracking links that people keep sharing here willynilly. Even if it's just a rule change. Feels like 6 months since I last posted about this without change.

  • Hurvitz [they/them]
    ·
    7 months ago

    Not sure what multi account containers buys in this context, I think the default behavior of firefox mostly mitigates the 3rd party tracking that used to be rampant. Maybe I'm just not thinking though. They'd still get your IP, and the fact that you clicked on a link shared by x other person?

    I guess it would open links posted on hexbear in the hexbear container, on which you won't be logged into the other site? But iirc common practice for sites you do have a sign in for is to auto-open them into their own container thonk so you'd have to be configuring it pretty paranoid-ly.

    Attempting to work around and mitigate these issues at the site level is probably a good idea, because people individually will not all be so careful. But it has to be done in as like, convenient a way as possible, otherwise it'll just piss users off

    • TheSpectreOfGay [he/him, she/her]
      ·
      7 months ago

      firefox doesn't kill all trackers, though it does kill a lot of them. things like google tracking what your account has interacted with obviously won't be handled by firefox's security features. when I open youtube videos in my hexbear container, I'm not logged into youtube, so my actual youtube account behaves like it's never watched them. do not set youtube to auto-open in a container, that defeats the purpose of using this imo. i have auto-open in container for hexbear, and like... shoppping sites like ebay? basically sites that wouldn't really be linked to. things like twitter and youtube where the concern comes from should not auto-open into a container, you can just manually open it into the proper container when you want to browse it properly.

      and yea, we should handle it site wide, but in absence of it being handled site wide i would recommend doing this ^^