Article 549Q8 Facebook's Mark Zuckerberg Accused of Setting Dangerous Precedent

Facebook's Mark Zuckerberg Accused of Setting Dangerous Precedent

by
martyb
from SoylentNews on (#549Q8)
Zuckerberg Accused of Setting Dangerous Precedent

upstart writes in with an IRC submission:

Zuckerberg accused of setting dangerous precedent:

Mark Zuckerberg is setting a "dangerous precedent" by allowing a post by Donald Trump to remain on Facebook, a group of civil rights leaders has warned.

[...] In the post, the president wrote he would "send in the National Guard", and warned that "when the looting starts, the shooting starts".

Mr Trump shared the same message on Twitter, where it was hidden behind a warning label, prompting an escalating row between Twitter and the White House.

Mr Zuckerberg had previously defended his decision to leave the same post up on Facebook, saying he disagreed with Mr Trump's words but that people "should be able to see this for themselves".

After meeting Mr Zuckerberg, three civil rights leaders responded that he was wrong.

[...] The joint statement, released on Monday night, was signed by Vanita Gupta, president of the Leadership Conference on Civil and Human Rights; Sherrilyn Ifill, director-counsel of the NAACP Legal Defense and Educational Fund; and Rashad Robinson, president of Color of Change. It has been published online by Axios.

A Facebook spokesman said: "We're grateful that leaders in the civil rights community took the time to share candid, honest feedback with Mark and Sheryl [Sandberg, Facebook's COO].

Mark Zuckerberg on Leaked Audio: Trump's Looting and Shooting Reference "Has no History of Dogwhistling

aristarchus writes:

Mark Zuckerberg on leaked audio: Trump's looting and shooting reference "has no history of being read as a dog whistle":

Read more of this story at SoylentNews.

External Content
Source RSS or Atom Feed
Feed Location https://soylentnews.org/index.rss
Feed Title SoylentNews
Feed Link https://soylentnews.org/
Feed Copyright Copyright 2014, SoylentNews
Reply 0 comments