CLUSTER RELAY-CHAT-CONNECTS · 4 ENTRIES · EARLIEST ENTRY 2013-03-05
WeeChat relay IRC clients
This cluster consists of remote clients that connect to a WeeChat relay to read and send IRC messages across devices, including web, Android, and desktop implementations. The dated history is too thin to read a shape from, with only four dated entries before the index start; it likely predates the index or members are undated. Traction leaders, based on activity signals, are Lith, Weechat-Android, and glowing-bear-web, though all have zero stars.
Entry timeline
ENTRY TIMELINE
Each bar is the month a member carries, which is a creation date where the source published one and a crawl date otherwise. Nothing in the index was found before 11 August 2026, and coverage broadened sharply on 14–15 August, so a bar from then on reports how much we found that month, not how much was built; an earlier bar reports how far back a member's own source dated it — not how long we have been watching.
Members by activity
Activity signals, not revenue.
Build origin · 2 hand-coded · 2 unlabelled
Operator · 4 open source
Two labels per entry, never collapsed into one: how it was built, and who stands behind it. Counted over the 4 listed below. Unlabelled means nothing has decided yet — not that the answer is small.
- 01Weechat-Android0★7 mostaleliveopen sourceAndroid app that connects to a WeeChat relay server to browse channels and chat on IRC from a mobile device.
- 02Lith0★7 mostaleliveopen sourceA relay client that connects to a remote chat server instance, letting users read and send messages remotely from any device.
- 03glowing-bear-web0★6 yrabandonedlivehand-codedopen sourceWeb-based client that connects to a WeeChat relay to read and send messages across internet relay chat networks.
- 04glowing-bear-electron0★5 yrabandonedlivehand-codedopen sourceDesktop client that connects to a WeeChat relay to read and send messages across internet relay chat networks.
Ranked by traction, highest first, and paged 20 at a time — this is a window on the cluster, never the whole of it. Ties are broken by a stable id so a product cannot appear on two pages or fall between them. Browse every cluster.