Skip to content

An alternative framing for the harms section #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

martinthomson
Copy link
Contributor

In looking at Robin's edits in #123, I was inspired to write something different.

It retains the same basic idea, but tries to avoid some of the hedging language.

That said, hedging is essential here. We're talking about evolutions to the web here and any change comes with consequences, just as not changing does. No action at this scale avoids harms, but we have a framework within which we can make these decisions in the priority of constituencies.

@@ -258,12 +258,12 @@ <h3 id="verify" data-export="" data-dfn-type="dfn">
</h3>
<p>
Society relies on the integrity of public information.
We have a responsibility to build web technologies to counter misinformation
We have a responsibility to build web technologies to counter misinformation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wish whitespace changes weren't mixed in with substantive changes.

@torgo torgo added the next version we have agreed to look at for the next version - previously 'back burner' label Jul 18, 2024
@hadleybeeman
Copy link
Member

@martinthomson we're minded to close this as we don't think it fits together with the language of the rest of the document. The document is very focused on our commitments and aspirations — we've tried to keep the language to a minimum — and it seems like the language you're proposing is descriptive. While we don't disagree with your proposed content, we'd like to keep this document as minimal as we can.

Also in general we think the current version of the document needs to play the role it needs be in use as a Statement for some time before we consider wording changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next version we have agreed to look at for the next version - previously 'back burner'
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants