What is only-talk-rs?

OnlyTalk RS is a backend server for an instant messaging application, written in Rust. It is not a finished chat app with a user interface, it is the server component that a client app would connect to. The project is intended for developers who want to run their own messaging infrastructure. The server handles two kinds of traffic at once. A standard HTTPS API handles account registration, login, friend management, group management, file uploads, and message history queries. A separate QUIC connection handles real-time message delivery. QUIC is a newer network protocol that reduces the delay between sending and receiving a message compared to older approaches. The server runs both services in a single process by default, though they can be split into separate processes for larger deployments. For direct device-to-device connections, the server supports a technique called P2P hole punching, which allows two clients to establish a direct link even when both are behind home routers or firewalls. If that direct connection cannot be established, the server automatically falls back to relaying messages through itself. File sharing supports local storage or any S3-compatible object store such as MinIO, Amazon S3, or Aliyun OSS. Images are automatically converted to WebP format on upload. Large files can be sent in chunks. Files are accessed through pre-signed URLs rather than public links. User passwords are hashed with Argon2. API traffic uses TLS 1.3. Sensitive data in transit is encrypted with RSA public keys. User sessions are managed with JWT tokens stored in Redis. Setup requires Rust, PostgreSQL, Redis, and TLS certificates. Configuration is split between a TOML file for server settings and an environment file for database and storage credentials. The README includes steps for database initialization, certificate placement, and running in development or release mode.