Thank you members of the Commerce Committee for the opportunity to speak with the American people about Twitter and §230. My remarks will be brief to get to questions. §230 is the most important law protecting internet speech. Removing §230 will remove speech from the internet.

§230 gave internet services two important tools. The first provides immunity from liability for user’s content. The second provides “Good Samaritan” protections for content moderation and removal, even of constitutionally protected speech, as long as it’s done “in good faith.”
That concept of “good faith” is what’s being challenged by many of you today. Some of you don’t trust we’re acting in good faith. That’s the problem I want to focus on solving. How do services like Twitter earn your trust? How do we ensure more choice in the market if we don’t?
There are three solutions we’d like to propose to address the concerns raised, all focused on services that decide to moderate or remove content. They could be expansions to §230, new legislative frameworks, or a commitment to industry wide self-regulation best practices.
The first is requiring a service’s moderation process to be published. How are cases reported and reviewed? How are decisions made? What tools are used to enforce? Publishing answers to questions like these will make our process more robust and accountable to the people we serve.
The second is requiring a straightforward process to appeal decisions made by humans or algorithms. This ensures people can let us know when we don't get it right, so that we can fix any mistakes and make our processes better in the future.
And finally, much of the content people see today is determined by algorithms, with very little visibility into how they choose what they show. We took a first step in making this more transparent by building a button to turn off our home timeline algorithms. It’s a good start.
We’re inspired by the market approach suggested by Dr. Stephen Wolfram before this committee in June 2019. Enabling people to choose algorithms created by third parties to rank and filter their content is an incredibly energizing idea that’s in reach. https://t.co/Oavx4xVskC
Requiring 1) moderation process and practices to be published, 2) a straightforward process to appeal decisions, and 3) best efforts around algorithmic choice, are suggestions to address the concerns we all have going forward. And they’re all achievable in short order.
It’s critical as we consider these solutions, we optimize for new startups and independent developers. Doing so ensures a level playing field that increases the probability of competing ideas to help solve problems. We mustn’t entrench the largest companies any further.
Thank you for the time, and I look forward to a productive discussion to dig into these and other ideas.

More from Tech

A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.

You May Also Like

1

From today, we will memorize the names of 27 Nakshatras in Vedic Jyotish to never forget in life.

I will write 4 names. Repeat them in SAME sequence twice in morning, noon, evening. Each day, revise new names + recall all previously learnt names.

Pls RT if you are in.

2

Today's Nakshatras are:-

1. Ashwini - अश्विनी

2. Bharani - भरणी

3. Krittika - कृत्तिका

4. Rohini - रोहिणी

Ashwini - अश्विनी is the FIRST Nakshatra.

Repeat these names TWICE now, tomorrow morning, noon and evening. Like this tweet if you have revised 8 times as told.

3

Today's Nakshatras are:-

5. Mrigashira - मृगशिरा

6. Ardra - आर्द्रा

7. Punarvasu - पुनर्वसु

8. Pushya - पुष्य

First recall previously learnt Nakshatras twice. Then recite these TWICE now, tomorrow morning, noon & evening in SAME order. Like this tweet only after doing so.

4

Today's Nakshatras are:-

9. Ashlesha - अश्लेषा

10. Magha - मघा

11. Purvaphalguni - पूर्वाफाल्गुनी

12. Uttaraphalguni - उत्तराफाल्गुनी

Purva means that comes before (P se Purva, P se pehele), and Uttara comes later.

Read next tweet too.

5

Purva, Uttara prefixes come in other Nakshatras too. Purva= pehele wala. Remember.

First recall previously learnt 8 Nakshatras twice. Then recite those in Tweet #4 TWICE now, tomorrow morning, noon & evening in SAME order. Like this tweet if you have read Tweets #4 & 5, both.