HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
diorwave
cmd-chat
Python2026–2026
diorwave / cmd-chat

cmd-chat

My ISP tried to block this repo. 🤐 A truly peer-to-peer, end-to-end encrypted CLI chat that leaves NO logs. Perfect for... sensitive discussions. 🔥 Get it before it gets taken down

Command LineSecurity & PrivacyNetworkingCommunication & Social
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
340GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

My ISP tried to block this repo. 🤐 A truly peer-to-peer, end-to-end encrypted CLI chat that leaves NO logs. Perfect for... sensitive discussions. 🔥 Get it before it gets taken down

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:02:26 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-01-06 14:02:23 UTC to 2026-01-07 09:16:07 UTC.

012026-01-06 14:00:00 UTC to 2026-01-06 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 6, 14:002026-01-06 15:00:00 UTC to 2026-01-06 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 16:00:00 UTC to 2026-01-06 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 17:00:00 UTC to 2026-01-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 18:00:00 UTC to 2026-01-06 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 19:00:00 UTC to 2026-01-06 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 20:00:00 UTC to 2026-01-06 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 21:00:00 UTC to 2026-01-06 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 22:00:00 UTC to 2026-01-06 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 23:00:00 UTC to 2026-01-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 6, 23:002026-01-07 00:00:00 UTC to 2026-01-07 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 01:00:00 UTC to 2026-01-07 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 02:00:00 UTC to 2026-01-07 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 03:00:00 UTC to 2026-01-07 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 04:00:00 UTC to 2026-01-07 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 05:00:00 UTC to 2026-01-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 06:00:00 UTC to 2026-01-07 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 07:00:00 UTC to 2026-01-07 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 08:00:00 UTC to 2026-01-07 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 09:00:00 UTC to 2026-01-07 10:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 7, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 6, 14:002026-01-06 14:00:00 UTC2026-01-06 15:00:00 UTC110
Jan 6, 15:002026-01-06 15:00:00 UTC2026-01-06 16:00:00 UTC000
Jan 6, 16:002026-01-06 16:00:00 UTC2026-01-06 17:00:00 UTC000
Jan 6, 17:002026-01-06 17:00:00 UTC2026-01-06 18:00:00 UTC000
Jan 6, 18:002026-01-06 18:00:00 UTC2026-01-06 19:00:00 UTC000
Jan 6, 19:002026-01-06 19:00:00 UTC2026-01-06 20:00:00 UTC000
Jan 6, 20:002026-01-06 20:00:00 UTC2026-01-06 21:00:00 UTC000
Jan 6, 21:002026-01-06 21:00:00 UTC2026-01-06 22:00:00 UTC000
Jan 6, 22:002026-01-06 22:00:00 UTC2026-01-06 23:00:00 UTC000
Jan 6, 23:002026-01-06 23:00:00 UTC2026-01-07 00:00:00 UTC000
Jan 7, 00:002026-01-07 00:00:00 UTC2026-01-07 01:00:00 UTC000
Jan 7, 01:002026-01-07 01:00:00 UTC2026-01-07 02:00:00 UTC000
Jan 7, 02:002026-01-07 02:00:00 UTC2026-01-07 03:00:00 UTC000
Jan 7, 03:002026-01-07 03:00:00 UTC2026-01-07 04:00:00 UTC000
Jan 7, 04:002026-01-07 04:00:00 UTC2026-01-07 05:00:00 UTC000
Jan 7, 05:002026-01-07 05:00:00 UTC2026-01-07 06:00:00 UTC000
Jan 7, 06:002026-01-07 06:00:00 UTC2026-01-07 07:00:00 UTC000
Jan 7, 07:002026-01-07 07:00:00 UTC2026-01-07 08:00:00 UTC000
Jan 7, 08:002026-01-07 08:00:00 UTC2026-01-07 09:00:00 UTC000
Jan 7, 09:002026-01-07 09:00:00 UTC2026-01-07 10:00:00 UTC110

What Hacker News says

1 sources
isanoguchi·Jan 7, 2026Submission

Show HN: A RAM-only, end-to-end encrypted P2P terminal chat in Python

Hi HN, This is cmd-chat, a Python terminal chat app designed around a few constraints: - No central servers - No message or key persistence - No plaintext credentials ever sent over the network Authentication uses *SRP*, and messages are encrypted after key exchange. All data lives in memory only and disappears when the process exits. This was partly a learning project and partly an experiment in building a “minimum-trust” chat system using standard cryptographic primitives. Curious to hear thoughts on the threat model, crypto choices, and overall design.
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.