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.
891 B
891 B
0.1.4 / 2020-06-02
- Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)
- Change license from MIT to Apache 2.0
0.1.3 / 2017-11-11
- Accept extension names and parameters including uppercase letters
- Handle extension names that clash with
Object.prototypeproperties
0.1.2 / 2017-09-10
- Catch synchronous exceptions thrown when calling an extension
- Fix race condition caused when a message is pushed after a cell has stopped due to an error
- Fix failure of
close()to return if a message that's queued after one that produces an error never finishes being processed
0.1.1 / 2015-02-19
- Prevent sessions being closed before they have finished processing messages
- Add a callback to
Extensions.close()so the caller can tell when it's safe to close the socket
0.1.0 / 2014-12-12
- Initial release