Send text and files directly between two paired devices.
Translation pending
SocialTypeScript · CSSGitHub @bos-codeOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A lightweight real-time text bridge between two paired devices. No account and no database.
client/ is a Next.js + TypeScript frontend. server/ is a small Node.js + ws relay. Rooms and their latest text live only in server memory and disappear after the room expires or the server restarts.
Requires Node.js 20+.
npm run install:all
npm run dev
Open http://localhost:3000. The WebSocket server runs on port 8080.
These run in CI (.github/workflows/ci.yml) on every push to main and every pull request:
npm run format:check # Prettier, whole repo (npm run format to fix)
npm --prefix server run typecheck # server source and tests
npm --prefix server test # server integration tests
npm --prefix client run lint # ESLint (Next.js rules)
npm --prefix client run typecheck
npm run build
server/src/realtime.ts: room, relay, rate-limit and heartbeat logic (createRealtimeServer)server/src/index.ts: reads environment variables and starts the serverclient/hooks/useRoomSocket.ts: WebSocket connection, reconnects and room stateclient/hooks/usePeerTransfer.ts: WebRTC negotiation and file transferclient/components/: UI pieces composed by client/app/page.tsxclient/lib/: message types and file helpersCopy .env.example to client/.env.local:
NEXT_PUBLIC_WS_URL=ws://localhost:8080
Production must use a secure wss:// endpoint.
Server environment variables (all optional):
| Variable | Purpose |
|---|---|
ALLOWED_ORIGINS | Comma-separated frontend origins allowed to connect, e.g. https://derashare.vercel.app. Unset allows any origin, which is only appropriate for local development. |
TRUST_PROXY | Set to 1 behind a reverse proxy (Render, Railway) so rate limits use the client IP from x-forwarded-for. |
MAX_ROOMS | Maximum concurrent rooms. Defaults to 10000. |
TURN_URLS | Comma-separated TURN URLs, e.g. turn:turn.example.com:3478,turns:turn.example.com:5349. |
TURN_SECRET | Shared secret for coturn's use-auth-secret mode. Each device gets credentials that expire after 12 hours. |
TURN_USERNAME / TURN_CREDENTIAL | Fixed credentials instead of TURN_SECRET, e.g. from a hosted TURN provider. |
Without TURN, files only transfer when the two devices can reach each other directly. That usually works on the same Wi-Fi and often fails between mobile networks. After 20 seconds without a connection the app says file sharing is unavailable; text keeps working through the server either way.
Deploy client/ to Vercel. Deploy server/ to a persistent Node.js host that supports WebSockets, such as Render or Railway. Set NEXT_PUBLIC_WS_URL on the frontend to the public WebSocket server URL, and set ALLOWED_ORIGINS on the server to the frontend URL.
The server exposes GET /health for host health checks.