Slack
Quick questions, show and tell, and a place to find people working on the same thing. Invite link coming.
Community
Come build it with us.
It is a small system that one person can understand, so one person can make a difference. Say hello, pick something small, and ship it.
Slack invite: comingGitHub
The Slack invite link is not set up yet. In the meantime, GitHub is the place to talk.
Where we talk.
GitHub
Issues for bugs and ideas, pull requests for changes, and the design notes in the open. Open the repository →
Inside the desktop
A native Messenger window, so the community can be a conversation in the same place you work. How it works →
Good first contributions.
Small, real, and checkable. No HolyC needed for most of them.
Try an untested platform
Linux, Windows and Intel Macs are marked Untested on the Download page. Run it, then tell us what happened.
Measure what we have not
The oldest macOS that works, the least memory, and how much Classic uses while running.
Audit accessibility
Keyboard paths, contrast and text size. The page lists what exists and what is missing.
Read the security model
The guest is not audited. A second pair of eyes on the install and approval flow is the most useful review.
Share a theme
Window and icon styles export as one line of text that anyone can import.
Port an app
The porting method explains how a web or desktop app becomes a native HolyC window.
Native Messenger
Talk from inside the desktop.
One window for every network, with one store on your Mac and the networks behind a provider interface. The desktop only draws it and sends what you typed. Your keys and accounts stay on the host.
Sending is always your click, and a real account asks for approval the first time it syncs or sends.
CommunityWelcome. Say hello in #general.Planned
Slack bridgeA channel mirrored from Slack.Planned
Sample chatA scripted demo conversation.Built
Phase 1: the Messenger app and message service
PrototypeA native window with conversations, filters, unread badges, bubbles and a composer, over a host store. A scripted sample provider shows the whole path, with 19 service tests.
Phase 2: SMS and approvals
PlannedA real provider by polling, an approval card, and notifications for new messages.
Phase 3: Matrix and bridges
PlannedOne adapter for history and receipts across networks. Unofficial bridges carry ban risk, so each is opt-in. A Slack bridge would live here.
Phase 4: Telegram and Signal
PlannedThrough a client library or a command-line client.
Phase 5: Bitsocial communities
PlannedCommunities as channels, then a decision on direct messages.
Status: phase 1 is built on its own branch and is not merged into the main desktop yet. It has run against a private hub on the native build; it has not run in the x86 VM. The conversations in the picture are an illustration, not a live community. Details: the Messenger design note.
How we treat each other.
Be kind
Assume good faith. People come here with very different experience.
Say what you tested
Platform, version and what you saw. "Untested" is a fine answer and a useful one.
Keep secrets out
Never paste keys, tokens or personal data in public places.
Placeholder: a full code of conduct and a contact for reporting problems are still to be written.