remove privacy.firstparty.isolate

[privacyguides]

remove privacy.firstparty.isolate

[dngray]

privacytools/privacytools.io#2081 (comment) and the following

What I am looking at doing with that is removing the whole "about:config" section, and just showing what can be achieved through Mozilla's UI.

We'll of course still mention https://github.com/arkenfox/user.js

@Thorin-Oakenpants, You are right. But I think it could much better like in GUI as https://ffprofile.com which will be easy to be use or how about making a UI like https://privacy.sexy ?

I mean these could be better for the user by finely adjust thing to fix some issues with arkenfox like crashes or incompatiblity with sites.

[rusty-snake]

privacytools/privacytools.io#2081 (comment) and the following

[Thorin-Oakenpants]

FPI overrides ETP Strict - so you should mention to make sure that is set to false - since you listed it for so long to so many users

[Thorin-Oakenpants]

How about the contents just be moved into a blog

that's what arkenfox is for. For most users, turning on HTTPS-Only Mode, ETP Strict and adding uBO is more than enough

Any thoughts on how you would expect this to happen?

What does the Strict mode in Firefox leave to be desired? Curious here.

[PhysicsIsAwesome]

What does the Strict mode in Firefox leave to be desired? Curious here.

A lot of things. privacy.resistFingerprinting is not enabled, just to give an example.

[PhysicsIsAwesome]

privacy.firstparty.isolate has been made (effectively) redundant with recent firefox updates, and should be removed

I don't see it being redundant. Do you have a source or sth? Tor browser and arkenfox still use FPI.

[rusty-snake]

If you set ETP=strict, FPI is effectively redundant (for the average user).

Since FF85 is privacy.partition.network_state set to true and isolates/partitions all network stuff (various caches, hsts, ...) and ETP in strict mode isolates storage stuff (cookies, localStorage, indexedDB, ...).

[dngray]

FPI overrides ETP Strict - so you should mention to make sure that is set to false - since you listed it for so long to so many users

Would it not be worthwhile to just suggest users create a new profile?

If I'm being totally honest, we don't know what state a user's browser might be in if they've been fiddling with about:config settings. I'm not totally confident that flicking that single option will restore things.

Perhaps something general like.

If you've changed settings in about:config, in the past, we suggest you create a new browser profile.

[Thorin-Oakenpants]

that's up to you .. at arkenfox we can run prefsCleaner or override for a few releases

[dngray]

I'm thinking of re-writing the blog article https://privacyguides.org/blog/2019/11/09/firefox-privacy/ so we might mention it there.

[ItsIgnacioPortal]

removing the whole "about:config" section

How about the contents just be moved into a blog, and then linked on the "Related Information" section? Mozilla frequently removes config options from the GUI and lets them be accesible via about:config only, so removing that section would limit the users a lot.

[ItsIgnacioPortal]

@Thorin-Oakenpants, You are right. But I think it could much better like in GUI as https://ffprofile.com which will be easy to be use or how about making a UI like https://privacy.sexy ?

I mean these could be better for the user by finely adjust thing to fix some issues with arkenfox like crashes or incompatiblity with sites.

A bit unrelated but thanks for the links! They seem really handy for mass-deployments

[dngray]

This will get closed soon when #383 and #309 is finished. Should happen this week.