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,

When an agent mute/unmute the converstion, add an activity message "#{agent_name} has muted the conversation"

Is your feature request related to a problem?

Our user needed to roll his own solution for refreshing feature flags: PostHog/posthog-js#100

We can provide tools to help them.

Describe the solution you'd like

Provide a hook, component or some other standardized way to use feature flags in react code which reacts (hah) to feature flags changing.

Stretch

Problem
We should be able to archive (soft delete) conversations if they've been closed for a certain period of time. This will speed up our queries and remove unnecessary data from the UI. Also, since it's a soft-delete, we'll be able to retrieve the data if the user decides they want it back.

Solution
Let's add an archived_at field to the conversations table and use the presence

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