The better approach in ExpressJS is to author up a quick middleware you
can toss onto any route to short-circuit the rest fo the route with the
redirect.
The implementation submitted was actually running double output. The
"checkForUser" method would call `res.redirect`, return, and then the
method would continue and produce additional output.
Explicit middleware helps prevent those kinds of errors :)
- Integrated all chat updates from Soapbox/Shing with heavy mods to
lib/site-ioserver.js and the creation of the chat service, worker, and
jobs
- Added ability to create ChatRoom instances, invite people to them,
join them and delete them
- Refactored the shit out of SiteWorker
- Created SiteWorkerProcess
- Created the chat worker and the chat-room-clear and chat-room-delete
job processors
- Created the media worker
- Refactored Stickers from Soapbox/Shing into the media system
- Created the Attachment model, service, and media worker jobs
- Upgraded the emoji picker from emoji-button to picmo because the
author depreacted emoji-button and released picmo.
- Made a custom presentation for the emoji picker
- Created the SiteChat client-side object for managing Core Chat within
the browser
- Brought the Kaleidoscope Event UI down from DTP Social so anything can
render a timeline of them
- Added configurations for the media and reeeper job queues
- Added the basics of a Notifications view
- Added the concept of Forms
- upgraded ioredis to 5.2.2