Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

User identity attribute #73

Open
rakiru opened this issue Jun 17, 2015 · 2 comments
Open

User identity attribute #73

rakiru opened this issue Jun 17, 2015 · 2 comments

Comments

@rakiru
Copy link
Member

rakiru commented Jun 17, 2015

A new base attribute for User objects to store the per-network identity (NickServ username, Mumble cert, Twitch username, etc.), to be used for storing user-specific information for users not authed with Ultros. Probably identity, but another name may be better.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22358092-user-identity-attribute?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github).
@rakiru
Copy link
Member Author

rakiru commented Sep 4, 2015

Mumble now has User.certificate_hash, which is how the friends system in the client is implemented. It also has User.user_id, which is an ID given to each registered user. You can't register without a cert though, and not using your cert means your user_id will change, so I see no advantage to using it over certificate_hash.

@gdude2002
Copy link
Member

I was thinking about this for Discord as well, I think a standard way of doing this would be great; then we can have the Auth system deal with it transparently.

By the by, auth currently works by setting attributes on User objects - should we change this to a method on the auth handler for the sake of extension and modularity?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants