Replace the terms whitelist and blacklist with alternatives

[Mike-J-W]

1. What is not working as documented?

The issue is the use of the terms "whitelist" and "blacklist", which are racially loaded and not inclusive. These terms are in the documentation and I'm guessing they might be used in the code as well.

2. How can we reproduce it?

You can see an example here, in the last bullet point: https://docs.photoprism.app/user-guide/organize/people/#when-a-face-was-not-detected

3. What behavior do you expect?

The terms "whitelist" and blacklist" should be changed to terms that are more direct and which lack racial connotations, such as "allowlist" and "blocklist". This is also becoming the industry standard, https://www.vice.com/en/article/v7dd3d/we-need-to-stop-saying-blacklist-and-whitelist.

4. What could be the cause of your problem?

n/a

5. Can you provide us with example files for testing, error logs, or screenshots?

n/a

6. Which software versions do you use?

n/a

7. On what kind of device is PhotoPrism installed?

n/a

8. Do you use a Reverse Proxy, Firewall, VPN, or CDN?

n/a

[lastzero]

Please do not use bug tickets for telling us this because the time we need to manage those could be used instead to improve our docs as you suggested. Thank you! ❤️

[lastzero]

@Mike-J-W @GlassedSilver Despite all the other work already on our plate and no help from the reporter or our community, I was able to go through our entire codebase today to replace the term blacklist with alternatives. Now that this is done, the documentation can also be updated (and not the other way around).

I stand by our policy to not use a bug ticket to get priority and/or more attention for demands. We're working as fast as we can, and it's not getting any faster this way. Thank you for your careful consideration! 👍

[lastzero]

Note that the configuration reference does not need to be updated manually as it will be updated automatically with our next release.