User Verification

[EranSch]

In order to branch the Visitor model discussed in #8 to our Frontend user, a user verification process could be implemented. Essentially...

1. User creates account on frontend
2. Plug.dj username is required during signup
3. Similar to an email verification process, the user is given a verification code.
4. User must enter plug.dj room and announce code with some sort of command like .verifyme <VerificationCodeHere>
5. System may now associate a Plug.dj user ID with a MEAN user.

Using this approach, the system can keep up to date stats on the user making personalized details of room activity more accessible and relevant. Further, Frontend permissions could be derived from the user's role/permission level in the room.

[hect1c]

This is a great idea. We should still be able to provide basic functionality for none registered users and be able to maintain their data as I'm sure not every user would want to have to sign up?

[EranSch]

I think every new user that enters the room should be logged in the Visitors collection. This would contain all the Plug.dj meta data as well as maybe a seen array field that keeps a record of every time the user enters the room.

If it's the first time the user's been in the room then a new record is created. If they're returning then a new date entry is added to the seen array.

Upon signing up on the front end and proceeding through the verification process, a flag would be set on the User record and a reference to the ID of the user's associated entry in the Visitor collection established.

[hect1c]

Good logic. I approve, good job on normalization of the db.