Shane Kilkelly 6765d03339 Track the isRestrictedUser flag on clients ... Then, don't send new chat messages and new comments to those restricted clients. We do this because we don't want to leak private information (email addresses and names) to "restricted" users, those who have read-only access via a shared token.		2019-10-04 10:30:24 +01:00
..
.github
app/coffee	Track the isRestrictedUser flag on clients	2019-10-04 10:30:24 +01:00
config	remove forceDrainMsDelay	2019-08-14 11:51:25 +01:00
test	Track the isRestrictedUser flag on clients	2019-10-04 10:30:24 +01:00
.dockerignore
.gitignore
.nvmrc	Revert "Csh issue 1118 node 10.15.3"	2019-05-24 15:21:48 +01:00
.travis.yml
app.coffee	add log line to draining	2019-08-15 14:41:22 +01:00
buildscript.txt	update logger and metrics	2019-06-21 11:26:28 +01:00
docker-compose.ci.yml	update logger and metrics	2019-06-21 11:26:28 +01:00
docker-compose.yml	update logger and metrics	2019-06-21 11:26:28 +01:00
Dockerfile	Revert "Csh issue 1118 node 10.15.3"	2019-05-24 15:21:48 +01:00
Jenkinsfile
Makefile	update logger and metrics	2019-06-21 11:26:28 +01:00
nodemon.json
npm-shrinkwrap.json	upgrade sinon to 1.17.7 for onCall support	2019-07-22 11:23:02 +01:00
package.json	upgrade sinon to 1.17.7 for onCall support	2019-07-22 11:23:02 +01:00
socket.io.patch.js	Patched EventEmitter for socket.io compatibility with Node >= 7	2019-07-25 09:22:24 +00:00