Moved the definition of updateTimestamps from Chat into the library base
App along with the call to update on-page timestamps during the creation
of the App as a convenience.
Any element following the `data-dtp-timestamp` and
`data-dtp-timestamp-format` conventions will have its `textContent` set
to a client-local representation of that date/time.
UserService.create was adapted a while back to accomodate imports, and
was honoring a field named `isAdmin` and/or `isModerator` during create
to set the value of `flags.isAdmin` and `flags.isModerator`.
This change breaks that importer but stops people from being able to
"sign up" with Admin privileges.
Allow the specification of the KaleidoscopeEvent creation date/time.
This allows Sites and Venue to emit their recent history to a Core when
connecting to populate the Core with their content upon arrival.
- Integrated EventEmitter2 for async event processing
- Changed jshint reporter module URL to avoid use of SSH
- Core can disconnect a service node, generates many events
- Service Node can disconnect a Core, generates many events
Nothing yet processes those events. Many things need to be cleaned up
and removed based on a Core Node disconnection. The Core itself needs to
remove all Kaleidoscope events and other data received from the Service
Node, and the Service Node needs to remove all CoreUser records (and
everything they did while there).
That's going to take a minute to implement throughout all the systems.
CyberShell