惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
V2EX
C
Check Point Blog
博客园 - Franky
月光博客
月光博客
T
Tenable Blog
博客园 - 聂微东
Cyberwarzone
Cyberwarzone
The GitHub Blog
The GitHub Blog
C
CERT Recently Published Vulnerability Notes
Scott Helme
Scott Helme
IT之家
IT之家
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
CXSECURITY Database RSS Feed - CXSecurity.com
F
Full Disclosure
博客园 - 司徒正美
Project Zero
Project Zero
Y
Y Combinator Blog
A
Arctic Wolf
美团技术团队
博客园 - 叶小钗
S
Securelist
F
Fortinet All Blogs
T
Threatpost
T
Threat Research - Cisco Blogs
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
酷 壳 – CoolShell
酷 壳 – CoolShell
MyScale Blog
MyScale Blog
大猫的无限游戏
大猫的无限游戏
Recorded Future
Recorded Future
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
S
Schneier on Security
Apple Machine Learning Research
Apple Machine Learning Research
L
LangChain Blog
P
Privacy International News Feed
博客园_首页
S
SegmentFault 最新的问题
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
腾讯CDC
P
Proofpoint News Feed
Cisco Talos Blog
Cisco Talos Blog
AWS News Blog
AWS News Blog
阮一峰的网络日志
阮一峰的网络日志
G
Google Developers Blog
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
雷峰网
雷峰网
P
Proofpoint News Feed
Latest news
Latest news
G
GRAHAM CLULEY

remy sharp's l:inks

Deno Style Guide Easy 6502 by skilldrick Profiling React.js Performance BEM Naming Cheat Sheet by 9elements Visual 6502 Remix Elijah Manor (@elijahmanor) on X All – Tiny Helpers AST explorer Insecure How to Authenticate with Next.js and Auth0: A Guide for Every Deployment Model Revealed: quarter of all tweets about climate crisis produced by bots I Add 3-25 Seconds of Latency to Every Page I Visit GitHub - ericchiang/pup: Parsing HTML at the command line Browserling – Online cross-browser testing Error Handling with GraphQL and Apollo Schwerkraftprojektionsgerät How To Turn Off Catalina Update Notifications (Prompts & Badges) • macReports Maskable.app It’s 2020 and you’re in the future Emulators written in JavaScript | Frederic Cambus The Size of Space systemfontstack JavaScript isn’t always available and it’s not the user’s fault Programming Fonts - Test Drive Screen Size Map GitHub - Yonet/MixedRealityResources: Mixed Reality related resources The Lines of Code That Changed Everything Notes from the Internet Health Report 2019 CopyPalette Generative Artistry Profile a React App for Performance nanoSQL 2 Moving Your JavaScript Development To Bash On Windows — Smashing Magazine Startup Playbook How to Release a Custom React Component, Hook or Effect as an npm Package React Suite - Enterprise React UI Component Library Use VSCode Dimmer to Highlight Code when Teaching 3 simple rules for effectively handling dates and timezones Large collection of how to animate pixelart Accessible React component libraries mineral-ui.com Australian Government Design System Reakit – Toolkit for building accessible UIs Chakra UI Curl Cookbook The problem with tooltips and what to do instead GitHub - trimstray/the-book-of-secret-knowledge: A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more. It Form design: from zero to hero all in one blog post Brussels changes its mind AGAIN on .EU domains: Euro citizens in post-Brexit Britain can keep them after all Improve Your Email Campaigns with These Fantastic Tools Old Typewriter Text Effect Bruce Lawson Google open sources standardized code in bid to become Mr Robots.txt Preferreds-color-scheme:你好,黑暗,我的老朋友  |  Articles  |  web.dev Free for Developers Startup idea checklist Developing a Robust Font Loading Strategy for CSS-Tricks—zachleat.com How I use Slack—alone—to get more done Upcoming proposals in JavaScript 🦄 VueJS is dead, long live VueJS! Bruce Lawson Answers for young people - Tim Berners-Lee Finally, an AI that can reliably catch and undo Photoshop airbrushing. Who made it? Er, Photoshop maker Adobe Qubyte Codes - How I schedule posts using GitHub Actions Games and Graphics in Popup URL bars Stack 58 bytes of css to look great nearly everywhere The reduce ({...spread}) anti-pattern - RichSnapp.com The Online Disassembler CSS Gradient – Generator, Maker, and Background Chrome DevTools  |  Chrome for Developers HB88 | Đăng Nhập HB88 Cá Cược Nhanh Chóng Không Bị Chăn #1 Introducing React Apollo 2.1 - Apollo GraphQL Blog Color Palettes Generator and Color Gradient Tool Clément Chastagnol ~ Moving efficiently in the CLI Testing Async Components · Issue #346 · enzymejs/enzyme Game Platforms recent news | Game Developer Professional Sound Effects - Royalty-Free SFX | Unlimited Downloads entr(1) Learn React From The Comfort Of Your Browser Axe Rules | Deque University Record and share your terminal sessions, the simple way Web Design Museum Powerful New Additions to the CSS Grid Inspector in Firefox Nightly – Mozilla Hacks - the Web developer blog Latency | Apex Software HackerNoon Signals and Sine Waves (Learn Web Audio from the Ground Up, Part 1) JavaScript Systems Music Vintage bits on cassettes Microsoft Design Legal Documents & Contract Templates | Simply Docs create-graphql-server — instantly scaffold a GraphQL server GraphQL and MongoDB — a quick example Using GraphQL with MongoDB Your First GraphQL Server Build a GraphQL server from scratch Practical Redux, Part 3: Project Planning and Setup 架构标记测试工具 | Google 搜索中心  |  Search Central  |  Google for Developers Freesound
Ethical Web Principles
Daniel Appelquist (Invited Expert) · 2019-07-13 · via remy sharp's l:inks

