Figuring out sharing for the web.
- End user
- User agent
- Items that can be shared (share item)
- Place that has items to share (share source)
- Place items can be shared with (share destination)
(Could potentially merge share source and share item.)
Brief: E wants to share I (image, URL, ...) from S (The New Yorker, xkcd, ...) on D (Twitter, Facebook, Pocket ...)
- The Boston Globe wants to allow users to share http://www.boston.com/bigpicture/2014/07/conflict_continues_in_gaza.html with their preferred social network or private database.
- And the converse: Pocket would like to allow end users to share items around the web with it.
Note that The Boston Globe needs no knowledge about the share destinations. And Pocket does not need to be known by all share origins.
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 overlay browsing context of which the security properties are somehow still clear to the end user.
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.
- Open-ended scheme names does not work when UI requires knowledge about its scheme name. ("Can Gmail handle 'mailto'?" vs "Can Gmail handle email links?")
- Replaces the current browsing contexts or spawns a new one. No overlay
- Limited to sharing things that can be expressed through a URL
- Paul Kinlan on Web Intents: http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0023.html
- Jonas Sicking on Web Activities: https://wiki.mozilla.org/WebAPI/WebActivities/LessonsLearned