Switch to FPP + Startup info box to inform users of changes in the future #130

Open
any1here wants to merge 2 commits from any1here/FPP into main
any1here commented 2026-01-18 14:48:37 +00:00 (Migrated from codeberg.org)
Requires https://codeberg.org/librewolf/settings/pulls/108
alyx161 commented 2026-05-04 17:44:12 +00:00 (Migrated from codeberg.org)

@any1here Is there still anything blocking this?
If not, interested to rebase it to we can merge it for the next release?

@any1here Is there still anything blocking this? If not, interested to rebase it to we can merge it for the next release?
any1here commented 2026-05-04 18:31:29 +00:00 (Migrated from codeberg.org)

@alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-14300327:

@any1here Is there still anything blocking this? If not, interested to rebase it to we can merge it for the next release?

Rebase wouldn't work, since I would need to move the settings to the new approach

@alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-14300327: > @any1here Is there still anything blocking this? If not, interested to rebase it to we can merge it for the next release? Rebase wouldn't work, since I would need to move the settings to the new approach
alyx161 commented 2026-05-04 19:00:57 +00:00 (Migrated from codeberg.org)

Soo settings update is the blocker, go it :3

Soo settings update is the blocker, go it :3
any1here commented 2026-05-04 19:06:24 +00:00 (Migrated from codeberg.org)

@alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-14317292:

Soo settings update is the blocker, go it :3

I updated the settings pane to the new approach, hope the other stuff still works.

@alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-14317292: > Soo settings update is the blocker, go it :3 I updated the settings pane to the new approach, hope the other stuff still works.
any1here commented 2026-08-06 11:13:46 +00:00 (Migrated from codeberg.org)

@alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154.

@alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154.
ltguillaume commented 2026-08-06 15:11:35 +00:00 (Migrated from codeberg.org)

@any1here wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20616905:

@alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154.

Any sources for this and your reasoning for doing this?

@any1here wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20616905: > @alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154. Any sources for this and your reasoning for doing this?
alyx161 commented 2026-08-06 15:24:24 +00:00 (Migrated from codeberg.org)

This would be a drastic change to the current behavior

I thought the consent was to consider this for later?

This would be a drastic change to the current behavior I thought the consent was to consider this for later?
any1here commented 2026-08-06 20:00:56 +00:00 (Migrated from codeberg.org)

CC @degausser

CC @degausser
degausser commented 2026-08-06 20:17:19 +00:00 (Migrated from codeberg.org)
https://bugzilla.mozilla.org/show_bug.cgi?id=2050515#c11
any1here commented 2026-08-06 21:11:44 +00:00 (Migrated from codeberg.org)

@ltguillaume wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20626895:

@any1here wrote in #130 (comment):

@alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154.

Any sources for this and your reasoning for doing this?

@alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20627279:

This would be a drastic change to the current behavior

I thought the consent was to consider this for later?

We could do the +AllTargets approach, but this would just kick the can down the road and have people get their defaults changed twice. +AllTargets also has various quirks, especially with the Canvas* RFPTargets, which breaks some of the permissions for extraction.

We are also hurting user experience for little to no gain, since this level of protection doesn't make sense outside of TB/MB. We are enabling everything, but gaining nothing. ETP Strict Firefox was good enough to beat fingerprint.com, which is the best we can also realistically aim for.

Will maybe edit this with more info tomorrow.

@ltguillaume wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20626895: > @any1here wrote in #130 (comment): > > > @alyx161 Change of plans. Instead of going with +AllTargets, I have opted to follow Nightly's RFPTargets. The current patch won't compile, since the extra nightly RFPTargets are coming in 154. > > Any sources for this and your reasoning for doing this? @alyx161 wrote in https://codeberg.org/librewolf/source/pulls/130#issuecomment-20627279: > This would be a drastic change to the current behavior > > I thought the consent was to consider this for later? We could do the `+AllTargets` approach, but this would just kick the can down the road and have people get their defaults changed twice. `+AllTargets` also has various quirks, especially with the [Canvas* RFPTargets](https://searchfox.org/firefox-main/rev/ac91bfcce1bf3240e2dce40f47c372e76bc4f26c/toolkit/components/resistfingerprinting/RFPTargets.inc#23-25), which breaks some of the permissions for extraction. We are also hurting user experience for little to no gain, since this level of protection doesn't make sense outside of TB/MB. We are enabling everything, but gaining nothing. [ETP Strict Firefox was good enough to beat fingerprint.com](https://brside.com/blog/brave-firefox-safari-only-two-survived-this-fingerprinting-test), which is the best we can also realistically aim for. Will maybe edit this with more info tomorrow.
This pull request has changes conflicting with the target branch.
  • assets/patches.txt
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin any1here/FPP:any1here/FPP
git switch any1here/FPP

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff any1here/FPP
git switch any1here/FPP
git rebase main
git switch main
git merge --ff-only any1here/FPP
git switch any1here/FPP
git rebase main
git switch main
git merge --no-ff any1here/FPP
git switch main
git merge --squash any1here/FPP
git switch main
git merge --ff-only any1here/FPP
git switch main
git merge any1here/FPP
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
librewolf/source!130
No description provided.