-
Notifications
You must be signed in to change notification settings - Fork 232
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
README: refactor addons section; other fixes; fix GEOLOCATION/QUIET FOX sections of #208 #255
Conversation
Done with this part. Let me know if this should be split into separate PRs. |
link to mozilla meta tracking page for this pref change pref description since this is related to more than screen size and media queries
* remove lengthy description, just recommend addons, or don't recommend them. * remove duckduckgo plus, add generic hardening recommendation about privacy-conscious search engines * store all addon-specific recommendations in the addon section * Move ghostery to Other addons subsection, add uMatrix to this section * remove links to issues (use the search feature) * move built-in tracking protection links to user.js tracking protection section * run make - auto-update 'What does it do' section
…pecific recommendations
…3 0204 of #208 more accurate description of accept_language setting
…when enabled, fixes items 0309 0310 of #208
see https://dxr.mozilla.org/mozilla-central/source/modules/libpref/init/all.js#1350 set experiments manifest uri to blank, even though experiments are already disabled; update previously broken links in experiments/telemetry section fixes item 0340 of #208
… don't nag user about unsent crash reports: fixes items 0350 0351 of #208
README: * add fingerprinting mitigation to project goals * add optional user.js customization to usage steps * reorder system wide installation section (os specific steps at the end) * add generic hardening recommendations regarding password policy/open-source software/plain-text communications/tor usage * issues: add generic organization guideline * add firefox about: urls doc link user.js: * add notice about webrtc breaking p2p file transfer methods * make affected Firefox versions consistent
* detect preferences that are no longer present in firefox source target firefox version is configurable mozilla test suite prefs files are included for completeness sake * detect Firefox preferences not covered by user.js preferences that should we don't want to modify should be listed in ignore.list add a basic ignore.list * display stats on number of covered preferences * to use, run 'make tests' subtargets: downloadffprefs, checkdeprecated, stats, cleanup * add 'make tests' to travis script * run 'make authors' to generate an AUTHORS file, ordered by number of commits to add extra authors/credits, git commit --allow-empty --author="A U Thor <[email protected]>" TODO: add a .mailmap file to deduplicate authors with multiple email addresses Results of tests against lastest Firefox revision can be seen at: ................
@nodiscc : I see under this you listed a link for about: URLs I find using Compared to the list at the URL, I am missing:
And here are six items (non-extension) not listed
Might be better and easier to just use |
Thanks, I edited https://developer.mozilla.org/en-US/Firefox/The_about_protocol and asked for review. It's better to link to that page since it's the actual documentation on all Edit: page history https://developer.mozilla.org/en-US/Firefox/The_about_protocol$history |
e92362c 093bd97 c0962da 24a5cfe c37bf58
Results of Edit: also on travis: https://travis-ci.org/pyllyukko/user.js/builds/215770898 |
Mehmet Atif Ergun <[email protected]> | ||
mengele-chan <[email protected]> | ||
uberspot <[email protected]> | ||
zummuz <[email protected]> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not needed. All the info is available as metadata.
|
||
// PREF: Disable Firefox Sync | ||
// https://wiki.mozilla.org/Services/Sync | ||
user_pref("services.sync.enabled", false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary, as it's opt-in and some users might actually want to use it.
Will continue the review later, as I'm afraid I don't have the time to do it this week |
|
||
// PREF: Don't use Mozilla-provided location-specific search engines | ||
user_pref("browser.search.geoSpecificDefaults", false); | ||
user_pref("browser.search.geoSpecificDefaults.url", ""); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the ""
necessary, when the feature is toggled off?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably not, this can be moved to ignore.list
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@./gen-readme.sh | ||
|
||
# To decrease tests verbosity, comment out unneeded targets | ||
tests: downloadffprefs checknotcovered checkdeprecated stats cleanup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will fail horribly if you have e.g. MAKEFLAGS="-j 4"
, like I do.
I'm not entirely sure what is the proper way to fix it, as I'm not that familiar with makefiles. Maybe with .NOTPARALLEL?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes apparently a target named .NOTPARALLEL
should inhibit the -j
cli/config file option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, that's what I thought. I'm still not sure as to where and how to add it.
e.g., should it be like:
.NOTPARALLEL: downloadffprefs
Or just as it's own line? It wasn't completely clear to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot to post the link I found: http://stackoverflow.com/questions/4346399/how-can-i-force-gnu-make-to-not-build-recipe-in-parallel/23903293#23903293
.PHONY: all clean
.NOTPARALLEL:
anotherTarget: dependency1
Apparently on it's own line. The MAKEFLAGS variable can also be used (solution 3)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw that post also when I was looking at the subject. Is it so, that everything below that will not run as parallel or what? I mean there are still some things, that can be run as parallel in the makefile, e.g. authors
, whatdoesitdo
and all the rest for that matter, once downloadffprefs
has finished.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it so, that everything below that will not run as parallel or what?
This is what it looks like, but I have no experience with parallel usage of Make - very interesting, I really need to read the full Make manual.
Unfortunately no time to work on it at the moment, would you be ok to apply the global MAKEFLAGS := --jobs=1
var, and open an issue (Makefile: parallelize tests
) ? We can improve this later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
BTW. are you planning on pushing more commits into this? As I'm now tweaking it and trying to get it merged soon. |
No, please edit it as you like; I will add commit comments on https://github.com/pyllyukko/user.js/commits/nodiscc-fixesfixesfixes if needed, or open other issues. |
@# generate an AUTHORS file, ordered by number of commits | ||
@# TODO: add a .mailmap file to deduplicate authors with multiple email addresses | ||
@# to add extra authors/credits, git commit --allow-empty --author="A U Thor <[email protected]>" | ||
@git shortlog -sne | cut -f1 --complement >| AUTHORS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW. would the following .mailmap
file be sufficient for this?
CHEF-KOCH <[email protected]> <[email protected]>
Francois Marier <[email protected]> <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it works with these contents (I just tested it with git shortlog -sne
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it with 563c4c6. Even though I removed the AUTHORS file, but it's still better to get exact stats :)
One thing that is wrong here, is that there are so many people who have contributed through insights in issues & PRs, but haven't pushed any commits.
We would need to have yet-another-script that queries GitHub's API for all the people involved in here to have a complete list :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I know there is no way to (directly) list users who posted in a github project issue tracker. But it can be parsed from https://api.github.com/repos/pyllyukko/user.js/issues (login
values). If you create a new issue for this, I'll have a look.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was a joke, we don't need to do that :)
See commit messages