A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Sharing

From WHATWG Wiki
Revision as of 12:10, 4 August 2014 by Annevk (talk | contribs) (Created page with "Figuring out sharing for the web. == Actors == * End user * Items that can be shared (share item) * Place that has items to share (share source) * Place items can be shared ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Figuring out sharing for the web.

Actors

  • End user
  • Items that can be shared (share item)
  • Place that has items to share (share source)
  • Place items can be shared with (share destination)

Use cases

Brief: E wants to share I (image, URL, ...) from S (The New Yorker, xkcd, ...) on D (Twitter, Facebook, Pocket ...)

Longer:

Note that The Boston Globe needs no knowledge about the share destinations. And Pocket does not need to be known by all share origins.

UI speculation

Share destination could be displayed on top of share source. In case of Twitter this might require almost the entire screen (on mobile). In case of Pocket this would not require much UI at all in the simple case.

Thus, an inline overlay of which the security properties are somehow still clear to the end user.

Requirements

As this is a new API, a secure origin (TLS) is required to be a share destination.

Requiring a secure origin for a share source seems like too much of a burden.

TODO

  • Analyze registerProtocolHandler()

Resources