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

update member row

Browse Source
This commit is contained in:
reya
2026-10-01 10:18:36 +07:00
parent 75b0f49d9e
commit a93be19e81
6 changed files with 103 additions and 263 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/nip29-usage.md
+7 -5
View File
@@ -592,11 +592,13 @@ before they reach the consumer, so a replay cannot double-hydrate.
reactions and admin pin/delete, a pins strip, a fork banner, and leave. Opening a
group also fills the sidebar with the group itself — banner (the `39000` `banner`
tag, falling back to its `picture`), avatar and name, a row of info / edit / invite /
members / leave buttons, and the collapsible `Admins`/`Members` lists. Members are
clickable and open a profile dialog. The panel has no header: the group's `about` lives in the
details dialog, and the composer's leading button shows or hides the sidebar's
group information. What a given account may actually do is the relay's call; the
client shows the refusal verbatim.
leave buttons, and the collapsible `Admins`/`Members` lists. Clicking a member opens
a dropdown menu (view profile, copy npub, and — for admins — remove from group).
There is no members-and-roles dialog: adding a member is done through the invite
flow, and roles are read-only. The panel has no header: the group's `about` lives
in the details dialog, and the composer's leading button shows or hides the
sidebar's group information. What a given account may actually do is the relay's
call; the client shows the refusal verbatim.
- **The composer uploads to the configured blossom server.** `GroupPanel`'s
paperclip uploads one file at a time, unencrypted, and appends its URL to the
message on send — the same plain-attachment path the chat composer uses when a