101–110 of 120 posts
> I’m not sure whether that is because Mozilla consider it unsafe, unpractical, or don’t want to commit to maintain the feature in future releases. I imagine it was implemented for the container tabs.
Earlier quoted context omitted.
I feel like the cause is most likely that there are just too many darn websites for a user to be willing to specify them all. Solving this would seem to require some global database of "all sites run by company X" that undergoes constant maintenance.
How far would the WHOIS records go toward providing that info?
Earlier quoted context omitted.
Why do you believe that Google aren't tracking people? If they have the technological capability to do so they almost certainly do, even if they happen to serve non-personalised ads while doing it.
Because technology alone can’t protect your privacy. You need to trust people. Google says they don’t track ads when configured to not-track. They provide technical details on what this means. It’s designed around the General Data Protection Regulation (GDPR). At some point there has to be trust. I trust that Google won’t risk millions of Euros in fines over lying about not tracking people.
Hell, it's the only thing that can.
Earlier quoted context omitted.
How can you tell it works? I've been trying now 5 times to enable it, and testing if it works. If I understand correctly, if I log in to gmail.com (mail.google.com), google.com should be logged in, but google.dk and youtube.com shouldn't since First-Party Isolation should be isolating them, but no matter how hard I try, it doesn't work. If I log in to mail.google.com, I get logged into youtube.com, google.com and goo…
Cooperating websites can subvert first-party isolation by redirecting the top level page through multiple first-party domains (with an ID in the URL). And Google does exactly that when you login. How to properly prevent it is still an open question: https://bugzilla.mozilla.org/show_bug.cgi?id=1319839
Is there a test I can use to confirm that it's working? I've set privacy.firstparty.isolate true and privacy.firstparty.isolate.restrict_opener_access true and when I log in to Github followed by Travis, Travis was able to log in without prompting for a password.... Firefox 62 macOS. Edit: I did lose all my cookies on restart, so I do believe the option is at least enabled. Still would like to test that it's actually…
Now go to https://rittervg.com/misc/ff/fpi.html On first load it should say the same. If it says the same timestamp that was stored on the first page - it's not working.
Source: I'm a Mozilla Developer who is one of the primary devs/supporters of First Party Isolation.
So after enabling it, is there some easy way to see if it actually works?
Is there a test I can use to confirm that it's working? I've set privacy.firstparty.isolate true and privacy.firstparty.isolate.restrict_opener_access true and when I log in to Github followed by Travis, Travis was able to log in without prompting for a password.... Firefox 62 macOS. Edit: I did lose all my cookies on restart, so I do believe the option is at least enabled. Still would like to test that it's actually…
Go to https://ritter.vg/misc/ff/fpi.html On first load it should say "There was nothing in local storage." Now go to https://rittervg.com/misc/ff/fpi.html On first load it should say the same. If it says the same timestamp that was stored on the first page - it's not working. Source: I'm a Mozilla Developer who is one of the primary devs/supporters of First Party Isolation.
Is there a test I can use to confirm that it's working? I've set privacy.firstparty.isolate true and privacy.firstparty.isolate.restrict_opener_access true and when I log in to Github followed by Travis, Travis was able to log in without prompting for a password.... Firefox 62 macOS. Edit: I did lose all my cookies on restart, so I do believe the option is at least enabled. Still would like to test that it's actually…
Go to https://ritter.vg/misc/ff/fpi.html On first load it should say "There was nothing in local storage." Now go to https://rittervg.com/misc/ff/fpi.html On first load it should say the same. If it says the same timestamp that was stored on the first page - it's not working. Source: I'm a Mozilla Developer who is one of the primary devs/supporters of First Party Isolation.
So wouldn't a better test be about a third party that was used in a first party context before? Since FPI goes beyond third party cookies.