Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changelog: v60-beta #422

Closed
earthlng opened this issue May 15, 2018 · 13 comments
Closed

changelog: v60-beta #422

earthlng opened this issue May 15, 2018 · 13 comments

Comments

@earthlng
Copy link
Contributor

  • date: 15-May-2018
  • foreword: These are all the changes since the last changelog (v59-alpha).

changelog: [all changes]

  • all user.js updates for Firefox v60 are detailed in the ToDo: diffs FF59-FF60 issue
    • includes links to the commits made for each pref, links to bugzilla tickets, our discussions etc.
  • spring cleaning - removed some prefs matching FF's default values
    • the values haven't changed in a long time and also match ESR52.x's default values
  • revamped section 2600: MISCELLANEOUS (mostly just reordering and renumbering)
    • new subsections for DOWNLOADS, EXTENSIONS and SECURITY
  • prefsCleaner.bat updated (download) - thanks @claustromaniac !
    • massive speed improvement! now takes less than a second instead of a few minutes !!
  • @claustromaniac also ported the prefsCleaner to Bash, for Linux and Mac. Thanks!
  • ghacks-user.js updater for Mac/Linux v1.3 (download) - thanks @overdodactyl !
    • The script now compares its version number to the one online. If there is a newer version of updater.sh online it asks the user whether to download and run it.
      • 2 parameters are supported: -donotupdate to disable the update-check and -update to auto-download and run the new version without asking
    • Backup files are now saved to the directory userjs_backups
  • ghacks-user.js updater for Windows v4.5 (download)
    • now supports commenting-out active user-prefs with the merge function
  • updated the scratchpad cleanup scripts and the wiki page
  • for all the rest see the full list of pref changes below

all pref changes:

  • new active prefs:
user_pref("app.normandy.api_url", "");
user_pref("app.normandy.enabled", false);
user_pref("app.shield.optoutstudies.enabled", false);
user_pref("browser.cache.offline.insecure.enable", false);
user_pref("browser.chrome.errorReporter.enabled", false);
user_pref("browser.chrome.errorReporter.submitUrl", "");
user_pref("dom.disable_open_during_load", true);
user_pref("security.insecure_connection_text.enabled", true);
user_pref("xpinstall.whitelist.required", true);
  • new in 60beta but commented out by default:
//user_pref("extensions.screenshots.upload-disabled", true);
//user_pref("extensions.webextensions.restrictedDomains", "");
//user_pref("network.cookie.same-site.enabled", true);
//user_pref("network.ftp.enabled", false);
//user_pref("network.trr.bootstrapAddress", "");
//user_pref("network.trr.mode", 0);
//user_pref("network.trr.uri", "");
//user_pref("security.insecure_connection_text.pbmode.enabled", true);
//user_pref("ui.key.menuAccessKey", 0);
  • activated previously commented-out prefs:
user_pref("permissions.default.geo", 2);
user_pref("privacy.resistFingerprinting.block_mozAddonManager", true);
  • commented out:
//user_pref("browser.cache.offline.enable", false);
//user_pref("browser.storageManager.enabled", false);
//user_pref("dom.storageManager.enabled", false);
//user_pref("geo.enabled", false);
  • removed from the user.js:
user_pref("device.storage.enabled", false);
user_pref("general.useragent.compatMode.firefox", false);
user_pref("network.dns.blockDotOnion", true);
user_pref("network.stricttransportsecurity.preloadlist", true);
user_pref("security.block_script_with_wrong_mime", true);
user_pref("security.fileuri.strict_origin_policy", true);
user_pref("security.sri.enable", true);
  • moved to 4600: RFP (4500) ALTERNATIVES:
user_pref("webgl.enable-debug-renderer-info", false);
  • moved to 9999: DEPRECATED / REMOVED:
user_pref("browser.newtabpage.activity-stream.enabled", false);
user_pref("browser.newtabpage.directory.source", "data:text/plain,");
user_pref("browser.newtabpage.enhanced", false);
user_pref("browser.newtabpage.introShown", true);
user_pref("dom.workers.enabled", false);
user_pref("extensions.shield-recipe-client.api_url", "");
user_pref("extensions.shield-recipe-client.enabled", false);
//user_pref("view_source.tab", false);

Any and all help, suggestions, recommendations, links, tips and tricks, questions, thank you's or whathaveyou are welcome - signup/login and start typing - thanks

@claustromaniac
Copy link
Contributor

Thanks guys. What would I do without you.

@earthlng
Copy link
Contributor Author

Might be worth adding to the "to keep an eye on" sticky. IMO we can disable it again for FF62 and wait until they remove appCache support for good.
Currently it sucks a bit for ESR52 to have appCache enabled but since it's rarely used and behind a prompt I think it's fine.

