Derived User Identity

Some of the features (such as list merging) could be made easier if our user base logged into the system, which is something we've been trying to avoid in the spirit of providing an open, collaborative user experience. I would like to discuss some alternatives we could apply that would allow us to derive some semblance of the user identities that are collaborating on a list and then further discuss how this information might be used to ease the implementation of those features that are more geared towards a logged in user experience. Some examples might include: listing those lists that a user is collaborating on, list merging, etc.

Some of the derived user identity information we currently have available:

• Amazon Unique ID (Alexa)
• Cellphone Number (Twilio)
• IP Address
• Can we obtain anything else if we are running on a phone? How about if they install our application on their desktop with the new Chrome capabilities (i.e. access to Android Intents).