About network.cookie.cookiebehaviour

[ghost]

Arkenfox sets it to 5 but when I checked my Mull 107 it say 4 but it has TCP now. Would it be better on 5?

[SkewedZeppelin]

Mull 107 still uses FPI, not dFPI.

[opusforlife2]

https://github.com/mozilla-mobile/fenix/issues/27487 says:

We want to disable TCP (tcp-feature and tcp-cfr flags in the mr2022 Nimbus feature) in 107, so we can re-enable it in a Nimbus rollout in 107 Release.

That sounds to me like the feature is ready, but they just want to roll it out slowly. We don't have that limitation.

Edit: BTW, how come the F-Droid builds of 106 are failing, yet you have both 106 and 107 available in your repo? Just F-Droid-specific issues?

[opusforlife2]

https://github.com/mozilla-mobile/firefox-android/pull/947

https://bugzilla.mozilla.org/show_bug.cgi?id=1818058

[opusforlife2]

@SkewedZeppelin Since 112 is out, can dFPI replace FPI?

[SkewedZeppelin]

I'm still on the fence with this.

There are people who keep dozens of tabs open or logins saved and switching from FPI to dFPI will invalidate all stored cookies.

Another issue I've learned about is people purposely disabling ETP for whatever asinine reasons despite ETP strict required for dFPI.

[opusforlife2]

Well, I think it's pretty clear that you don't have to shoulder the responsibility of how people use your app. You provide the absolute best presets out of the box, and if people want to mess with that for whatever reason, that's on them, whether it is out of learned expertise, ignorance, or misguidance.

---

A hard line on this would be to disable the menu completely, forcing people to use ETP Strict.

[opusforlife2]

@SkewedZeppelin Any change in your thoughts on this?