@earthlng
Copy link
Contributor Author

I haven't ever seen a system addon update outside of FF releases

probably because you have auto-install disabled

@Okamoi
Copy link

Okamoi commented May 17, 2018

@earthlng Talking about changelogs, is there anything to come for Firefox 59 Release to Firefox 60 Release here ?

I'm using these any time Firefox updates, so I'm currently waiting on Firefox 59 for the repo to update :)

If it is not to be updated any more because it's too much hassle or whatever, I'll pull back to this one again, as I used to in the past. It's less good because it updates from Beta X to Release X+1, but no worries if you don't want to be burdened with this any more there's at least an alternative :)

@earthlng
Copy link
Contributor Author

@Okamoi

I'm using these any time Firefox updates, so I'm currently waiting on Firefox 59 for the repo to update :)

We're always going over those lists in our ToDo: diffs issues and instead of you looking at the lists for yourself, you'd be more than welcome to provide your input in those issues.

But anyway, I've updated the repo with the FF60 diff. A couple of prefs were not included in any of the previous or current diffs but I've listed them here. From now on Release diffs will list changes to those prefs as well.

@overdodactyl
Copy link
Contributor

Thanks Pants! Not a huge fan of that change 👎. Just now seeing this....I've got lots of emails from this repo to catch up on!

@earthlng
Copy link
Contributor Author

Maybe it's time to think about enabling DNT by default.

pros:

  1. we don't clear extensions.webextensions.restrictedDomains by default and some mozilla domains use GA but do honor the DNT flag
  2. mozilla does not set DNT by default because it was spec-ed as user-opt-in. But IMHO using something like the privacy and security enhancing ghacks user.js qualifies as saying "do-not-track me!"
  3. with the new law in Europe, explicitly telling sites to DNT might even be useful in courts
  4. DNT might not do much but it does something

cons:

  1. because it's opt-in, it puts us in smaller group FP-ing-wise (at least until more people start using it)
    BUT the same can be said about blocking cookies (which probably even fewer people do) for example.
    RFP is easily detectable too and the large majority of FF users don't use it but that didn't stop us from enabling it either.

👍 or 👎 ?

@overdodactyl
Copy link
Contributor

I can certainly appreciate that view point, there's just something that doesn't sit right with me about Mozilla giving their own websites special treatment. It would look bad for any site to be infested with adverts or to be hijacked when it's not the website owner's fault - Mozilla doesn't have the Monopoly on that.

To me, this sounds like an issue where there's gaps in the Addon review system or the ability to notify users of malicious addons, and they are trying to solve that larger problem with a little band-aid.

But given there's about:config setting, I guess it's not that big of a deal

@overdodactyl
Copy link
Contributor

Of course they have the right to do it...doesn't mean I have to like the decision. We will just have to agree to disagree on this one

@overdodactyl
Copy link
Contributor

given there's about:config setting, I guess it's not that big of a deal

#422 (comment)

@earthlng
Copy link
Contributor Author

earthlng commented May 29, 2018

@overdodactyl

I don't like it either but I understand why they did it. If a malicious addon would manage to steal millions of user's sync account and copy all their synced private data, it could be the end of mozilla.
IMO it's fine as long as they don't remove the about:config pref.

You're probably right about the review system but I think they had to change the review process, at least temporarily, because of the switch from legacy to webextensions.
Hopefully they'll change it back to review-first-publish-later at some point, but even then it's not guaranteed that they catch every malicious addon.
It's also possible that they plan to eventually support WE's from the Chrome store and if that's the case they need to protect themselves and the users from what's at that point completely outside of their control.

@earthlng
Copy link
Contributor Author

DNT vs RFP ("I don't buy this comparison") - I only compared it in terms of putting us in smaller groups

Courts? Who cares.

Companies care. Why do you think they try to comply with the new law? It's because users could sue them. Doesn't mean someone actually has to go to court - the threat of it is enough.

earthlng added a commit that referenced this issue May 29, 2018
pros and cons: see #422 (comment) + follow-up comments
@overdodactyl
Copy link
Contributor

Thanks! An interesting read for sure...glad they opened it up

@earthlng earthlng closed this as completed Jul 6, 2018
nachoparker pushed a commit to nachoparker/firefox-ownyourbits-user.js that referenced this issue Sep 8, 2018
pros and cons: see arkenfox/user.js#422 (comment) + follow-up comments
PatrickMcKenzier pushed a commit to PatrickMcKenzier/user.js that referenced this issue Oct 10, 2022
pros and cons: see arkenfox/user.js#422 (comment) + follow-up comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants