There& #39;s a good argument Mark Zuckerberg should be personally liable for much of the property destruction and harm taking place across the United States.
The argument here is that Facebook is not a speech platform, it& #39;s a product, and it should face product liability claims for the harm it causes. There are enough instances of & #39;rumors spread on social media& #39; leading to violence to show what& #39;s happening. https://twitter.com/matthewstoller/status/1300104029075369984">https://twitter.com/matthewst...
One of the smartest lawyers @cagoldberglaw focusing on tech platforms sees these corporations as offering defectively designed products. They are not platforms for speech. Facebook/Twitter are simply unsafe products. https://twitter.com/cagoldberglaw/status/1184641323481157633?s=20">https://twitter.com/cagoldber...
Former Googler @tristanharris has accumulated a large stock of research on how these products addict and harm adults and especially children. These are *products.* Social media should be regulated in part under product liability law. https://ledger.humanetech.com/ ">https://ledger.humanetech.com/">...
It& #39;s fun to watch the meltdown from elite corporate lawyers like @tedfrank as I point out a very obvious reality about how Facebook works. Their snotty legal posture is in fact a defense of mass murder (in Myanmar and increasingly elsewhere), property destruction and mass harm.
Zuckerberg continually apologizes for failure when Facebook induces harm. His employees are angry that the corporation& #39;s services foster certain types of behavior. Sean Parker even admitted that the company& #39;s services are addictive.
Legal sneering doesn& #39;t mitigate reality.
Legal sneering doesn& #39;t mitigate reality.
If Facebook had been held liable for the genocide in Myanmar it helped induce years ago, we wouldn& #39;t be facing the constant and endless & #39;rumors spread on social media led to XYZ conflict& #39; dynamic. https://www.nytimes.com/2018/10/15/technology/myanmar-facebook-genocide.html">https://www.nytimes.com/2018/10/1...