Meta: Difference between revisions
Copy editing |
Added further information about that the Meta Quest headsets are not usable at all if you don't connect them to the internet and create an login an account. If Meta decides to kill the headsets to generate more profit they just need to disable the login so new customers and customers who reset their software are left with a bricked piece of trash. |
||
Line 23: | Line 23: | ||
In August 2022, following public backlash, Meta reversed the policy, allowing users to sign in with a new "Meta account" instead of a Facebook account.<ref>[https://www.pcgamer.com/finally-the-quest-2-no-longer-requires-a-facebook-login/ "Finally, the Quest 2 no longer requires a Facebook login"] - pcgamer.com - 24 Aug 2022</ref> This, however, did not prevent several original Oculus accounts from being deleted or suspended, with Facebook users being locked out of their headsets for two years. | In August 2022, following public backlash, Meta reversed the policy, allowing users to sign in with a new "Meta account" instead of a Facebook account.<ref>[https://www.pcgamer.com/finally-the-quest-2-no-longer-requires-a-facebook-login/ "Finally, the Quest 2 no longer requires a Facebook login"] - pcgamer.com - 24 Aug 2022</ref> This, however, did not prevent several original Oculus accounts from being deleted or suspended, with Facebook users being locked out of their headsets for two years. | ||
Additionally to all of this the headsets are not usable at all without connecting them to the Internet and logging them into a Meta/Facebook account when the owner wants to use it for the first time after purchase. This creates the risk that the headsets will be indefinitely unusable, or at least not to be able to be set up after a reset of the software, if Meta theoretically decides to shutdown the authentication or login servers. | |||
===''Echo VR'' shutdown and Ready At Dawn=== | ===''Echo VR'' shutdown and Ready At Dawn=== | ||
Line 39: | Line 41: | ||
In July 2019, Facebook agreed to pay $5 billion USD and implement corrective measures after it was sued by the Department of Justice and Federal Trade Commission (FTC) for "misleading users about the extent to which third-party application developers could access users' personal information."<ref>[https://www.justice.gov/opa/pr/facebook-agrees-pay-5-billion-and-implement-robust-new-protections-user-information "Facebook Agrees to Pay $5 Billion and Implement Robust New Protections of User Information in Settlement of Data-Privacy Claims"] - justice.gov - 24 Jul 2019</ref> | In July 2019, Facebook agreed to pay $5 billion USD and implement corrective measures after it was sued by the Department of Justice and Federal Trade Commission (FTC) for "misleading users about the extent to which third-party application developers could access users' personal information."<ref>[https://www.justice.gov/opa/pr/facebook-agrees-pay-5-billion-and-implement-robust-new-protections-user-information "Facebook Agrees to Pay $5 Billion and Implement Robust New Protections of User Information in Settlement of Data-Privacy Claims"] - justice.gov - 24 Jul 2019</ref> | ||
==== Controversy over default privacy settings (2010–2018) ==== | ====Controversy over default privacy settings (2010–2018)==== | ||
Facebook's default settings allowed third-party app developers to access not only the data of users who installed their apps, but also the data of those users' friends. While users could opt out of this data sharing, the setting was located separately from the main privacy settings page, making it difficult to find and adjust.<ref name=":0">"[https://www.justice.gov/opa/press-release/file/1186506/dl United States of America v. Facebook, Inc., Case No. 19-cv-2184, Complaint for civil penalities, injunction, and other relief"] PDF - justice.gov - 24 Jul 2019</ref> | Facebook's default settings allowed third-party app developers to access not only the data of users who installed their apps, but also the data of those users' friends. While users could opt out of this data sharing, the setting was located separately from the main privacy settings page, making it difficult to find and adjust.<ref name=":0">"[https://www.justice.gov/opa/press-release/file/1186506/dl United States of America v. Facebook, Inc., Case No. 19-cv-2184, Complaint for civil penalities, injunction, and other relief"] PDF - justice.gov - 24 Jul 2019</ref> | ||
Line 46: | Line 48: | ||
While Facebook publicly announced in 2014 that it would stop allowing third-party developers to collect data about users' friends, it privately maintained agreements with dozens of "whitelisted developers" who continued to have this access until June 2018.<ref name=":0" /> | While Facebook publicly announced in 2014 that it would stop allowing third-party developers to collect data about users' friends, it privately maintained agreements with dozens of "whitelisted developers" who continued to have this access until June 2018.<ref name=":0" /> | ||
==== Deceptive two-factor authentication (2015–2018) ==== | ====Deceptive two-factor authentication (2015–2018)==== | ||
Facebook requested users' phone numbers for security purposes, including two-factor authentication, without effectively disclosing that this information would also be used for advertising purposes.<ref name=":0" /> | Facebook requested users' phone numbers for security purposes, including two-factor authentication, without effectively disclosing that this information would also be used for advertising purposes.<ref name=":0" /> | ||