It would be better to use bcrypt, beause its more secure as it's slower (uses more computing cycles).
Your code could also be better:

You wouldn't need salt field in User model, because it's saved into the same field as password does.

For authentication, something like:

var mongoose = require('mongoose'),
  bcrypt = require('bcryptjs');

var userSchema = mongoose.Schema({
  email: String,

Problem

Right now, the option to change availability status is hidden in profile settings. People might not realize that they have an option offline. To improve this UX, provide a setting right on the sidebar to change the status

Design

<img width="391" alt="Screenshot 2020-09-14 at 5 24 24 PM" src="https://user-images.githubusercontent.com/2246121/93082974-73c19e80-f6af-11ea-90da

Is your feature request related to a problem?

Please describe.

Feature flags currently can only be toggled on and off, but not deleted.

Describe the solution you'd like

A delete button.

Describe alternatives you've considered

Repurposing old feature flags for new ones.

Additional context

Thank you for your feature request – we love each and every on

Right now we only set the ip and last_seen_at fields when a customer record is created. Let's update the customer update_metadata endpoint (https://github.com/papercups-io/papercups/blob/master/lib/chat_api_web/controllers/customer_controller.ex#L58) so that it also handles this.

(I think we can just default the last_seen_at field to the current timestamp for now.)

Context

• This is part of release-1.5 #148
• MEDIUM priority task

Tasks

• Remove dependency bcrypt-nodejs in package.json
• Add dependency bcrypt in package.json
• Migrate file app/data/user-dao.js to bcrypt
• Validate the instalation with the local test
• Add and submit the chang