Facebook real-name policy controversy

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Facebook's notification to "update your name"

The Facebook real-name policy controversy refers to the controversy over social networking site Facebook's "real-name system" dictating how people register their accounts and configure their user profiles. The controversy stems from a policy that those who have been adversely affected describe as penalizing users who are in fact using their real names which Facebook has nevertheless deemed to be "fake", while simultaneously allowing anyone to create fake yet plausible-sounding names, as well as obviously implausible-sounding names comprising word combinations that Facebook's software fails to recognize as unlikely to be real. Facebook furthermore prohibits users from accurately representing names which according to the site have "too many words", and prohibits initializing first names, preventing users who do so in real life from formatting their own names as they see fit.

Background

The social networking website Facebook has maintained the real-name system policy for user profiles. According to Facebook, the real-name policy stems from the position "that way, you always know who you're connecting with. This helps keep our community safe."[1][2] Likewise per this policy, a "real name" is defined by "your real name as it would be listed on your credit card, driver's license or student ID."[3] In August 2012, Facebook estimated that more than 83 million Facebook accounts are fake accounts.[4] As a result of this revelation, the share price of Facebook dropped below $20.[5] Facebook has asserted that "authentic identity is important to the Facebook experience, and our goal is that every account on Facebook should represent a real person."[4]

Affected users

Ethnic minorities

Native Americans

Native Americans have been repeatedly targeted due to Facebook's policy.[6]

  • Robin Kills The Enemy, a resident of the Sioux Rosebud reservation in South Dakota, found that when she tried to register her surname in its normal format, the site would not let her use them, so she resorted to combining the three words, spelling them as one word. After having been a member for some time, she eventually contacted the site in an attempt to have her surname spelled as it actually is in real life. However, after reaching out to Facebook, they instead deactivated her account without explanation. When she was finally able to make contact with an actual employee, they wrote back telling her "Fake names are a violation of our Terms of Use. Facebook requires users to provide their full first and last names". She eventually managed to have her account reinstated; however, users with the surname Kills The Enemy are, as of 2015, still required by Facebook to spell their surname without spaces as a single word.[7]
  • Shane Creepingbear, an Oklahoman member of the Kiowa tribe, reported that he had been "kicked off" of Facebook on Columbus Day for having a supposedly fake name.[8]
  • Lance Brown Eyes, an Oglala, found that his account had been suspended; when he was able to send in documentation to Facebook proving his identity, Facebook reinstated his account, but changed his name to "Lance Brown".[9]
  • Dana Lone Hill, a member of the Lakota tribe who had been a registered Facebook user for several years, discovered one day that she had been locked out of her account. A message from Facebook said "it looks like the name on your Facebook account may not be your authentic name". After a week, during which she had to send in her personal documentation to Facebook, her account access was restored. She has since threatened a class-action lawsuit on behalf of Native Americans against Facebook due to how it exercises its name policies.[10]

On October 13, 2014, Native Americans' user profiles—specifically in Yellow Springs, Ohio—were temporarily deactivated.[11][12][13] Native American activists claimed to be planning to file a class action lawsuit against Facebook regarding the 'real name' policy.[14]

Irish

The Dublin branch of the Irish language rights group, Misneach, has started on Change.org online petition to demand that right to use Irish names on Facebook and protested outside Facebook's European headquarters in Dublin on October 7, 2015.[15]

Chamoru

In the Spanish-influenced indigenous Chamoru culture of the Marianas, the standard naming convention has historically been for a person to use their mother's maiden name as their middle name. (Chamoru culture, having been colonized by Spain, went through a period where indigenous names and naming conventions were forcibly eradicated and replaced by what the conquering Spanish deemed acceptable.) Furthermore, using one's full name rather than simply the first and last is commonplace, if only for disambiguation purposes due to a relatively small pool of surnames. Therefore, middle names such as De Leon Guerrero and De La Cruz are frequently encountered. However, attempting to register such names as one's middle name results in a message telling users that "Names can't have too many words." Therefore, many Chamoru users are forced to either run all of the words together as if they were one single word, or to initialize each word to a common acronym such as DLG or DLC.

