How Keychat thinks about group
The essence of a group is to establish a boundary where only members can participate in communication. In a decentralized system, this boundary can only be enforced through encryption.
Groups generally fall into two categories: **chat groups** and **feed groups**. The former focuses on interaction—members are visible to each other, and messages are shared with the entire group. The latter is centered around content sharing—members are invisible to one another, and messages are individually encrypted for each recipient rather than broadcast to all.
Compared to chat groups, feed groups create much less social pressure, allowing both the sharer and the recipients to interact in a more relaxed and private environment.
Replies (5)
This whole “feed group” thing has been tried many times before. Called “circles” etc. it ends up being way too complex and over-engineered. Users just don’t get it because there’s no real life corollary.
You can do whatever you want to share read/decrypt keys on the backend, but just make the UX what people already understand. Visibility settings, private accounts, newsletters, etc.
The strength of keychat is the mail analogy. Keep building on your strengths
The description above mischaracterizes a Feed Group — it’s not a “group.”
From the poster's perspective, it's a broadcast channel to friends.
From the viewer's perspective, it's a feed composed of posts from multiple friends.
Is there a private share app that looks like old Facebook in Keychat?
Not yet. There’s a wide range of possible product designs that sit between fully end-to-end encrypted chat and completely public microblogging.
