Repository navigation
feat(stacker): add stack room create for unencrypted family rooms - #278
Open
arthware-dev wants to merge 1 commit into
Open
arthware-dev wants to merge 1 commit into
arthware-dev wants to merge 1 commit into
Conversation
arthware-dev
force-pushed
the
feature/0.5.0-beta.1
branch
from
October 20, 2026 19:20
0030ec5 to
524d008
Compare
Element X encrypts every room it creates and cannot switch that off. An encrypted room ties the family to their device keys: a new phone without an old device or the recovery key loses the room's history. Rooms the bots work in do not need encryption, since the server and the bots are the family's own Mac. An admin now writes `stack room create <name>` in the Server Room and Stacker answers with a link to the new room. The room: - is not encrypted, - sits in the Family space (its own `m.space.parent` and the space's `m.space.child`), - has the family members with a chat account and the archivist invited, and the family's admins as its admins. A name starting with `Topic:` or `Thema:` becomes a topic room, as before. A name already in use, or one whose address is taken, gets a link to that room and no second room. Non-admins are refused like for the other changing commands. The work is done by `stack messages room create`, which now also takes just a name (`stack messages room create "Topic: Garden"`), derives the alias from it, and invites the family. The core API gains a `room-create` command that runs it for Stacker. A taken alias no longer exits with an error: the command names the existing room instead.
arthware-dev
force-pushed
the
feat/stacker-room-create
branch
from
October 20, 2026 19:52
646696a to
4c34d12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
stack room create <name>in the Server Room: Stacker creates the room unencrypted in the Family space, invites the family and the archivist, makes the family's admins its admins, and replies with a link. A name starting withTopic:orThema:becomes a topic room as before. A name or address already in use gets a link to that room and no second room. Non-admins are refused like for the other changing commands.stack messages room create, which now also takes just a name (stack messages room create "Topic: Garden"), derives the alias from it, sets the room's space parent and invites the family. The core API gains aroom-createcommand that runs it for Stacker, with the name as one argument. A taken alias no longer exits with an error; the command names the existing room.Defaults to confirm
messagesin their stacklets) plus the archivist. People get an invite to accept;stack messages setupforce-joins its own rooms instead. Recommendation: keep invites, so nobody gets a room they did not ask for.