Skip to content

docs: add 'Why SemaBuzz?' origin story section #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skynrlabs merged 1 commit into from
May 15, 2026
+12 −0
Merged

docs: add 'Why SemaBuzz?' origin story section #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,18 @@ Every session generates fresh encryption keys on both devices using **ECDH P-256

---

## 💬 Why SemaBuzz?

I grew up on PowWow, ICQ, and MSN Messenger — there was something magical about that era of direct, personal chat that modern apps have completely lost. I built SemaBuzz to bring that feeling back.

You'll find a lot of the classics: URL Walk, a shared whiteboard, file transfer, and rich status changes with custom status messages — things PowWow and ICQ fans will recognize instantly.

Then we added our own spin: every session generates fresh encryption keys via token-based E2E chat, with a private relay that literally cannot read your messages. And the live-typing preview — that flowing filament line showing characters as they're typed — is our love letter to what made those old programs feel so alive.

Fully open-source (AGPL-3.0). Would love to hear from anyone else who misses that era. 👾

---

## ✨ Features

- ⌨️ **Live-wire typing** — keystrokes stream in real time; watch the other person compose character by character
Expand Down
Loading