Open rakiru opened 9 years ago
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
.
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?
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.