ux+fix: rename Network Identity → Device Address (UI) + redundancy authors
#6: UI rename — Network Identity → Device Address. Just labels/wording, no backend changes. Tauri command names (list_identities, create_identity, etc.) and DTO fields stay as-is; the rename is purely user-facing. Settings labels, lightbox titles, toasts, danger-zone text, and welcome-screen "Import an Identity" button all updated. Distinguishes more clearly from Personas (which ARE the posting identity peers see). #7: Bug fix — redundancy showed 0 for new posts. Root cause: get_redundancy_summary queried SELECT p.id FROM posts WHERE p.author = ?1 with ?1 = self.node_id (the device's network NodeId). After the v0.6.0 network/posting-ID split, posts are authored by posting identities (personas), not the network NodeId — so the query returned 0 of my posts and the redundancy panel showed all zeros. Fix: storage::get_redundancy_summary now takes &[NodeId] and uses WHERE author IN (?, ?, ...) over every persona on the device. Node::get_redundancy_summary gathers them via list_posting_identities() before delegating. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
83fd30753f
commit
100ea55a15
4 changed files with 50 additions and 29 deletions
|
|
@ -236,7 +236,7 @@
|
|||
<p class="empty-hint" style="margin-bottom:0.5rem;font-size:0.78rem;line-height:1.5">
|
||||
<strong style="color:#7fdbca">Personas</strong> are who you are to peers — the keys you post and message with. Most people only need one. To move your account to a new device, you <em>export your personas</em> from this device and <em>import them</em> on the new one.
|
||||
<br><br>
|
||||
<strong style="color:#888">Identities</strong> below are this device's own network address — usually not what you want to move. Leave them alone unless you know why you're touching them.
|
||||
<strong style="color:#888">Device Address</strong> below is this device's own network endpoint — usually not what you want to move. Leave it alone unless you know why you're touching it.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
|
|
@ -259,14 +259,14 @@
|
|||
</div>
|
||||
|
||||
<div class="section-card" style="text-align:center">
|
||||
<h3 style="margin-bottom:0.4rem;font-size:0.85rem;color:#888">Identities (advanced)</h3>
|
||||
<h3 style="margin-bottom:0.4rem;font-size:0.85rem;color:#888">Device Address (advanced)</h3>
|
||||
<p class="empty-hint" style="margin-bottom:0.5rem;font-size:0.72rem">
|
||||
This device's network address. Changing this is rarely useful — it lets you move the device's QUIC endpoint, NOT your posting identity.
|
||||
This device's network endpoint — the QUIC address peers use to reach you. Changing this rotates the device's network identifier but does NOT change your posting identity (personas). Rarely useful.
|
||||
</p>
|
||||
<div id="identities-list" style="margin-bottom:0.5rem"></div>
|
||||
<div style="display:flex;gap:0.5rem;justify-content:center;flex-wrap:wrap">
|
||||
<button id="create-identity-btn" class="btn btn-ghost btn-sm">New Identity</button>
|
||||
<button id="import-identity-btn" class="btn btn-ghost btn-sm">Import Key</button>
|
||||
<button id="create-identity-btn" class="btn btn-ghost btn-sm">New Device Address</button>
|
||||
<button id="import-identity-btn" class="btn btn-ghost btn-sm">Import Address Key</button>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
|
@ -316,7 +316,7 @@
|
|||
|
||||
<div class="section-card">
|
||||
<h3>Danger Zone</h3>
|
||||
<p class="empty-hint">Delete all local data. Identity key preserved.</p>
|
||||
<p class="empty-hint">Delete all local data. Device address key preserved.</p>
|
||||
<button id="reset-data-btn" class="btn btn-danger btn-full">Reset All Data</button>
|
||||
</div>
|
||||
</section>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue