Closed Bug 1713842 Opened 3 years ago Closed 3 years ago

Deprecate Master Password; Replace with Prime Password (or other suggestion)

Categories

(Invalid Bugs :: General, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1649482

People

(Reporter: sj, Unassigned)

Details

+++ This bug was initially created as a clone of Bug #1713483 +++

+++ This bug was initially created as a clone of Bug #1649482 +++

The term "master" in software makes reference to the "Master/Slave" relationship. As one action to uproot this problematic terminology (see Meta bug), we are replacing the term Master Password with Prime Password

See Transvision for instances of where this term appears in SeaMonkey.

+++++

Recreating this bug, because the reasons for not changing given in the still-open ticket (on which comments have been closed) were clearly all made by men who cannot or will not empathize with the injury caused by the colonial and Jim Crow era popularization of the word "master" as terminology.

While the etymology does include non-enslavement based usage, the fact that it is inextricably tied to slavery and other oppressive regimes, such as in the case of "Master Race", and that better or more accurate terms do in-fact exist, along with the evidenced notion that the tech industry as a whole is changing, should be reason enough to change this term.

The etymology since the 14th century, however, is largely related to "the controlling and disposing of animals which one owns" especially dogs and slaves, with only secondary usages as reference to excelling in a subject, all originating from Magister. https://www.etymonline.com/word/master

Indeed, it is reasonable and expected that higher education will be changing their usage of the term to something appropriate, as quick research suggests that the term was originally "Magister", and that modern usage of the term 'Master' as we do today in education originates no earlier than 1870.
https://www.historians.org/about-aha-and-membership/aha-history-and-archives/historical-archives/retrieving-the-masters-degree-from-the-dustbin-of-history-(2005)/i-a-(very)-brief-history-of-the-masters-degree

Deep research suggests that the Colonial Army of the United States did not have a rank of Master Sergeant, even though the colonizing Queens Navy did have one such rank, and that the first references to such in American history were in the Confederate Army during the American Civil War. The term was codified in 1920, which does not seem "coincidental" when in the context of Jim Crow, and considering the treatment of black men in the military at the time. I do expect that even though the military is steeped in tradition and that the rank has been written into NATO designation, that the military will find another term for their rank in time, as well.

Based on the above, I can't imagine the auto industry will continue to create "slave cylinders" for much longer, instead finding new term going forward, too, though because of the naming of historical parts, this will take longer to promulgate.

While "primary password" may imply a secondary password, a short think reveals that "Prime Password" may be a better term, which does not imply a secondary password. We can do better if we put our minds to solving issues, rather than thinking on how to reframe a suggestion as a problem itself. If one has a problem with the term, it would be best to suggest another term than to simply find reasons the suggestions is wrong. This is the essence of "being constructive" rather than being a blocker to progress.

Simply because others have not yet changed is not a reason to not improve yourself. "We've always done it this way" is one of the most dangerous phrases in the English language, as most software developers should already know.

++++++++

It is summarily offensive that this bug is closed as a duplicate (when it is a "clone" of another bug) without discussion, and that the previous discussion ignores all reasoning presented here and in the other previous bugs.

Terms which may be alienating should be changed or considered. The list of those who have already had this very discussion and changed is long.

Mozilla is historically a progressive organization. It is shocking to see the previous bug report closed without context or discussion.

Repeating for emphasis, to ensure it is actually read:

It is summarily offensive that this bug be closed as a duplicate (when it is a "clone" of another bug) without discussion, and that the previous discussion ignores all reasoning presented here and in the other previous cloned bugs.

Terms which may be alienating should be changed or considered. The list of those who have already had this very discussion and changed is long.

Mozilla is historically a progressive organization. It is shocking to see the previous bug report closed without context or discussion.

Posting this because the most vocal person on these tickets repeatedly denies a problem, even though the very math that binary math is based on: logic, insists that proving something is false is impossible, one can only prove truthiness. This is why null does not equate to null.

This has been a systemic issue since before most of us were even born. Why is everything black and white?
Why even use terms that normalize a "master" relationship? ...especially when there are other terms which are arguably more descriptive?

If one needs reference, here is Mohammed Ali:
https://www.bbc.com/news/av/world-us-canada-52988605

Note that "arguably" means that in the least a discussion should be had, which should also consider that many people have already been alienated from that discussion. No reason to further alienate people.

Lastly, the discussion should go on. I don't see, at all, how an old thread that disallows comments is any kind of ongoing discussion.
The fact is that "master" is a loaded term, with connotations as well as problematic etymology. It demonstrably normalizes problematic things.

I cannot imagine this would be desired to be continued, even if you think the word is already "perfect".

It is enough. The first bug is open and New. This is not a debate club and we are all against racisim if this is unclear.

Product: SeaMonkey → Invalid Bugs

I did seem unclear, since there were enough such comments on the thread for the open ticket (which has closed comments for, presumably, the number of people who were offended by the mere suggestion of impropriety in naming)

We are at a time in history when the number of people willing to engage in this change is at an all time low, and this is absolutely shameful.

This was made so obviously necessary a year ago, and for about two months a lot of lip service was paid by many corporations and organizations, and then nothing was done, at all. This is not conjecture, there are real facts behind it. This ticket still remaining open 11 months later is further evidence of that shift in priorities.

And this has been a problem for over 150 years, which is why so many don't even see the problems today: they are used to it and many do not expect any change at all anymore. It worked, these people have been disenfranchised. Even getting vaccinations to the black community was damaged by campaigns that fraudulently infected black people as part of inhumane medical testing. It goes deep. It's not a leap to see that the word "master" is a word that came into vastly popular usage in these contexts again beginning in the 1870s. It's a subtle but effective jab and it's time for it to end.

I'm not calling anyone racist, I'm simply asking to fix a term that is genuinely problematic, whether you believe me or not. Much like science and math, it doesn't matter if you believe in it, it still is.

I do see in Transvision that there are now references to Primary Password, which is good. It's unclear in any of these tickets why the original was still open, and it is not fully confirmed anywhere referenced that this has been implemented in public releases.

Thank you for attending to this genuinely important matter.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.