Mozilla provide the service
Originally Posted by Old Pedant
Okay...I'm with you.
Now why does it need to be taken beyond what Mozilla offers?
Ahhh...you want to keep track to be sure an email address isn't reused.
But that is an ENORMOUS CONFLICT with this statement in your second post:
How does that work, if an email address can't be used more than once? How many users keep around as many email addresses as computers where they might login?
I know that I login to CodingForums.com from several different computers during the course of a month. So I would need a different email address for each computer??? I happen to have the capability to do that, but I would sure hate it!
I'm trying hard to see the advantages of this system, but I'm not there yet.
... it is the community that must produce the solutions.
If you have visited the site mentioned in the previous post, and tried it, you'll see that its output is an email variable, which is fine.
The signin button changes to your email address (after signing in)
If you click thru to main menu, and then return to 'Quick Intro & Signin', the signin button is back.
Not the end of the world - even on the Bing webtools site, after signing in, you are still asked to sign in...... it's just a bit slack.
However, with a developed solution, the signin button would disappear until you choose to log out.
Current Storage of the email/userID
I've just used local storage.
Any page then displaying ones userID simply pulls it out of storage.
On a subsequent visit, even if you don't sign in, your userID will display.
It's fine for starters, but the next step ought be to establish a website account specification, and then develop the scripts to achieve it.
Each browser on each PC that is being used, will need to be registered once.
For simplicity, one would use the same password, and same email address for all browsers.
Once the Browsers are registered (using the std email system), then it becomes very easy for the user.
If your PC's are secure, you can choose to store the password for 3 months, in which case you will not have to enter a password again when logging in to a Persona enabled site (for 3 months).
Clearly the initial setup is a bit of a pain when you're using lots of browsers, but most web users will probably use a couple on the PC, and probably just one or two on their mobile platforms.
Either way, account registration is the price paid for password security.
The single User Session Concept
Would be a useful enable/disable feature for site developers.
For some sites you just wouldn't dream of enabling it, whereas for other sites, it would perfect.
For example: A site providing a paid for service, per member.
Say $10 per member per year.
A business buys membership and hands the password around to 20 staff, who would be getting the service for 50 cents.
A single user session would solve that problem.