# New feature: Group Types **URL:** \ **Category:** Feature Proposal\ **Tags:** moderation\ **Created:** [February 20, 2019, 6:49pm UTC](https://forum.delta.chat/t/new-feature-group-types/263 "2019-02-20T18:49:21Z")\ **Posts on this page:** 9\ **Page:** 3
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [October 25, 2025, 2:47pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/42 "2025-10-25T14:47:12Z")
key rotation is complicated, if one member doesn’t receive the message with the new key they will not be able to read the group anymore, as I already mentioned in the other thread, it is better to keep things simple: - group with owner is mainly for public groups and there it doesn’t matter key is fixed, - private groups don’t need owners and there message is encrypted to members and not with fixed key ---
**Author:** ![Minim](https://forum.delta.chat/letter_avatar_proxy/v4/letter/m/ccd318/32.png) [@Minim](https://forum.delta.chat/u/Minim)\ **Post date:** [October 25, 2025, 3:03pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/43 "2025-10-25T15:03:33Z")
Would key rotation be easier in the “blind” groups? As in the owner could help co-ordinate the key rotation to provide many-to-many comms, not just 1-to-many. ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [October 25, 2025, 3:07pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/44 "2025-10-25T15:07:20Z")
it is the same problem, you have no warranty all your subscribers received the new key, so you can’t rotate, you could implement some confirmation mechanism in which you pre-advertize the upcoming key but keep using the old one until all subscribers confirm they received the new key, but just one inactive member would delay the rotation potentially forever, plus such auto-reply/confirm mechanism for subscribers have privacy considerations **it is a blind group == channel, key rotation is not needed, it is probably public channel, if used privately for people you trust then it doesn’t matter** ---
**Author:** ![9er](https://forum.delta.chat/user_avatar/forum.delta.chat/9er/32/2678_2.png) [@9er](https://forum.delta.chat/u/9er)\ **Post date:** [October 28, 2025, 8:45pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/45 "2025-10-28T20:45:56Z")
> [@adbenitez](#): > > but keep using the old one until all subscribers confirm they received the new key It will be easier without this confirmation part. Admin adds a second key, and in a couple of days/weeks drops the first one. ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [October 30, 2025, 3:56pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/46 "2025-10-30T15:56:10Z")
that would cause “unable to decrypt” experiences, which is not acceptable ---
**Author:** ![eidolog](https://forum.delta.chat/letter_avatar_proxy/v4/letter/e/a9adbd/32.png) [@eidolog](https://forum.delta.chat/u/eidolog)\ **Post date:** [November 1, 2025, 11:41am UTC](https://forum.delta.chat/t/new-feature-group-types/263/47 "2025-11-01T11:41:21Z")
Am I correct in understanding that newly added group members won’t see previously published messages in the group? Is this the same for channels? ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [November 1, 2025, 5:17pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/48 "2025-11-01T17:17:16Z")
> [@eidolog](#): > > Am I correct in understanding that newly added group members won’t see previously published messages in the group? yes. > [@eidolog](#): > > Is this the same for channels? yes. for groups, this is can be regarded as a privacy feature. however, reason is also that it is just not done and not easy 🙂 still, one can resend one own’s messages after a member is added. ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [January 24, 2026, 6:57pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/49 "2026-01-24T18:57:47Z")
> [@9er](#): > > IMHO it probably should be a separated topic ‘Owned groups’, with all corresponding messages from both linked topics moved there (if it is technically possible for moderators). since the rest is already done, it makes sense to have a dedicated on-point topic, I created it at: > [@Spec Proposal: Super Groups](https://support.delta.chat/t/spec-proposal-super-groups/4644): > > Delta Chat Spec Proposal: Super Groups Terminology semi-public group: A group that is intended to be used for more or less public interactions, its invitation link can be shared in public spaces like social media or websites. It is “semi-public” and not “public” because it is up to the members to distribute its invitation link, they could keep it private and only invite certain people or share it only in certain spaces, that is: there is no public discovery of the group inside Delta Chat. The p… to recapitulate this was the latest state of the proposal for “Owned Groups”: > [@New feature: Group Types](https://support.delta.chat/t/new-feature-group-types/263/37): > > updating the status of this proposal: in the meantime “Blind group” already got implemented via the new “channels”! partying_faceonly type missing is “Owned groups”, here are some more recent ideas I had for “owned groups”: group creator is “owner” of the group, the group works with a symmetric key that is a subkey or in a way cryptographically verifiable/tied to the public key of the “owner” (with channels we are introducing this type of chat, it is also useful for super-groups with l… let’s close this topic and continue the discussion about “Owned Groups” (a.k.a Super groups) in the other thread ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [January 24, 2026, 6:58pm UTC](https://forum.delta.chat/t/new-feature-group-types/263/50 "2026-01-24T18:58:41Z")
[Previous page](https://forum.delta.chat/t/new-feature-group-types/263.md?page=2)