residual/rechat
Watch
3
0
Fork
You've already forked rechat
 0
Code Issues 12 Pull requests Projects Releases Packages Wiki Activity Actions
res-chat: self-hosted IRC-based chat with voice and file transfers
19 commits 1 branch 0 tags 211 KiB
  • Go 100%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
merith-tk 9a7b1ba944 Docs: RECHAT-INFO in services.md
2026-10-17 20:26:05 +00:00
cmd Client: multi-server UI prototype (issue #13) 2026-10-17 20:25:50 +00:00
docs Docs: RECHAT-INFO in services.md 2026-10-17 20:26:05 +00:00
internal Client: multi-server UI prototype (issue #13) 2026-10-17 20:25:50 +00:00
.gitignore Initial structure: rechat-server and rechat binaries 2026-10-16 10:05:54 -07:00
go.mod Server: RECHAT-INFO metadata command (issue #11) 2026-10-17 20:20:34 +00:00
go.sum Server: RECHAT-INFO metadata command (issue #11) 2026-10-17 20:20:34 +00:00
README.md Initial structure: rechat-server and rechat binaries 2026-10-16 10:05:54 -07:00

README.md

rechat

Self-hosted chat: IRC server + official TUI client, with voice and file transfers.

Binaries

Binary Purpose
rechat-server Hand-rolled IRC server (SRV). Standard IRC clients can connect.
rechat Official Limoni TUI client.

Architecture

Three components sharing one account backend:

  • Chat: IRC over TCP/TLS (hand-rolled server). Text, presence, channels.
  • Files: HTTP. Upload/download, inline rendering. Torrent mode later.
  • Voice: WebRTC P2P (host-relayed). Design TBD.

Build stages

  1. SRV — IRC server. Messaging, auth, standard client compat.
  2. Client — Official rechat TUI client.
  3. Files — HTTP file sharing (flat downloads initially).
  4. Voice — P2P voice channels.

See issues for stage plans and design notes.