Skip to content

Commit

Permalink
Merge pull request #285 from thegreatfatzby/patch-1
Browse files Browse the repository at this point in the history
Clarify: Current Rather than Future
  • Loading branch information
dvorak42 authored Jan 16, 2024
2 parents 35baf72 + c7d3ac2 commit cb60720
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Private State Token API Explainer

This document is an explainer for a potential future web platform API that allows propagating limited private signals across sites, using the [Privacy Pass](https://privacypass.github.io) protocol as an underlying primitive.
This document is an explainer for a Web Platform API that allows propagating limited private signals across sites, using the [Privacy Pass](https://privacypass.github.io) protocol as an underlying primitive.

The current version of the spec is available at [https://wicg.github.io/trust-token-api/](https://wicg.github.io/trust-token-api/).

Expand All @@ -12,7 +12,7 @@ This API was formerly called the Trust Token API and the repository and API surf

- [Motivation](#motivation)
- [Overview](#overview)
- [Potential API](#potential-api)
- [API](#api)
- [Private State Token Issuance](#private-state-token-issuance)
- [Private State Token Redemption](#private-state-token-redemption)
- [Forwarding Redemption Attestation](#forwarding-redemption-attestation)
Expand Down Expand Up @@ -53,7 +53,7 @@ This API proposes a new per-origin storage area for “Privacy Pass” style cry
When an origin is in a context where they trust the user, they can issue the browser a batch of tokens, which can be “spent” at a later time in a context where the user would otherwise be unknown or less trusted. Crucially, the tokens are indistinguishable from one another, preventing websites from tracking users through them.


## Potential API
## API


### Private State Token Issuance
Expand Down

0 comments on commit cb60720

Please sign in to comment.