<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 25/11/14 11:13, Shane Tomlinson a
écrit :<br>
</div>
<blockquote cite="mid:5474564B.2070509@mozilla.com" type="cite">
<pre wrap="">On 24/11/2014 19:43, Tarek Ziadé wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Moving folks in cc to Bcc and keeping the ML
Le 24/11/14 20:26, Chris Karlof a écrit :
[..]
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">2- will fxa-profile be Mozillian's backend for profile data ?
</pre>
</blockquote>
<pre wrap="">I’m not sure, but migrating Mozillans.org data to FxA would be a serious effort, so we should understand the value prop there.
</pre>
</blockquote>
<pre wrap="">
I am not fully understanding the scope of fxa-profile - according to
<a class="moz-txt-link-freetext" href="https://developer.mozilla.org/en-US/Firefox_Accounts#Firefox_Accounts_user_data">https://developer.mozilla.org/en-US/Firefox_Accounts#Firefox_Accounts_user_data</a>
it might even store phone numbers.
So it sounded like a phonebook/directory of users to me. Which is
exactly what Mozillians.org is (a subset of a wider users directory +
some social feats)
</pre>
</blockquote>
<pre wrap="">
At the moment profile information is private by default and only
provided to an RP after the OAuth dance. That said, public/searchable
profiles are useful. I think your idea and the current private by
default can co-exist.
Users should be able to opt-in to making a portion of their profile
public. We would then provide a search mechanism that returns the public
profile information for a user. </pre>
</blockquote>
Yes, this is what Mozillians.org provides. If you log in your
account there, you have 3 levels of visibility for each info in your
profile:<br>
<br>
- private: only you can see it<br>
- mozillians: only people connected can see it<br>
- public: everyone can see it<br>
<br>
They also have APIs to search by username or email
<a class="moz-txt-link-freetext" href="http://mozillians.readthedocs.org/en/latest/api/api-users.html">http://mozillians.readthedocs.org/en/latest/api/api-users.html</a><br>
They have api keys to deal with *per app* authorization.<br>
<br>
<br>
<blockquote cite="mid:5474564B.2070509@mozilla.com" type="cite">
<pre wrap="">If an RP wishes for additional user
information, they have to go through the OAuth dance and for ask the
user's permission. This would allow a user to make their email address &
public key public, but nothing more.</pre>
</blockquote>
That'd be exactly what I'd want. We'd probably need to have a list
of keys per users rather than a single key - and a way to revoke
some.<br>
<br>
I am not clear yet about the notion of "application" in fxa context
though. <br>
<br>
<blockquote cite="mid:5474564B.2070509@mozilla.com" type="cite">
<pre wrap="">
Shane
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dev-fxacct mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/dev-fxacct">https://mail.mozilla.org/listinfo/dev-fxacct</a>
</pre>
</blockquote>
<br>
</body>
</html>