-
Notifications
You must be signed in to change notification settings - Fork 523
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
Comments
Thanks guys. What would I do without you. |
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. |
probably because you have auto-install disabled |
@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 :) |
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. |
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! |
Maybe it's time to think about enabling DNT by default. pros:
cons:
👍 or 👎 ? |
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 |
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 |
|
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. 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. |
DNT vs RFP ("I don't buy this comparison") - I only compared it in terms of putting us in smaller groups
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. |
pros and cons: see #422 (comment) + follow-up comments
Thanks! An interesting read for sure...glad they opened it up |
pros and cons: see arkenfox/user.js#422 (comment) + follow-up comments
pros and cons: see arkenfox/user.js#422 (comment) + follow-up comments
changelog: [all changes]
2600: MISCELLANEOUS
(mostly just reordering and renumbering)updater.sh
online it asks the user whether to download and run it.-donotupdate
to disable the update-check and-update
to auto-download and run the new version without askinguserjs_backups
all pref changes:
4600: RFP (4500) ALTERNATIVES
:9999: DEPRECATED / REMOVED
:Any and all help, suggestions, recommendations, links, tips and tricks, questions, thank you's or whathaveyou are welcome - signup/login and start typing - thanks
The text was updated successfully, but these errors were encountered: