545563e776
- Complete NestJS TypeScript implementation with WebSocket support - Direct messaging (DM) and group chat functionality - End-to-end encryption with AES encryption and key pairs - Media file support (images, videos, audio, documents) up to 100MB - Push notifications with Firebase Cloud Messaging integration - Mention alerts and real-time typing indicators - User authentication with JWT and Passport - SQLite database with TypeORM entities and relationships - Comprehensive API documentation with Swagger/OpenAPI - File upload handling with secure access control - Online/offline status tracking and presence management - Message editing, deletion, and reply functionality - Notification management with automatic cleanup - Health check endpoint for monitoring - CORS configuration for cross-origin requests - Environment-based configuration management - Structured for Flutter SDK integration Features implemented: ✅ Real-time messaging with Socket.IO ✅ User registration and authentication ✅ Direct messages and group chats ✅ Media file uploads and management ✅ End-to-end encryption ✅ Push notifications ✅ Mention alerts ✅ Typing indicators ✅ Message read receipts ✅ Online status tracking ✅ File access control ✅ Comprehensive API documentation Ready for Flutter SDK development and production deployment.
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# Change Log
|
|
All notable changes to this project will be documented in this file.
|
|
|
|
## [3.0.0]
|
|
### Changed
|
|
- **BREAKING**: `jwt.verify` now requires an `algorithm` parameter, and
|
|
`jws.createVerify` requires an `algorithm` option. The `"alg"` field
|
|
signature headers is ignored. This mitigates a critical security flaw
|
|
in the library which would allow an attacker to generate signatures with
|
|
arbitrary contents that would be accepted by `jwt.verify`. See
|
|
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
|
|
for details.
|
|
|
|
## [2.0.0] - 2015-01-30
|
|
### Changed
|
|
- **BREAKING**: Default payload encoding changed from `binary` to
|
|
`utf8`. `utf8` is a is a more sensible default than `binary` because
|
|
many payloads, as far as I can tell, will contain user-facing
|
|
strings that could be in any language. (<code>[6b6de48]</code>)
|
|
|
|
- Code reorganization, thanks [@fearphage]! (<code>[7880050]</code>)
|
|
|
|
### Added
|
|
- Option in all relevant methods for `encoding`. For those few users
|
|
that might be depending on a `binary` encoding of the messages, this
|
|
is for them. (<code>[6b6de48]</code>)
|
|
|
|
[unreleased]: https://github.com/brianloveswords/node-jws/compare/v2.0.0...HEAD
|
|
[2.0.0]: https://github.com/brianloveswords/node-jws/compare/v1.0.1...v2.0.0
|
|
|
|
[7880050]: https://github.com/brianloveswords/node-jws/commit/7880050
|
|
[6b6de48]: https://github.com/brianloveswords/node-jws/commit/6b6de48
|
|
|
|
[@fearphage]: https://github.com/fearphage
|