In cases where the acronym is employed, Facebook automatically changes to lower-case all letters except the first. (Use of periods, e.g. D.L.G., will result in a message telling users that "Profile names can't have too many periods.") Therefore, someone commonly known in real life by a name such as Mary De Leon Guerrero Mafnas would have to resort to using what on Facebook would end up being "Mary Dlc Mafnas". The message is not accompanied by an option to challenge/appeal the restriction, or to send Facebook documentation that the format is how one normally formats their name in real life.

Vietnamese

In January 2015, a 23-year-old Australian bank employee claiming to be named Phuc Dat Bich posted a photo of his passport identification page to Facebook, protesting that the company had unfairly shut down his account for being "false and misleading".[16] "Is it because I'm Asian? Is it?" he asked. The BBC reported that in Vietnamese the name is pronounced similarly to "Phoo Da Bi" (IPA: /fuq˦˥ ɗat˩ ɓic˦˥/).[16] After his reinstatement, Bich posted a thank you note to supportive Facebook fans, stating he was "glad and honoured to be able to make people happy by simply making them laugh at something that appears outrageous and ridiculous".[16] Subsequently "Phuc Dat" published a further message admitting it was a hoax.[17]

Tamils

Tamils do not have surnames, but have their father or mother or both father and mother's first name as initials.[18] This standard naming practice has not been acknowledged by Facebook.[19]

LGBT users

Facebook's real-name policy does not reflect adopted names or pseudonyms used by the LGBT community, and has even led to suspending users with real names that might be thought to be fake.[20] A user via the anonymous Android and iOS app Secret began reporting "fake names" which caused user profiles to be suspended, specifically targeting the stage names of drag queens.[3][21]

Transgender people have also been affected by the policy, including one former Facebook employee who initiated development on Facebook's custom gender options, who was suspended on the day the Supreme Court of the United States ruled in Obergefell v. Hodges that same-sex marriage bans were unconstitutional.[22][23] According to gender non-conforming activist D. Dragonetti, Facebook even disregarded their government identification when supplied.[better source needed][24]

On October 1, 2014, Chris Cox, Chief Product Officer at Facebook, offered an apology to the LGBT community and drag kings and queens:

In the two weeks since the real-name policy issues surfaced, we've had the chance to hear from many of you in these communities and understand the policy more clearly as you experience it. We've also come to understand how painful this has been. We owe you a better service and a better experience using Facebook, and we're going to fix the way this policy gets handled so everyone affected here can go back to using Facebook as you were.[25]

Established online alter-egos

Virtual world artists and business owners have also been targeted by Facebook. Although the use of identities based on online sites such as Second Life and IMVU has been dismissed as video game role playing, many people generate real-world income through these virtual communities.[26]

Reaction

International non-profit digital rights group Electronic Frontier Foundation stated they were "alarmed to hear that Facebook's 'real name' policy is disproportionately affecting the LGBTQ community."[27]

Online magazine Queerty called Facebook's policy "a frankly creepy overreach of authority", adding "There are a million reasons why someone would choose to self-identify with a name other than the one that's printed on their birth certificate. And really, it's absolutely none of your business in the first place."[28]

In an interview for MAGE Magazine, Second Life entrepreneur Jennifer Ceara Firehawk stated: "If we are not using our page to abuse or grief others they just need to leave us be. We are not hurting anyone… FB does not realize some SL people earn lindens to turn into RL (real life) money and that is how they make a living. Once you force a person to change the SL name they will lose money due to not being able to find them on FB or SL as they may use FB for their buisness [sic] or advertise. So they end up losing buisness [sic] and money."[29]

Seattle drag performer Olivia LaGarce started a Change.org online petition titled "Allow performers to use their stage names on their Facebook accounts!"[30][31]

Compromise to protect those with special circumstances

On December 15, 2015, Facebook announced in a press release[32] that it would be providing a compromise to its real name policy after protests from groups such as the gay/lesbian community and abuse victims.[33] The site is developing a protocol that will allow members to provide specifics as to their "special circumstance" or "unique situation" with a request to use pseudonyms, subject to verification of their true identities. At that time, this was already being tested in the U.S. Product manager Todd Gage and vice president of global operations Justin Osofsky also promised a new method for reducing the number of members who must go through ID verification while ensuring the safety of others on Facebook. The fake name reporting procedure will also be modified, forcing anyone who makes such an allegation to provide specifics that would be investigated and giving the accused individual time to dispute the allegation.[34]

As of May 2016, nothing has been offered or modified by Facebook.

List of notable Facebook accounts suspended

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.