make p3p policy great again!
Firefox 85 cracks down on supercookies
771–780 of 786 posts
Re: Firefox 85 cracks down on supercookies
#772Earlier quoted context omitted.
Regulation as a solution for problems on the Internet is pretty stupid because jurisdictions are so diverse.
But the reason you're not brute forcing passwords on your bank's e-banking system isn't because you can't or because they are super secure, it's because if you do you'll probably go to jail. Also, good regulation is important to keep the big dogs on a leash and to have something to go after them when they don't behave. Technological solutions will of course come, but you also need regulation, especially until the tec…
> But the reason you're not brute forcing passwords on your bank's e-banking system isn't because you can't or because they are super secure, it's because if you do you'll probably go to jail.
No, this is really out of touch with how crime online works. People that want to hammer a bank rent botnets, use tor, vpns, etc.
Banks get absolutely zero protection from the law in that regard. It’s “illegal” but completely unenforceable to the point of being useless.
Re: Firefox 85 cracks down on supercookies
#773Earlier quoted context omitted.
The image caches offer no means to identify individual users unless you're able to re-parse the client side (cached) data. Guess what component is essential to perform that client-side parsing?
So tracking pixels in email clients aren’t a thing? Trust me, people will find ways around it without JS. Reinventing Flash, for a start.
Yes, tracking pixels aren't a thing (anymore).
Gmail no longer loads them. Thunderbird no longer loads them. Most providers, offering online email, have already caught on.
> Trust me, people will find ways around it without JS. Reinventing Flash, for a start.
There is no need for that. Why bother, when you can write a mobile app in proper computer language and eliminate the middleman (browser)?
Re: Firefox 85 cracks down on supercookies
#774Earlier quoted context omitted.
>JS didn't lower the barrier to programming at all. >But I disagree about lowering the barrier for developers. I think OP meant it as browsers that run JS. The built in console is so useful for testing/practice. You can run JS without any setup on most popular OS - Win/Linux/Mac. You can practice JS in console while viewing YouTube tutorial or following a JS blog/ Mozilla dev page.
I know that's what they meant, but I disagree that it lowered the barrier to creating actual applications or to getting into programming. Everyone who had MS Office installed back in the 1990s (which was basically everyone) could easily run some quick VB code to try things. But the difference was that you could also create proper applications with a UI, a database and (optionally!) some glue code. We just had no good…
>Everyone who had MS Office installed back in the 1990s (which was basically everyone) could easily run some quick VB code to try things.
Can't be everyone, how do you know the numbers? How many Office users actually used VB? MS famously stifled competition in internet browsers. 1990s numbers still won't give a fair picture.
>The Web fixed all that, albeit at the cost of cratering developer productivity, a massive increase in complexity and higher barriers to entry for new devs.
Why blame the web for higher barrier to entry. JS is doing fine. See a few surveys for popular languages: https://insights.stackoverflow.com/survey/2020#most-popular-...
Re: Firefox 85 cracks down on supercookies
#775Re: Firefox 85 cracks down on supercookies
#776Earlier quoted context omitted.
I'm not sure I understand how this is related to pi-hole. Your computer sends the raw domain name to pi-hole (e.g. ads.google.com), and pi-hole returns 0.0.0.0 if it's on the block list. There's nothing Google or anyone can do to make pi-hole stop working.
IoT devices are starting to use hardcoded DNS servers instead of using the one provided by DHCP, which negates the benefits of Pi-Hole on those devices. For now, I've configured my router to force all UDP port 53 traffic to my Pi-Hole which overrides what I mentioned above. But, in the future we may start to see IoT Devices hard-code DoH servers which will be harder to force over to the Pi-Hole.
> I've configured my router to force all UDP port 53 traffic to my Pi-Hole
Oh wow, how do you do that?
Re: Firefox 85 cracks down on supercookies
#777Re: Firefox 85 cracks down on supercookies
#778Earlier quoted context omitted.
"Regulation" mandated stupid cookie consent overlays on every damn European website. Thanks, regulation.
There is no regulation mandating cookie consent overlays - websites are free to not abuse cookies to track their users.
> There is no regulation mandating cookie consent overlays
Yes there is. A mugging is still a mugging even if the victim is "free" to give their wallet.
> websites are free to not abuse cookies to track their users.
You're free to not use such websites.
I dislike tracking and avoid being tracked myself. But this absolutely is a regulation and it's immensely disingenuous to pretend otherwise.
Re: Firefox 85 cracks down on supercookies
#779Re: Firefox 85 cracks down on supercookies
#780Earlier quoted context omitted.
Can you be tracked within the private browsing mode though? For instance in Chrome private tabs I know if you log in to something then open a new tab, that tab retains the cookies from the private session until you close all private tabs. Is this the same with Firefox? I'm hesitant to install yet another extension but I'm wondering if this one mentioned elsewhere in this thread will fix it, if it is the case with fir…
No, in Firefox I've seen each private window is a separate unrelated container.
Looks like I was wrong. All private windows and tabs belong to the same temporary container sharing cookies. Temporary Containers remedy this.
[1]: https://medium.com/@stoically/enhance-your-privacy-in-firefo...