reya/coop
1
0
Fork 0
Code Issues Pull Requests 1 Releases 3 Activity

add community creation flow

Browse Source
This commit is contained in:
reya
2026-09-19 08:14:03 +07:00
parent 907347d002
commit 0328d35945
8 changed files with 126 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concord-usage.md
+4 -3
View File
@@ -542,9 +542,10 @@ client.subscribe(filter).with_id(sub_id).await?;
`crates/community`.** `concord` has no subscriptions, no `init`, and no
`Entity<Community>`; `community::CommunityRegistry` owns one `Entity<Community>`
per state document, subscribes when a community's plane set changes, and
re-folds on an inbound wrap. Nothing observes `CommunityEvent` yet, and
`CommunityRegistry::create` persists the genesis locally without publishing it
to the metadata's relays.
re-folds on an inbound wrap. The sidebar observes the registry, logs
`CommunityEvent::Error` through `log::error!`, and its "New community" row opens
a name prompt that calls `CommunityRegistry::create`. `create` still persists
the genesis locally without publishing it to the metadata's relays.
- **Account-key writers take any signer, not `&Keys`.** `genesis`,
`ControlWriter`, the guestbook and chat `seal_rumor`s, the `list` builders, and
the `cord05` invite writers (`build_direct_invite` / `unwrap_direct_invite`,