-
Notifications
You must be signed in to change notification settings - Fork 519
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: v67-beta #732
Comments
It seems I'm partly to blame for that. I gotta admit your reaction kinda took me by surprise though. I recall comments of yours where you were clearly against keeping some FYI kind of stuff, and I'm pretty sure you at least once said you considered the number of prefs excessive. Then again, maybe those memories are from before previous cleanups... |
No one is to blame for anything. No-one, myself included, did anything wrong. The changes look excessive but they're not. All I've done is remove a lot of dead wood, simplify troubleshooting, make corrections and consistencies, and flip 3 major things (HWA, HTTP2, and some font shit). You're all big girls now, who know how to use overrides. It's certainly nothing like a fucking shitshow, and no offense, but if anyone was paying attention over the last 6 weeks (i.e they were here), they would have seen the 100+ tiny incremental changes and had input (as some of you did). Anything changed can be put back. It's a living document. Calm down and chill out and all that 💋 |
Just popping in to give my two cents. On a side note, I really hope I'm misinterpreting because I feel like some tension arose on this issue and it saddens me. stalker mode: on The lurker I am follows this repo as closely as I follow some of my favorite TV shows. stalker mode: off I know I'm no expert, but I read every commit and issue, and I really think the level of protection offered by the .js did not weaken at all. Removed prefs were useless and commented out prefs are still listed for anyone to add to their overrides. I made my own research when something felt off, and I always ended up agreeing to the changes. |
No. That's just me being insecure and getting all defensive. I highly value E's input, and would have thought everything I did was backed up by practicality and solid logic. |
Okay then, have a hug. |
Hi, Thanks for all the work you've done! I noticed that the pref differential, which I always use first before checking in here, hasn't been updated for Firefox 67. Is it abandoned for good ? I can see that the issue we're posting in right now uses a pref differential, but I really liked the presentation of Earthlng's repo. If it is to be dropped, would you mind making public the tool used to build the diffs, with maybe a short explanation on how to use it ? |
I went to my bathroom, turned off the lights and said Earthlng's name twice in front of the mirror. After taking in some water to clean up the blood from the mouthful, I'm ready. Don't blame me as we all die in the most twisted and excruciatingly painful way. Would you mind updating your pref differential repo, or maybe sharing the diff-making tool if you can't be bothered with this repo any more ? |
Hi, my pref differential repo is not abandoned, I just forgot to update it. Must have been the shock of seeing 70 prefs removed from the user.js, I guess ;) Here you go: https://github.com/earthlng/FFprefs-diffs/blob/master/diffs/6x/diff-v66.0-vs-v67.0.log.js |
No death whatsoever, not even a polar bear ? Neat.
Shit that's a big one. Gonna take a while. I have dreaded memories of 62 --> 63 with its 199 diffs ( 122 new, 56 gone, 21 different ), but gotta do it. Thanks for the update :) I ALWAYS end up updating Firefox within 0-10 days from the release, by which point this repo is done with the work. I should somehow find a sweet spot where I can contribute back. |
Would I seem any weirder of a Maybe I should drop my current privileges and start doing that again... |
Damn NSA cats... |
About the removed safe browsing prefs, I'm not going to complain about them or anything else being removed or changed, but I'd like to know if the same results can be fully achieved in the UI or if I should copy the entries and re-add them on my personal user.js. I don't follow reddit or any other of the mentioned places you guys supposedly had issues with, I don't really know what happened and I don't want to stir up any trouble, but I just don't want anything google related on my browser unless google is what I'm using as a search engine. |
Technically, no, because you can't blank out all those URL prefs via GUI (if that's what you're referring to), but those were there only as fallbacks, I guess. In practice, blanking those out is not necessary to disable SB, so they are redundant.
Pants simply removed a bunch of redundant (unnecessary) prefs. Nothing else happened. There were other unrelated changes I hope that helps. |
I don't care much about those if they're just fallbacks, I just wanted to be sure the GUI settings were effectively and completely disabling the "feature" on their own. Thanks.
That's never been an issue for me, especially if they are single entries about different things, I always compare and edit my user.js according to new releases, changes, things I find out to be breaking stuff and so on. |
FF67 Release notes
FF67 for developers
FF67 compatibility
FF67 security advisories
⭐ foreword from 👖 ⭐
the biggest change / surprise in FF67+ is the pref
privacy.resistFingerprinting.letterboxing
(4504). This affects everyone: including those who disabled RFP (4501) because it is currently independent of RFP (but expected to get tied into it at some stage after testing).So if you were wondering what the white borders around the web content in your browser window was, this is the pref (4504). If you're serious about anti-fingerprinting, then this fixes a lot of screen/window measurement shortcomings, and we recommend you use it and get used to it. If you're not using RFP, override it.
changelog: [all changes]
all pref changes:
4600: RFP ALTERNATIVES
:9999: DEPRECATED / REMOVED
:Any and all help, suggestions, recommendations, links, tips and tricks, questions, thank you's or what have you are welcome - signup/login and start typing - thanks
The text was updated successfully, but these errors were encountered: