946
edits
Firefox/Projects/AccountManager/Meetup/Analysis: Difference between revisions
Jump to navigation
Jump to search
Firefox/Projects/AccountManager/Meetup/Analysis (view source)
Revision as of 02:02, 5 June 2010
, 5 June 2010no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
One slight quirk is that the browser should probably ignore the caching hints when the cookie changes. | One slight quirk is that the browser should probably ignore the caching hints when the cookie changes. | ||
;Flood-attack prevention | ;Flood-attack prevention | ||
| Line 70: | Line 66: | ||
A variant of the above could be to allow the password to be changed during the registration flow, but that would require the final confirmation step to return the credentials (username and password both), which sites might not want to do (?). The confirm-registration step need only work once, however, the <token> in the cookie could expire after first use, or have a very short life. | A variant of the above could be to allow the password to be changed during the registration flow, but that would require the final confirmation step to return the credentials (username and password both), which sites might not want to do (?). The confirm-registration step need only work once, however, the <token> in the cookie could expire after first use, or have a very short life. | ||
= Rejected Ideas = | ;Splitting authentication profiles from other profiles | ||
We have some thoughts around it, but it's not clear yet. More work to do here. | |||
;Federation | |||
Still distilling proposals here, stay tuned. | |||
= Rejected/Other Ideas = | |||
;JS API for setting status | ;JS API for setting status | ||