Confirmed users, Bureaucrats and Sysops emeriti
525
edits
Labs/Cherrypicker: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=Cherrypicker | |||
|Feature stage=Draft | |||
|Feature health=At risk | |||
|Feature status note=Need to do design validation before we invest too much time. | |||
}} | |||
{{FeatureTeam | |||
|Feature product manager=Bryan Clark | |||
|Feature lead engineer=Simon Wex | |||
|Feature additional members=Andy Chung, David Ascher | |||
}} | |||
{{FeaturePageBody | |||
|Feature open issues and risks=* Design Validation: does the idea have legs? | |||
* Delivery: is this something we'd want to offer at scale? | |||
* Security | |||
* Compliance | |||
* Long-term commitment | |||
|Feature overview=Cherrypicker is a codename for a service which we're exploring. This service is an email service which users would use to sign up for webapps, especially those they don't trust yet. Using a cherrypicker email account has the following values for users: | |||
* I don't need to share my (valuable) primary email address with a web app until I trust it | |||
* Web apps tend to send me bacn (machine-generated mail) which clutters my inbox, but is hard to find when I need it. Cherrypicker manages those messages intelligently, so that they're available when I want them, but out of my way most of the time. Examples include: | |||
** friend requests | |||
** shipment notifications | |||
** periodic announcements | |||
* If a webapp turns out to be spammy, I can delete it from cherrypicker, and the service unsubscribe me from the app, and hide those messages from me whether the app honors the unsubscription request or not. | |||
For webapps, cherrypicker can be an on-ramp to a higher-fidelity notification system with users: cherrypicker can both advertise and support direct messaging to the user through a (not-yet-designed) notification protocol, so that as an app developer, I can reach my users without having to fight spam detection, write lowest-common denominator email HTML, and unpredictable delivery delays. | |||
|Feature users and use cases=Someone who wants to try a webapp but is uncomfortable sharing their primary email address, or for whom the expected impact of possibly getting junk/spam/bacn is a deterrent to exploring the web. | |||
Someone who is an eager user of webapps, but who'se drowning in an overflowing inbox and wants help sorting the wheat from the chaff. | |||
|Feature dependencies=* Likely we'll use the verified email protocol to make signup easy. | |||
* Downstream, there are possible Firefox integration scenarios where Firefox, if it were to detect signups to a webapp, could offer the cherrypicker account, or even generate pseudonymous (per-site) accounts. | |||
|Feature non-goals=This is not about making a generic webmail. The set of messages we'd want to capture are explicitly computer-generated notices. | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=Unprioritized | |||
}} | |||
{{FeatureTeamStatus}} | |||
Cherrypicker is an exploration by Mozilla Labs of a possible service to provide better communications between webapps and people. | Cherrypicker is an exploration by Mozilla Labs of a possible service to provide better communications between webapps and people. | ||