You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of passing the user's ID directly as the parameter userID in join API calls (see this), the gem could hash this ID with something like sha1 to make sure the actual ID that comes from the database is not leaked while still make sure it's unique and always the same for users that have the same ID.
The text was updated successfully, but these errors were encountered:
Instead of passing the user's ID directly as the parameter
userID
injoin
API calls (see this), the gem could hash this ID with something likesha1
to make sure the actual ID that comes from the database is not leaked while still make sure it's unique and always the same for users that have the same ID.The text was updated successfully, but these errors were encountered: