Project description
TranslatedWe have a working web application and now need to integrate full real-time messaging into it. We're talking about chat between our users, not a support widget popup or an AI bot: a user opens a conversation with another user and exchanges messages that arrive instantly without page reload. We need both one-to-one private dialogs and group chats where multiple participants see a common thread, room composition, and follow the conversation as it appears. This is a communication feature between our own platform accounts, so it must work as smoothly and reliably as familiar messaging apps.
Technically we expect WebSocket transport for live delivery with a reasonable fallback option and automatic reconnection on connection loss. Messages must be persisted in the database so chat history loads correctly when reopening a conversation, and delivery should be ordered and deduplicating even on unstable networks. We need a typing indicator, 'delivered' and 'read' statuses for each message, unread counters per chat, and presence (online, last seen). Attachments are important: users should be able to send images and documents with previews and safe size limits. When the recipient is offline or the tab is closed, a push notification alerts them to the new message. The backend should rely on our current user accounts and access permissions rather than introducing a separate auth system.
We consider security and abuse prevention part of the task: authenticated socket connections tied to active sessions, permission checks (a user reads only threads they participate in), input sanitization against XSS when displaying messages, and basic rate limiting against spam. We expect clean documented code in our current stack, brief integration instructions, and tests for main scenarios.
— Private and group chats with participant management
— WebSocket delivery with reconnection and offline fallback
— Typing indicator, delivery/read statuses, unread counters, presence
— Image and document attachments with previews and size limits
— Push notifications for offline recipients
— History, ordering, deduplication and message persistence
— Session-bound sockets, per-thread permission checks, XSS protection, rate limiting
Technically we expect WebSocket transport for live delivery with a reasonable fallback option and automatic reconnection on connection loss. Messages must be persisted in the database so chat history loads correctly when reopening a conversation, and delivery should be ordered and deduplicating even on unstable networks. We need a typing indicator, 'delivered' and 'read' statuses for each message, unread counters per chat, and presence (online, last seen). Attachments are important: users should be able to send images and documents with previews and safe size limits. When the recipient is offline or the tab is closed, a push notification alerts them to the new message. The backend should rely on our current user accounts and access permissions rather than introducing a separate auth system.
We consider security and abuse prevention part of the task: authenticated socket connections tied to active sessions, permission checks (a user reads only threads they participate in), input sanitization against XSS when displaying messages, and basic rate limiting against spam. We expect clean documented code in our current stack, brief integration instructions, and tests for main scenarios.
— Private and group chats with participant management
— WebSocket delivery with reconnection and offline fallback
— Typing indicator, delivery/read statuses, unread counters, presence
— Image and document attachments with previews and size limits
— Push notifications for offline recipients
— History, ordering, deduplication and message persistence
— Session-bound sockets, per-thread permission checks, XSS protection, rate limiting
Web programming Cash, Bank transfer