Abstract

The web should be a platform that helps people and provides a positive social benefit. As we continue to evolve the web platform, we must therefore consider the consequences of our work. The following document sets out ethical principles that will drive W3C's continuing work in this direction.

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document is a Technical Architecture Group (TAG) Finding. It does not contain any normative content.

This document reflects the consensus of the TAG at the time of publication. It will continue to evolve and the TAG will issue updates as often as needed.

This document was published by the Technical Architecture Group as a Statement using the Note track.

A W3C Statement is a specification that, after extensive consensus-building, is endorsed by W3C and its Members.

The W3C Patent Policy does not carry any licensing requirements or commitments on this document.

This document is governed by the 03 November 2023 W3C Process Document.

The web should empower an equitable, informed, and interconnected society. It has been, and should continue to be, designed to enable communication and knowledge-sharing for everyone. In order for the web to continue to be beneficial to society, we need to consider the ethical implications of our work when we build web technologies, applications, and sites.

The web is made up of a number of technologies and technical standards. HTML, CSS, and JavaScript are often thought of as the web's core set of technologies but there are many other technologies, standards, languages and APIs that come together to form the "web platform." We strive to maintain a strong ethical framework as a differentiator for the web platform, for example an emphasis on internationalization, accessibility, privacy, and security. Web technologies are also released for use under a royalty-free license to enable open source implementation. We build new web technologies in a collaborative manner according to open processes (for example, the W3C process), and in inclusive environments adhering to codes of conduct (such as the W3C Code of Conduct).

These are often cited as some of the strengths of the web. Despite this, in the 30 years since the development of the web began, it has become clear that the web platform can often be used in ways that subvert its original mission or even be used to cause harm.

The architecture of the web is designed with the notion of different classes of application that retrieve and process content, and represent the needs of the application's users. This includes web browsers, web-hosted applications such as search engines, and software that acts on web resources. This lends itself well towards empowering people by allowing them to choose the browser, search engine, or other application that best meets their needs (for example, with strong privacy protections).

The web should also support human rights, dignity, and personal agency. We need to put internationally recognized human rights at the core of the web platform [UDHR]. We can reinforce this approach by promoting ethical thinking across the web industry.

The principles in this document are deliberately unordered, and many are interconnected with each other. They are intended to be read together, rather than each in isolation, and to collectively support a web that is beneficial for society. When the effects of upholding one principle may diminish the efficacy of another principle, the benefits and tradeoffs need to be carefully balanced. It is important to consider the context in which the technology is being applied, the expected audience(s) for the technology, who the technology benefits and who it may disadvantage, and any power dynamics involved (see also the priority of constituencies).

This is a statement of the ethical principles of the W3C community. Spec developers, authors, and reviewers can use it to guide their thinking. In particular, the purpose of this document is to inform wide review of new charters, new specifications, and updates to published recommendations. Others can read this document to understand how we are informing our design process with ethical considerations.

For actionable guidance applicable to spec editors, site authors, and others designing and building parts of the web platform, see the Web Platform Design Principles, Self-Review Questionnaire: Security and Privacy, the Privacy Principles, and TAG Findings.

When we are adding new web technologies and platforms, we will build them to cross regional and national boundaries. People in one location should be able to view web pages from anywhere that is connected to the web.

When we are adding a feature or technology to the web, we will work to prevent or mitigate any harm it might cause society or groups, especially to vulnerable people. We consider a range of threat models that account for abuse scenarios at different scales, from societal to interpersonal. We will prioritize potential benefits for web users over potential benefits to web developers, content providers, user agents, advertisers, or others in the ecosystem, in line with the priority of constituencies. We commit to learning about and understanding diverse perspectives, and will strive to reflect a respect for that diversity in the designs we produce, so that our designs properly respect the interests and views of all of the people who might be affected by them.

