v0.6.0: hard network fork; ship multi-persona + CDN restructure
Phases 1-5 of the Identity Architecture rollout are on master; Phase 6 (rotating DM IDs) is deferred. This bumps the protocol-breaking release: v0.5 and v0.6 cannot interoperate. Packaging: - Cargo + tauri.conf: 0.5.3 -> 0.6.0 - deploy.sh: drop -beta filename suffix - download.html: single v0.6.0 section with fork notice at the top; changelog entry summarising the five phases and the schema migration; Phase 6's rotating-DM-ID status noted as deferred Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Scott Reimers
parent
eea868b4cc
commit
8e35add7bb
7 changed files with 44 additions and 36 deletions
|
|
@ -24,42 +24,38 @@
|
|||
<div class="container">
|
||||
<section>
|
||||
<h1 style="font-size: 2rem; font-weight: 800; letter-spacing: -0.03em; margin-bottom: 0.25rem;">Download ItsGoin</h1>
|
||||
<p>Available for Android and Linux. Free and open source.</p>
|
||||
<p>Available for Android, Linux, and Windows. Free and open source.</p>
|
||||
|
||||
<h2 style="margin-top: 2rem;">Stable Release</h2>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">Version 0.5.3 — April 19, 2026</p>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">Multi-identity, export/import, fast startup, pagination, SAF support, AppImage video, and more. Recommended for daily use.</p>
|
||||
<div class="note" style="margin-top: 1rem; border-left: 3px solid var(--accent); padding-left: 0.9rem;">
|
||||
<strong>Network fork:</strong> v0.6 is a hard fork from v0.5. Older versions cannot connect to the v0.6 network. If you were on v0.5.3, upgrade to stay reachable. Export your identity from v0.5.3 (Settings → Export) and import it on first launch of v0.6.
|
||||
</div>
|
||||
|
||||
<h2 style="margin-top: 2rem;">v0.6.0 — April 21, 2026</h2>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">The privacy architecture overhaul. Network identity is decoupled from posting identity — peers cannot correlate network traffic to a posting identity, and users can hold multiple simultaneous posting identities (personas) on one device.</p>
|
||||
|
||||
<div class="downloads">
|
||||
<a href="itsgoin-0.5.3.apk" class="download-btn btn-android">
|
||||
<a href="itsgoin-0.6.0.apk" class="download-btn btn-android">
|
||||
Android APK
|
||||
<span class="sub">v0.5.3 stable</span>
|
||||
<span class="sub">v0.6.0</span>
|
||||
</a>
|
||||
<a href="itsgoin_0.5.3_amd64.AppImage" class="download-btn btn-linux">
|
||||
<a href="itsgoin_0.6.0_amd64.AppImage" class="download-btn btn-linux">
|
||||
Linux AppImage
|
||||
<span class="sub">v0.5.3 stable</span>
|
||||
<span class="sub">v0.6.0</span>
|
||||
</a>
|
||||
<a href="itsgoin-cli-0.5.3-linux-amd64" class="download-btn btn-linux">
|
||||
<a href="itsgoin-cli-0.6.0-linux-amd64" class="download-btn btn-linux">
|
||||
Linux CLI / Anchor
|
||||
<span class="sub">v0.5.3 stable</span>
|
||||
</a>
|
||||
<a href="itsgoin-0.5.3-windows-x64-setup.exe" class="download-btn btn-linux">
|
||||
Windows Installer
|
||||
<span class="sub">v0.5.3 stable</span>
|
||||
<span class="sub">v0.6.0</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
<h2 style="margin-top: 2rem;">Coming in Beta (0.6.x)</h2>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">The next beta introduces a major privacy architecture overhaul:</p>
|
||||
<ul style="color: var(--text-muted); font-size: 0.85rem; line-height: 1.6;">
|
||||
<li><strong>Multiple personas</strong> on one device — Public, Private, Work, per-conversation. No switching; all active at once.</li>
|
||||
<li><strong>Network-ID / Posting-ID split</strong> — peers can no longer correlate network traffic to a posting identity.</li>
|
||||
<li><strong>Ephemeral rotating DM identities</strong> — observers cannot link successive messages in a thread.</li>
|
||||
<li><strong>CDN-only DM propagation</strong> — removes the sender→recipient traffic signal entirely.</li>
|
||||
<li><strong>Multi-device support</strong> — phone + desktop share a persona without exposing the relationship.</li>
|
||||
<li><strong>File-holder CDN</strong> — replaces the upstream/downstream tree with flat lateral replication.</li>
|
||||
<ul style="color: var(--text-muted); font-size: 0.85rem; line-height: 1.6; margin-top: 1rem;">
|
||||
<li><strong>Multiple personas</strong> on one device — Public, Private, Work, whatever you want. No switching; all active at once. Filter the merged feed per persona; compose as any persona.</li>
|
||||
<li><strong>Network-ID / Posting-ID split</strong> — content is signed by a posting key, not the network endpoint. Peers cannot link network connections to posting identities.</li>
|
||||
<li><strong>CDN-only DM propagation</strong> — encrypted posts no longer have a sender→recipient traffic signal. They travel through the same CDN path as any other content.</li>
|
||||
<li><strong>Merged pull with recipient-match</strong> — DMs from strangers reach you without requiring a mutual follow. No distinguishable “searching for DMs” traffic pattern.</li>
|
||||
<li><strong>File-holder CDN</strong> — replaces the upstream/downstream tree with flat lateral holder sets (max 5 per file, LRU-capped). Delete-notice and manifest fan-out are now uniform.</li>
|
||||
</ul>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">See the <a href="design.html#identity-architecture">Identity Architecture section of the design doc</a> for the full plan. Beta releases will appear here as each phase ships.</p>
|
||||
<p style="color: var(--text-muted); font-size: 0.85rem;">See the <a href="design.html#identity-architecture">Identity Architecture section of the design doc</a> for details. Rotating DM identities (from the original plan) are deferred — they need more work on the connection model.</p>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
|
|
@ -116,6 +112,18 @@
|
|||
<section>
|
||||
<h2>Changelog</h2>
|
||||
<div class="changelog">
|
||||
<div class="changelog-date">v0.6.0 — April 21, 2026</div>
|
||||
<ul>
|
||||
<li><strong>Network fork from v0.5.</strong> The network protocol has changed enough that v0.5 and v0.6 cannot interoperate. Upgrade if you want to stay reachable.</li>
|
||||
<li><strong>CDN-only encrypted-post propagation.</strong> Direct <code>PostPush</code> for encrypted posts is removed; encrypted DMs look identical on the wire to any other encrypted post.</li>
|
||||
<li><strong>Flat per-file holder sets replace upstream/downstream trees.</strong> Each file tracks up to 5 most-recent peers it was exchanged with. Engagement diffs, manifest pushes, and delete notices all route through this holder set uniformly.</li>
|
||||
<li><strong>Merged pull with recipient-match.</strong> Pull queries contain a uniform list of NodeIds (follows + your own); server matches on post author OR wrapped-key recipient. Non-follower DMs now reach you via a normal pull cycle — no sender→recipient traffic signal.</li>
|
||||
<li><strong>Posting-key / network-key split.</strong> Content is signed with a dedicated posting key; the network endpoint uses a separate network key. Peers can no longer correlate posting identity to network traffic.</li>
|
||||
<li><strong>Multi-persona support.</strong> Hold multiple posting keys on one device; each peer sees distinct authors. Settings → Personas to create/manage; compose box picks which persona posts each item; feed has filter pills per persona.</li>
|
||||
<li><strong>pkarr default lookup suppressed.</strong> <code>clear_address_lookup()</code> + mDNS only; no implicit DNS publishing.</li>
|
||||
<li><strong>Schema: four legacy tables dropped</strong> (<code>post_upstream</code>, <code>post_downstream</code>, <code>blob_upstream</code>, <code>blob_downstream</code>); replaced with <code>file_holders</code>. One-way migration seeds the new table from the old ones on first launch. Also adds <code>post_recipients</code> index for merged pull, and <code>posting_identities</code> table for multi-persona.</li>
|
||||
</ul>
|
||||
|
||||
<div class="changelog-date">v0.5.3-beta — April 19, 2026</div>
|
||||
<ul>
|
||||
<li><strong>Feed pagination</strong> — Cursor-based pagination (20 posts/page) with pre-fetch and infinite scroll. Batched engagement queries (3 SQL queries instead of 4 per post). Media loads only for visible posts via IntersectionObserver.</li>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue