Cookie-AutoDelete
Rename whitelist to something
In the face of all the current things going on in the world it would be a nice way of showing support by renaming graylist and whitelist to something else. You for sure will be able to give that concept another name that might not carry the co notation that the term whitelist carries with it.
Thanks ❤️ .
While I'd like for this to be an instant change, there is a bit of coding to actually change the entire backend code that uses 'grey' and 'white' (not to mention the locales that will need to be translated on Crowdin as well).
In other words, it will be worked upon, but don't expect anything to be quickly published in the near future (next minor/patch version) or so.
no whitelist is extremely standard, do not change that
- it's be an extremely bad idea to change sometihng that is so standard,
- it'd make this extension more confusing than it already is
this extension does not have good ux/ui design like other extensions and softwares do
- look at how simple + clean other things are, this extensions is so complicated
- the only postiive is that the options has a link that goes to a github section explaining what something does (but it is without pictures like the good extensions have)
whitelist = allowing something that isnt blacklisted, allowing someting outside of the default and whitelist will stay standard forever
naming of greylist should be changed cos it's extremely confusing, and nobody uses the term 'greylist'
Even if they were standard in the past it's time to change them. Companies like Microsoft already do this for a long time. see here for an example of it.
Hurtful language needs to stop. Language can change. To the better. It does not hurt you to use "Allowlist" instead. There is no harm done to you.
In the face of all the current things going on in the world it would be a nice way of showing support by renaming graylist and whitelist to something else. You for sure will be able to give that concept another name that might not carry the co notation that the term whitelist carries with it.
Thanks ❤️ .
Please prioritize features that people actually care about. This comment has only received 3 votes, and yet you claim to support an "instant change?" Complaints about unwanted notifications showing from "manual cleaning" have received over four times as many comments, and yet you say it's "not a big priority at this time?" Why not? How about prioritizing it?
In the face of all the current things going on in the world it would be a nice way of showing support by renaming graylist and whitelist to something else. You for sure will be able to give that concept another name that might not carry the co notation that the term whitelist carries with it. Thanks heart .
Please prioritize features that people actually care about. This comment has only received 3 votes, and yet you claim to support an "instant change?" Complaints about unwanted notifications showing from "manual cleaning" have received over four times as many comments, and yet you say it's "not a big priority at this time?" Why not? How about prioritizing it?
You seem to be mistaken about 'instant change' from my comment of
"While I'd like for this to be an instant change, there is a bit of coding to actually change the entire backend code that uses 'grey' and 'white' (not to mention the locales that will need to be translated on Crowdin as well)."
to which I implied it won't be easy. I also have said
In other words, it will be worked upon, but don't expect anything to be quickly published in the near future (next minor/patch version) or so.
This can also be applied to the other issue about notifications as well...
BTW the more you keep making comments like these, the more time I need to read though and write up responses, which takes time away from what little I already have to code. Keep that in mind please.
Whether terms like “white list” are acceptable or not is not left to the individual, the industry as a whole is considering it as a harmful term. Please read further about what these terms imply: https://www.localizationlab.org/blog/2020/8/19/it-starts-with-words-unconscious-bias-in-gender-race-and-class-in-tech-terminology
If companies like IBM, Microsoft, Autodesk, etc. have decided to temporarily stop software development to prioritize the replacement of all these terms, “Cookie Autodelete” should consider to also make it a priority by respect to its users. I’m afraid that seeing these changes implemented in v4 will push them for many months, sending the message that reforming language, replacing terms that exclude and reinforce oppression in our systems is not so important to the “Cookie Autodelete” dev team.
Wholeheartedly agree with @Chaddock. A simple term which has been in use for years and isn't doing anything bad is "considered harmful". This is beyond reason. 🙄
The fact alone that someone seriously requested that and that it is actually being discussed is astonishing I am afraid. What do they come after next? Cookie? Delete?
Why is it seem there has been no work on this? Fixing https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/issues/711 would make this even harder.
This is beyond reason
Fixing this will actually make the language clearer, as allowlist clearly means a list of allowed domains, while whitelist is extremely confusing until you either look it up or ask someone. Even though I know what it means, it still sounds like a list of white-colored objects. It may take a small time to change for people used to this terminology, but in the end it will improve the UI and UX. Also consider that everyone else is already switching, so still using whitelist will make Cookie Auto Delete hard to use.
[the term whitelist promotes] the racist ideology of “white is good, black is bad”
I think the article posted by @AO-LocLab explains it better than I can
Thanks for your work on Cookie Auto Delete!
The terms white- and blacklist are industry standards and generally understood.
https://en.wiktionary.org/wiki/whitelist
There's no "confusion" and hence no need to change anything.
The terms white- and blacklist are industry standards and generall understood.
https://en.wiktionary.org/wiki/whitelist
There's no "confusion" and hence no need to change anything.
The terms allowlist and denylist are self-explanatory.
An allowlist is a list of allowed domains and a denylist is a list of domains denied access.
You always could use blocklist if that works better or sound better
That does not change what I wrote earlier. The currently used terms are industry standards and it is known what they stand for.
That does not change what I wrote earlier. The currently used terms are industry standards and it is known what they stand for.
What I meant is that allowlist & denylist are not hard to understand.
They are also becoming industry standards as major companies switch to using them
I don't think anybody here argued that they are hard to understand.
The point rather is that there is no need to change anything in the current setup.
And while they might not be hard to understand they still sound awkward, simply because these have never been commonly used terms.
I don't think anybody here argued that they are hard to understand.
The point rather is that there is no need to change anything in the current setup.
And while they might not be hard to understand they still sound awkward, simply because these have never been commonly used terms.
I agree that denylist sound extremally odd and hard to say, but I am sure that as a community we can determine something that works for everyone.
I am going to stop posting any more comments on this thread as to avoid this getting too heated
Locking this issue before it gets heated even more. Judging by the amount of reactions to the first post this isn't on top of the list of things to do at this point.
Denylist isn't the best to use because we are not denying cookies at all. Allow would be fine, though would be non-existent once the below is integrated.
Plans for this includes the ability to have cookies check multiple lists, and lists to be self-configurable and re-nameable.
In addition the backend lists are also hardcoded as 'white' and 'grey' so changing those will take some time to allow users to properly migrate so that the configured lists still work (Kinda learnt that the hard way at one release point). This isn't including the translations for each term.
As a temporary solution to those that want it, I will attempt to add two settings - each will take in a string/text that allows you to 'visually' rename the lists. The imports/exports will still be white or grey, but the visual look in the popup and list of expressions will have the text you put in.
Best of both worlds and a much easier solution to implement.
Unlocking for now, as locking it also prevented emojis/reactions from being used.
@bitboxer, not a single one I am afraid. Only arbitrarily motivated political agendas.
I feel offended by the word cookie, please rename immediately 🙄
Best of both worlds and a much easier solution to implement.
I am sorry, that is still caving in to ridiculous demands. Will you do the same if someone actually demands "cookie" to be renamed or any other string in your application?
Will you do the same if someone actually demands "cookie" to be renamed or any other string in your application?
If somebody wanted to rename cookie, then it would need a lot of visual changes from many browsers and websites, not just this web extension.
For reference, a discussion about this for PiHole: https://discourse.pi-hole.net/t/change-blacklist-and-whitelist-terminology/31657/23
It does not hurt you to use "Allowlist" instead. There is no harm done to you.
"They're only words, not using them can't hurt you", is right up there with, "they're only words, using them can't hurt you".
Hurtful language needs to stop. Language can change. To the better.
"All usage of that word looks the same to me", goes nicely with "they all look the same to me" and "all black people are X".
In your effort to stamp out the pain of bigotry, you've become a bigot, punishing each and every individual for the actions of the racists among us, and employing the same illogical justifications as bigots always do.
Instead of using the concept of lists, I would suggest the concept of events. For example, instead of saying a site is on the white or gray list, I would prefer a site had an auto-clean mode of “On Domain Exited”, “On Tab Closed”, “On Session Ended”, or “Never”. On the UI, we could then set this for a site using an option-cicler button with an optional dropdown button. Also, a tooltip on the button, describing what the hovered auto-clean mode represents, would be more user-friendly/inclusive.
I suggest this, not because of cultural concerns, but because it looks more clear about the functionality we are configuring. The concept of white and gray lists doesn't seem clear enough to me. When I first started using CAD, I had to read the documentation to understand what does it mean for a site to be on the gray list, for example. I recommended CAD for people I know, but they found it confusing and stop using it. They said they didn't like it, but I'm sure they just didn't understand how it works.
@AderitoSilva, I'd argue it should be pretty clear what whitelist should mean/do. A list of exceptions where a certain functionality is not applied. As far as greylist is concerned, I do agree its meaning could be a bit ambiguous.
Having said all that, I do believe your suggestion is a viable "compromise" as it does not try to pursue an agenda and shift things around or no reason, but it's more of a feature enhancement in general. As I understand it even adds functionality which is currently not present. But I also believe this should warrant its own issue entry here.
I like the idea of @AderitoSilva, as it tells what the function actually does. Changing the words white/black to something different will not change peoples mind. (kidding a bit: looking at a traffic light, red for "stop" hurts Russians, yellow for "take care" hurts Asien ppl, green for "go" might make vegans happy :-)
Big companies doing the changes now, want to sell something, I don't think its changing their mindset. Making the strings configurable is more work and might bring more confusion. I think it would be better to put development time into the desired function of CAD.
Black could be understood as night, white as day, not necessarily what we are talking about here.
Apologies for the rather long delay. Initial commit has been changed to simple language term adjustments in linked PR. I will need some time to propagate the adjustments into the actual codebase.
TL;DR:
- WhiteList -> KeepList
- GreyList -> RestartList
- List of Expressions -> List of Exceptions
All right, your decision of course, will switch to https://addons.mozilla.org/en-GB/firefox/addon/forget_me_not/ though
Not only did you not take @AderitoSilva's suggestion into account, you even ignored your own idea of making the name customisable but went the Full Monty and continued wiping out perfectly acceptable words to cater to some political idealogies.
Again, your decision, but also mine to switch to https://addons.mozilla.org/en-GB/firefox/addon/forget_me_not/