We are building technologies and platforms for distributing ideas, for virtual interaction, and for mass collaboration on any topic. While those tools can be used for good, they can also be used for spreading misinformation, revealing private personal information (doxing), harassment, and persecution. We will consider these risks in the work we do, and will build web technologies and platforms that respect individuals' rights and provide features to empower them against dangers like these.

People should not need a high level of technical literacy to use the web. Web platform technologies should behave consistently and intuitively. We will build internationalization and localization capabilities into our specifications and websites, including support for different languages. Our specifications and websites are well internationalized, provide support for language and cultural adaptation, and support localization, so that our work is accessible to all users, regardless of language, writing system, or culture. We will accommodate people on low bandwidth networks and with low specification equipment. The web platform and the tools we use to create it must be accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Anyone should be able to meaningfully participate in the creation of specifications, user agents, and content, and the platform should enable a fully accessible end-user experience.

When we add features to the web platform, we are making decisions that impact people's ability to control their personal data. This data includes their conversations, their financial transactions and how they live their lives. We will start by creating web technologies that create as few potential threats to web users as possible, and mitigate the threats that we cannot avoid. We will make sure people understand what risks they are taking when they use the web.

We will create web technologies and platforms that encourage free expression. Our work should not enable state censorship, surveillance or other practices that seek to limit this freedom. This principle must be balanced with respect for other human rights and does not imply that individual services on the web must therefore support all speech.

Society relies on the integrity of public information. We have a responsibility to build web technologies to counter attempts to mislead, deliberate or inadvertent, and to maintain the integrity of information for public good. The public needs verifiable source and context information to recognize trustworthy web publishers and content. The concept of origin and its relationship with information sources are core to the web's security model.

We recognize that web technologies can be used to manipulate and deceive people, complicate isolation, and encourage addictive behaviors. We seek to mitigate against these potential abuses and patterns when creating new technologies and platforms, and avoid introducing technologies that increase the chance of people being harmed in this way. We aim to reduce centralization in web architecture, minimizing single points of failure and single points of control. We will also build web technologies for individual developers as well as for developers at large companies and organizations. The web should enable do-it-yourself developers.

Web technologies may have overall positive environmental impacts as well as negative impacts. These can change over time and vary geographically as both web and environmental technologies develop. We will endeavor not to do further harm to the environment when we introduce new technologies to the web and keep in mind that people most affected by the environmental consequences of new technologies may not be those who benefit from the features introduced. This includes, but is not limited to, lowering carbon emissions by minimizing data storage and processing requirements, as well as reducing electronic waste by maximizing the lifespan of physical devices through backwards compatibility.

The web was built on a "view source" principle, currently realized through robust developer tools built into many browsers. We will always make sure it is possible to determine how a web application was built and how the code works. Furthermore, we will always make sure it is possible to audit and inspect web applications and underlying software for security, privacy, or other considerations.

We will not create web technologies that encourage the creation of websites that work only in one browser, or only on particular hardware. We expect that content provided by accessing a URL should yield a thematically consistent experience when someone is accessing it from different devices. The existence of multiple interoperable implementations enables competition, and thus a variety of choices for web users.

People must be able to change web pages according to their needs. For example, people should be able to install style sheets, assistive browser extensions, and blockers of unwanted content or scripts. We will build features and write specifications that respect people's agency, and will create user agents to represent those preferences on the web user's behalf.

The TAG would like to thank the following people for their help, input, and feedback during the conceptualization and ongoing development of this document: Tantek Çelik (Mozilla), Oluwatomisin Niyi-Awosusi, Joanna J. Bryson (Professor of Ethics and Technology, Centre for Digital Governance, Hertie School), Wendy Seltzer.

[design-principles]
Web Platform Design Principles. Lea Verou. W3C. 18 July 2024. W3C Working Group Note. URL: https://www.w3.org/TR/design-principles/
[mobile-bp]
Mobile Web Best Practices 1.0. Jo Rabin; Charles McCathieNevile. W3C. 29 July 2008. W3C Recommendation. URL: https://www.w3.org/TR/mobile-bp/
[Privacy-Principles]
Privacy Principles. Robin Berjon; Jeffrey Yasskin. W3C. 20 November 2024. W3C Working Group Note. URL: https://www.w3.org/TR/privacy-principles/
[RFC7258]
Pervasive Monitoring Is an Attack. S. Farrell; H. Tschofenig. IETF. May 2014. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc7258
[security-privacy-questionnaire]
Self-Review Questionnaire: Security and Privacy. Theresa O'Connor; Peter Snyder. W3C. 16 December 2021. W3C Working Group Note. URL: https://www.w3.org/TR/security-privacy-questionnaire/
[UDHR]
Universal Declaration of Human Rights. United Nations. URL: https://www.un.org/en/universal-declaration-human-rights/