Ability to replace obsolete default whitelist entries

[Mc]

How does the new ability to replace obsolete default whitelist entries work? Do I miss something in Options?

[redwolfe_98]

i was wondering about that too.. i have always deleted the "default whitelist" entries and replaced them with my own whitelist entries..

[WhatItSays]

I read back in the Updates feed

Code: Select all

http://noscript.net/feed?c=200&t=a

Replaced browserid.org with persona.org in the default whitelist

The replace obsolete default whitelist entries seems self-evident: if a whitelist item supplied by the developer becomes obsolete, it's his responsibility to either delete or replace it.
Natch, if you don't have that particular default whitelist entry in your config, then it won't affect your config.

The update is an example of just how well Giorgio looks after his users: he knows that most power users will wipe his default whitelist and so he has taken the trouble to interrogate individual entries, rather than do a full whitelist update, with all the whinging that might produce .

[GµårÐïåñ]

What are you guys babbling about obsolete whitelist entries? If its a default by NoScript then likely its left over from you upgrading NoScript over the same profile for a long time. Save your whitelist, do a reset and reimport and you are now using the new default whitelist. Or just manually delete them. The developer does and has always maintained a clean list, if you don't have one, then you haven't maintained your profile, not his problem.

[Thrawn]

What are you guys babbling about obsolete whitelist entries?

I believe that they're referring to the first changelog item for 2.4.9:

v 2.4.9
=========================================================================
+ Added ability to replace obsolete default whitelist entries

And I'm curious myself; this sounds like something more than just Giorgio issuing an update to the default whitelist. And users were already able to remove any whitelisted entries (except chrome etc).

Does this mean that 2.4.9 adds a mechanism whereby future updates can intelligently alter the default whitelist?

[GµårÐïåñ]

No matter changes the whitelist default or otherwise, I don't believe Giorgio as a matter of respect for user decision will EVER automatically remove something from someone's list under the presumption that they might very well want it there and removing it would adversely affect them. So they need to remove it manually, clean install, or do what I suggested, export, reset, import and then be up to par with where we are or manually using about:config to remove what they don't want; like I have been along with hundreds of thousands of others for years.

[Giorgio Maone]

The specific case: browserid.org had been added to the default whitelist because many sites (starting with Mozilla's properties, but hopefully expanding beyond) adopted the BrowserID clever sign-on mechanism, but the need for the domain to be whitelisted is not self-evident (the signon window is displayed without a navigation bar) and therefore the login experience might be frustrating to most users.

Recently the technlogy has been renamed as "Persona", and the domain has changed from "browserid.org" to "persona.org". For the time being, there's a redirection in place which sends you to the new domain if needed, but there's no guarantee that in future the browserid.org is not used for other purposes which cannot justify its permanence in the whitelist.

Therefore if this update finds browserid.org in your whitelist, it changes it to persona.org to spare you troubles in future, when browserid.org goes unmaintained or, worse, falls in bad hands.

[therube]

(Well that, the changelog, was clear as mud .)

[Non-Whinger]

It was too clear, therube, so it needed muddying with a thread
More words = less meaning.

Bingo! the visual confirmation on this post included "Socrates"

[therube]

Revised in the changelog:

Code: Select all

x Replaced browserid.org with persona.org in the default whitelist

Now that is clearer.