Tighten the prose around chat requests
This commit is contained in:
parent
939caadc32
commit
5c38fdbb44
3 changed files with 10 additions and 13 deletions
|
|
@ -623,13 +623,13 @@ care about, so that a stranger cannot bury them.
|
|||
|
||||
Acceptance:
|
||||
|
||||
- The chat list has a Conversations tab and a Requests tab, each carrying its own count.
|
||||
- The chat list has a Conversations tab and a Requests tab, each with its own count.
|
||||
- Someone I follow opens under Conversations and someone I share nothing with opens under Requests.
|
||||
A member of a space I belong to, a sender enough of my follows follow, and a message carrying
|
||||
enough proof of work each count as a connection too.
|
||||
- Choosing Requests shows the held conversation, which reads and opens like any other.
|
||||
- A chat I have written in is mine whatever I know about the other person, so answering a request
|
||||
moves it to Conversations.
|
||||
- Choosing Requests shows the chat held there, and it reads and opens like any other.
|
||||
- A chat I have written in appears under Conversations whatever I know about the other person,
|
||||
so answering a request moves it there.
|
||||
|
||||
## Articles & threads
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ const seedPerson = (space: SeededSpace, user: TestUser, name: string, ...rooms:
|
|||
|
||||
const chatFilter = (page: Page) => page.locator(".secondary-nav input[type='text']")
|
||||
|
||||
// The chat list renders twice, once per breakpoint, so a tab is named inside the sidebar.
|
||||
// The chat list renders twice, once per breakpoint, so this scopes the tab to the sidebar.
|
||||
const chatTab = (page: Page, name: string) =>
|
||||
page.locator(".secondary-nav").getByRole("button", {name})
|
||||
|
||||
|
|
|
|||
|
|
@ -148,8 +148,8 @@
|
|||
Message Requests
|
||||
</strong>
|
||||
<p class="text-sm opacity-50">
|
||||
Messages from people you have no connection to wait in the Requests tab of your chat list.
|
||||
These two thresholds are the other ways in.
|
||||
Messages from people you have no connection to appear in the Requests tab of your chat list.
|
||||
A sender who meets either threshold below reaches your conversations instead.
|
||||
</p>
|
||||
<Field>
|
||||
{#snippet label()}
|
||||
|
|
@ -170,8 +170,8 @@
|
|||
{#snippet info()}
|
||||
<p>
|
||||
A sender who spends this much proof of work reaches your conversations whether or not
|
||||
you know them. Each step up doubles what it costs them, and {PLATFORM_NAME} spends 16 bits
|
||||
on every message you send.
|
||||
you know them. Each step up doubles the work they have to do, and {PLATFORM_NAME} spends 16
|
||||
bits on every message you send.
|
||||
</p>
|
||||
{/snippet}
|
||||
</Field>
|
||||
|
|
@ -192,10 +192,7 @@
|
|||
bind:value={$settings.min_dm_wot} />
|
||||
{/snippet}
|
||||
{#snippet info()}
|
||||
<p>
|
||||
How many of the people you follow have to follow a sender for you to count as knowing
|
||||
them.
|
||||
</p>
|
||||
<p>A sender counts as known when this many of the people you follow also follow them.</p>
|
||||
{/snippet}
|
||||
</Field>
|
||||
</Card>
|
||||
|
|
|
|||
Loading…
Reference in a new issue