Wondering whether a 1-pager would be useful.

[ianbjacobs]

No description provided.

[jyasskin]

A summary of the discussion today:

• I had summarized the principles for my TPAC presentation last year, at

  privacy-principles/meetings/2023-09-tpac/tuesday-ac-meeting/slides.html

  Lines 133 to 192 in 011b137

  	<section class="slide">
  	<h2 title="These are not direct quotes of the principles from the document.">Principles *</h2>
  	<div class="columns">
  	<ul>
  	<li title="A user agent should help its user pick an identity to present to each site they visit.">
  	Help users pick their identities.
  	</li>
  	<li title="We should all send the minimal amount of data to achieve our users' goals.">
  	Minimize data for user goals.
  	</li>
  	<li
  	title="When we add a new API to the web, it needs to protect the data it exposes at least as well as existing APIs and not make bad uses easier.">
  	New APIs can expose some data.
  	</li>
  	<li
  	title="Some classes of information are sensitive, but it's dangerous to assume that people won't find other information sensitive too.">
  	Information can be sensitive.
  	</li>
  	<li title="People have some rights to control their data.">
  	People have data rights.
  	</li>
  	<li title="De-identifying data is both good and difficult, and we talk about some aspects of doing it well.">
  	Try to de-identify data.
  	</li>
  	<li
  	title="Relying too much on individual choices about privacy can sacrifice the interests of other people based on their membership in groups.">
  	Groups have privacy interests.
  	</li>
  	</ul>
  	<ul>
  	<li
  	title="Even though browsers are chosen by a device's owner or administrator; browsers also have to protect their end-users against surveillance by those owners. Children are an especially complex case here.">
  	Balance device owners & users.
  	</li>
  	<li title="We need to design ways to prevent abuse into both websites and web APIs.">
  	Protect users from abuse.
  	</li>
  	<li
  	title="We need to support vulnerable people, including by making sure everything degrades gracefully if people opt for stronger privacy protections.">
  	Support vulnerable people.
  	</li>
  	<li
  	title="And in general, when people opt for more privacy, sites shouldn't retaliate by removing unrelated features.">
  	Don't retaliate.
  	</li>
  	<li
  	title="We need to ask for consent respectfully by avoiding interruptions, making sure that we learn people's actual intentions, and letting people change their minds.">
  	Request consent respectfully.
  	</li>
  	<li title="Notifications shouldn't interrupt people.">
  	Avoid unwanted interruptions.
  	</li>
  	<li
  	title="And when an API exposes information about a person, we should let that person choose what information is sent, and not just whether information is sent.">
  	Let users choose their data.
  	</li>
  	</ul>
  	</div>
  	<p class="note" style="text-align: right">* These highly compressed principles omit a lot of the document's nuance.</p>
  	</section>

  . Those summaries might be the right thing to put in a 1-pager, with links back to the main document.
• We have 3 audiences for the principles. Maybe that implies we should have a separate 1-pager for each audience. We can auto-subset the summaries.
• The 1-pager(s) might actually not be in scope for this task force. MDN folks do summaries of specs for other audiences, and they might be the right people to summarize this document too.
• Despite that, I was volunteered to draft per-audience 1-pagers, incorporating some of the text from this PR.

[ianbjacobs]

@jyasskin, thank you for the summary. I'm happy to review 1-pagers.