333 lines
35 KiB
HTML
333 lines
35 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<title>Download — ItsGoin</title>
|
|
<meta name="description" content="Download the ItsGoin app for Android and Linux. Free, open source, Apache 2.0.">
|
|
<link rel="stylesheet" href="style.css">
|
|
</head>
|
|
<body>
|
|
<nav>
|
|
<a href="index.html" class="logo">ItsGoin</a>
|
|
<button class="menu-toggle" onclick="this.parentElement.querySelector('.links').classList.toggle('open')" aria-label="Menu">☰</button>
|
|
<div class="links">
|
|
<a href="index.html">About</a>
|
|
<a href="tech.html">How It Works</a>
|
|
<a href="design.html">Design</a>
|
|
<a href="download.html" class="active">Download</a>
|
|
<a href="contribute.html">Contribute</a>
|
|
<a href="https://discord.gg/pCjMbY9PmN">Discord</a>
|
|
</div>
|
|
</nav>
|
|
|
|
<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 style="color: var(--text-muted); font-size: 0.85rem;">Version 0.4.3 — March 22, 2026</p>
|
|
|
|
<div class="downloads">
|
|
<a href="itsgoin-0.4.3.apk" class="download-btn btn-android">
|
|
Android APK
|
|
<span class="sub">v0.4.3</span>
|
|
</a>
|
|
<a href="itsgoin_0.4.3_amd64.AppImage" class="download-btn btn-linux">
|
|
Linux AppImage
|
|
<span class="sub">v0.4.3</span>
|
|
</a>
|
|
</div>
|
|
</section>
|
|
|
|
<section>
|
|
<h2>Installation</h2>
|
|
|
|
<div class="card">
|
|
<h3 style="color: var(--accent);">Android</h3>
|
|
<ol class="steps">
|
|
<li><strong>Download the APK</strong> — Tap the button above. Your browser may warn that this type of file can be harmful — tap <strong>Download anyway</strong>.</li>
|
|
<li><strong>Open the file</strong> — When the download finishes, tap the notification or find <code>itsgoin-0.4.3.apk</code> in your Downloads folder and tap it.</li>
|
|
<li><strong>Allow installation</strong> — Android will ask you to allow installs from this source. Tap <strong>Settings</strong>, toggle <strong>"Allow from this source"</strong>, then go back and tap <strong>Install</strong>.</li>
|
|
<li><strong>Launch the app</strong> — Once installed, tap <strong>Open</strong> or find ItsGoin in your app drawer.</li>
|
|
</ol>
|
|
<div class="note">
|
|
<strong>Note:</strong> If you don't see the "Allow from this source" prompt, go to <strong>Settings → Apps → Special access → Install unknown apps</strong> and enable it for your browser.
|
|
</div>
|
|
</div>
|
|
|
|
<div class="card">
|
|
<h3 style="color: var(--green);">Linux (AppImage)</h3>
|
|
<ol class="steps">
|
|
<li><strong>Download the AppImage</strong> — Click the button above to download.</li>
|
|
<li><strong>Make it executable</strong> — Open a terminal and run:<br><code>chmod +x itsgoin_0.4.3_amd64.AppImage</code></li>
|
|
<li><strong>Run it</strong> — Double-click the file, or from the terminal:<br><code>./itsgoin_0.4.3_amd64.AppImage</code></li>
|
|
</ol>
|
|
<div class="note">
|
|
<strong>Note:</strong> If it doesn't launch, you may need to install FUSE:<br><code>sudo apt install libfuse2</code> (Debian/Ubuntu) or <code>sudo dnf install fuse</code> (Fedora).
|
|
</div>
|
|
</div>
|
|
</section>
|
|
|
|
<section>
|
|
<h2>Changelog</h2>
|
|
<div class="changelog">
|
|
<div class="changelog-date">v0.4.3 — March 22, 2026</div>
|
|
<ul>
|
|
<li><strong>Lock contention overhaul</strong> — All conn_mgr lock holds during network I/O eliminated across 14 handlers. Brief locks for data gathering only; all network operations run lock-free.</li>
|
|
<li><strong>StoragePool</strong> — 8 concurrent SQLite connections in WAL mode replace the single Mutex. Reads run fully parallel; writes serialize only at the SQLite level.</li>
|
|
<li><strong>Initial exchange fix</strong> — Failed initial exchanges now abort the mesh upgrade instead of silently continuing with a broken connection.</li>
|
|
<li><strong>Connect timeout</strong> — connect_to_peer and connect_to_anchor now use a consistent 15s timeout. ResolveAddress adds 5s per-query timeout (was unbounded).</li>
|
|
<li><strong>Worm cascade unlock</strong> — WormLookup, ContentSearch, and WormQuery use connection snapshots for lock-free fan-out.</li>
|
|
<li><strong>Bottom nav bar</strong> — Mobile/tablet (≤768px) gets a fixed bottom navigation bar with icon tabs. Desktop keeps the top tab bar.</li>
|
|
<li><strong>Text size update</strong> — Five options: XS (75%), S (100%), M (125% default), L (150%), XL (200%). Persisted to localStorage for instant restore on startup.</li>
|
|
<li><strong>Startup fix</strong> — Fixed blocking_lock panic that prevented app from launching (async runtime conflict). StoragePool reduced to 4 connections for Android compatibility.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.4.2 — March 22, 2026</div>
|
|
<ul>
|
|
<li><strong>Welcome screen</strong> — Startup shows “How’s it goin?” with staggered counters (connections, posts, messages, reacts, comments) while the backend bootstraps. Replaces the blank-screen wait.</li>
|
|
<li><strong>Status ticker</strong> — Header ticker shows new posts, messages, reactions, comments, and connection state changes as they arrive.</li>
|
|
<li><strong>Notification improvements</strong> — Tauri plugin → Web Notification API → notify-rust fallback chain. Linux native desktop notifications now work.</li>
|
|
<li><strong>Responsive text scaling</strong> — Small/Normal/Large text size (100%/150%/200%), persisted via settings. Default bumped to Normal (150%).</li>
|
|
<li><strong>Diagnostics popover</strong> — Network diagnostics moved from inline section to overlay popover. Connections loaded on-demand. Timer countdowns removed.</li>
|
|
<li><strong>Share details lightbox</strong> — QR code + connect string in a modal overlay from People tab.</li>
|
|
<li><strong>Connect string improvement</strong> — Prefers external address (UPnP/public IPv6/observed) over local bind address.</li>
|
|
<li><strong>Stale N1 fix</strong> — Disconnected social routes excluded from N1 share. Prevents dead nodes appearing online to peers.</li>
|
|
<li><strong>Replication handler fix</strong> — Actively fetches posts + blobs from requester after accepting replication. Previously relied on pull cycle which doesn’t work for infrastructure nodes.</li>
|
|
<li><strong>Hole punch fix</strong> — Target-side registers publicly routable remote address for relay introduction. Fixes address injection for subsequent connections.</li>
|
|
<li><strong>Replication semaphore</strong> — Concurrent replication handlers capped at 3 to prevent overload.</li>
|
|
<li><strong>Peer labels</strong> — Display names now show truncated node ID for disambiguation.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.4.1 — March 21, 2026</div>
|
|
<ul>
|
|
<li><strong>Security: Reaction signatures</strong> — Reactions now carry ed25519 signatures. Forged reactions from other NodeIds are rejected. Backward-compatible with unsigned reactions from older nodes.</li>
|
|
<li><strong>Security: Comment signature verification</strong> — Comment signatures (already present) are now verified on receipt. Forged comments rejected.</li>
|
|
<li><strong>Security: Reaction removal auth</strong> — Only the reactor or post author can remove reactions. Previously any peer could strip reactions.</li>
|
|
<li><strong>Security: BlobHeader author verification</strong> — Header rebuild verifies author against stored post, not trusted from payload.</li>
|
|
<li><strong>Lock contention: ManifestPush discovery</strong> — cm lock released before PostFetch network I/O. Was holding lock during entire discovery (5s+ freeze).</li>
|
|
<li><strong>Lock contention: Pull request handler</strong> — Load posts under lock, filter without lock, brief re-lock for is_deleted. Was holding lock during full post list iteration.</li>
|
|
<li><strong>Lock contention: Pull sender</strong> — Split into two brief locks (store, then batch upstream+sync). Was holding one long lock for all operations.</li>
|
|
<li><strong>Lock contention: Engagement checker</strong> — Batch writes per chunk with single lock. Was acquiring lock per post (100+ times).</li>
|
|
<li><strong>Data cleanup</strong> — Post deletion now cleans up post_downstream, post_upstream, and seen_engagement tables.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.4.0 — March 21, 2026</div>
|
|
<ul>
|
|
<li><strong>Protocol v4: Header-driven sync</strong> — Major sync protocol revision. ManifestPush now triggers post discovery from CDN tree headers. Bandwidth reduced ~90% for established nodes.</li>
|
|
<li><strong>Slim PullSyncRequest</strong> — Per-author timestamps replace full post ID lists. Request size drops from O(posts) to O(follows). Backward-compatible with v3 peers.</li>
|
|
<li><strong>Tiered pull frequency</strong> — Pull cycle checks every 60s but only syncs stale authors (4-hour default). Full pull only on first tick. Most ticks do nothing.</li>
|
|
<li><strong>Tiered engagement checks</strong> — Engagement polling frequency scales with content age: 5min (<72h), 1hr (3-14d), 4hr (14-30d), 24hr (>30d). Single SQL query filters due posts.</li>
|
|
<li><strong>Header-driven post discovery</strong> — ManifestPush triggers PostFetch for missing followed-author posts (capped at 10 per manifest). CDN tree becomes the notification system.</li>
|
|
<li><strong>Multi-upstream (3 max)</strong> — Posts track up to 3 upstream sources with priority ordering. Engagement diffs sent to all upstreams. Fallback on upstream failure.</li>
|
|
<li><strong>Lock contention fixes</strong> — 6 hot paths optimized: get_blob_for_post (3→1 locks), prefetch (lock-free blob checks), serve_post (4→2 locks), badge cycle (N+2→1 IPC call).</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.6 — March 20, 2026</div>
|
|
<ul>
|
|
<li><strong>Network indicator</strong> — Header shows connection status dot (black/red/yellow/green for 0/1/2-10/11+ connections) with capability labels (Public, Server).</li>
|
|
<li><strong>Tab badges</strong> — Feed shows new post count, My Posts shows new engagement count, People shows online count, Messages shows unread conversation count. Numbers only, no labels.</li>
|
|
<li><strong>Message read tracking</strong> — Conversations marked as read on open, close, and send. Prevents re-notification of already-seen messages.</li>
|
|
<li><strong>Active CDN replication</strong> — All devices proactively request replication of their recent posts (<72h) to connected peers. Targets prioritized: desktops > anchors > phones. Graceful with small networks (1 peer = 1 replica). ReplicationRequest/Response (0xE1/0xE2) wire messages.</li>
|
|
<li><strong>Device roles</strong> — Nodes classified as Intermittent (phones), Available (desktops), or Persistent (anchors). Advertised in InitialExchange. Influences replication target selection and budget defaults.</li>
|
|
<li><strong>Bandwidth budgets</strong> — Hourly replication budget (content pulled to cache) and delivery budget (content served). Phones: 100MB/1GB, Desktops: 200MB/2GB, Anchors: 200MB/1GB. Auto-reset hourly. Blob serving declines when delivery budget exhausted.</li>
|
|
<li><strong>Cache management</strong> — 1GB default cache limit (configurable 256MB–unlimited). Eviction cycle now active (was implemented but never started). Priority scoring with share-link boost (+100 for 3+ downstream). Cache pressure score (0–255) for future budget advertisement.</li>
|
|
<li><strong>Engagement distribution fix</strong> — BlobHeader JSON now rebuilt after processing BlobHeaderDiff ops. Previously reactions/comments stored in tables but header JSON stayed stale, breaking pull-based sync for downstream peers.</li>
|
|
<li><strong>Tombstone system</strong> — Deleted reactions/comments are tombstoned (<code>deleted_at</code> timestamp) instead of hard-deleted. Tombstones propagate through pull sync, ensuring deletes reach peers that missed the real-time diff.</li>
|
|
<li><strong>Persistent notifications</strong> — Notification tracking backed by <code>seen_engagement</code> and <code>seen_messages</code> tables. Only notifies on genuinely unseen content. Survives app restarts.</li>
|
|
<li><strong>DOS hardening</strong> — BlobHeaderDiff fan-out capped at 10 concurrent sends. Blob prefetch capped at 20 per cycle. PostDownstreamRegister capped at 50 per sync. Delivery budget enforcement on blob serving.</li>
|
|
<li><strong>Pull preference</strong> — Blob fetches prefer non-anchor sources (phones > desktops > replicas > anchors) to preserve anchor delivery budget for web requests.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.5 — March 20, 2026</div>
|
|
<ul>
|
|
<li><strong>Private blob encryption</strong> — Attachments on encrypted posts (Friends, Circle, Direct) are now encrypted with the same CEK as the post text. Public blobs remain plaintext. CID computed on ciphertext preserves content addressing.</li>
|
|
<li><strong>Blob prefetch on sync</strong> — When posts are pulled from peers, their attachments are eagerly fetched for offline availability. Previously blobs were only fetched on view.</li>
|
|
<li><strong>Crypto refactoring</strong> — Extracted reusable primitives: <code>encrypt_bytes_with_cek</code>, <code>decrypt_bytes_with_cek</code>, <code>unwrap_cek_for_recipient</code>, <code>unwrap_group_cek</code>. Foundation for encrypted blob storage and future chunk-level encryption.</li>
|
|
<li><strong>Intent-based post filtering</strong> — Feed, My Posts, and Messages now filter on the author's original visibility intent (<code>intentKind</code>) rather than encryption state.</li>
|
|
<li><strong>Encrypted receipt slots</strong> — Private messages get encrypted receipt and comment slots in BlobHeader. Delivery indicators, read receipts, and message reactions.</li>
|
|
<li><strong>Download filename sanitization</strong> — Prevents path traversal in downloaded file names.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.4 — March 18, 2026</div>
|
|
<ul>
|
|
<li><strong>Comment edit & delete</strong> — Edit or delete your own comments. Trust-based: post authors can also delete comments on their posts. Propagates via BlobHeaderDiff to all holders.</li>
|
|
<li><strong>Native notifications</strong> — System notifications via Tauri plugin (works on all platforms). Notifications for messages, new posts, reactions, and comments. Configurable in Settings with button-group toggles.</li>
|
|
<li><strong>Forward-compatible protocol</strong> — Unknown BlobHeaderDiffOp variants are silently ignored instead of crashing deserialization. Prevents old nodes from breaking when new features are added.</li>
|
|
<li><strong>Following: Online/Offline</strong> — Self removed from following list. Offline follows hidden behind lightbox popup. Shows expanded if no one is online.</li>
|
|
<li><strong>DM filter fix</strong> — Sent direct messages no longer appear in My Posts tab.</li>
|
|
<li><strong>Comment threading fix</strong> — Comments now work correctly in My Posts tab (duplicate element ID scoping fix).</li>
|
|
<li><strong>Dropdown text fix</strong> — Select dropdowns across the app now have legible text in WebKitGTK native popups.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.3 — March 16, 2026</div>
|
|
<ul>
|
|
<li><strong>IPv6 HTTP address fix</strong> — Nodes with public IPv6 now correctly advertise their real address for direct browser access, instead of <code>0.0.0.0</code>. Fixes share link video/image serving for IPv6-reachable nodes.</li>
|
|
<li><strong>Video preload fix</strong> — Share link videos and in-app videos from peers now buffer properly for playback (<code>preload="auto"</code>). Previously only the first frame loaded.</li>
|
|
<li><strong>Connection rate limiting</strong> — Incoming connections that fail authentication are rate-limited per source IP (3 attempts, then exponential backoff up to ~4 minutes). Prevents CPU exhaustion from rogue or stale nodes spamming auth failures.</li>
|
|
<li><strong>Schema versioning</strong> — Database tracks schema version via <code>PRAGMA user_version</code>. Future upgrades can run data migrations automatically. Databases too old to migrate are reset cleanly.</li>
|
|
<li><strong>N2/N3 freshness</strong> — TTL reduced from 7 days to 5 hours. Full N1/N2 state re-broadcast every 4 hours catches missed diffs.</li>
|
|
<li><strong>Bootstrap isolation recovery</strong> — 24 hours after startup, nodes verify the bootstrap anchor is within N1/N2/N3 reach. If absent, they reconnect and request referrals. Bootstrap is added to sticky N1 for 24 hours so mesh peers discover it via diffs.</li>
|
|
<li><strong>Following: Online/Offline</strong> — People tab splits followed peers into Online and Offline sections with “Last online” timestamps.</li>
|
|
<li><strong>DM filter</strong> — Direct messages no longer appear in My Posts tab.</li>
|
|
<li><strong>Bidirectional engagement propagation</strong> — Reactions and comments now flow both upstream (toward author) and downstream through the CDN tree. Previously only downstream propagation existed, so the post author often never received reactions.</li>
|
|
<li><strong>Auto downstream registration</strong> — Nodes that receive a post via pull sync or push notification automatically register as downstream peers. This ensures engagement diffs reach all holders without manual registration.</li>
|
|
<li><strong>Upstream tracking</strong> — New <code>post_upstream</code> table records which peer each post was received from, enabling engagement to flow back toward the author hop-by-hop through the CDN tree.</li>
|
|
<li><strong>N2/N3 freshness</strong> — TTL reduced from 7 days to 5 hours. Full N1/N2 state re-broadcast every 4 hours catches missed diffs. Disconnect cleanup already removes departed peer's contributions immediately.</li>
|
|
<li><strong>Bootstrap isolation recovery</strong> — 24 hours after startup, nodes check if the bootstrap anchor is within their N1/N2/N3 reach. If absent, they reconnect and request referrals. The bootstrap is added to sticky N1 for 24 hours so mesh peers discover it via diffs, bridging isolated network segments back together.</li>
|
|
<li><strong>Following: Online/Offline</strong> — People tab splits followed peers into Online and Offline sections with “Last online” timestamps. DMs no longer appear in My Posts.</li>
|
|
<li><strong>Video playback</strong> — Videos now play correctly in-app on both desktop and Android.</li>
|
|
<li><strong>On-demand blob fetch</strong> — Media attachments that haven't synced locally are fetched from peers when you view them.</li>
|
|
<li><strong>Image loading fix</strong> — Asset protocol properly configured for streaming images from disk. Fallback to IPC if asset protocol fails.</li>
|
|
<li><strong>Image lightbox</strong> — Click any image to view full-size. Escape or click to close.</li>
|
|
<li><strong>File attachments</strong> — Attach any file type to posts. Non-media files show as download buttons with a trust warning prompt.</li>
|
|
<li><strong>Audio player</strong> — Audio attachments display with native playback controls.</li>
|
|
<li><strong>Video download</strong> — Download button under video player saves to Downloads folder.</li>
|
|
<li><strong>Share link fix</strong> — Fixed redirect to <code>0.0.0.0</code> — unroutable addresses are now skipped, falling through to QUIC proxy correctly.</li>
|
|
<li><strong>TCP hole punch protocol</strong> — New wire messages (TcpPunchRequest/Result) enable direct HTTP serving from nodes to browsers, reducing proxy load on itsgoin.net.</li>
|
|
<li><strong>Tiered web serving</strong> — Share links try direct redirect to HTTP-capable post holders before falling back to QUIC proxy.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.1 — March 13, 2026</div>
|
|
<ul>
|
|
<li><strong>Engagement sync</strong> — Pull sync now fetches reactions, comments, and policies from peers. Previously these only propagated via real-time push.</li>
|
|
<li><strong>Profile push fix</strong> — Name and bio changes now sent to all connected peers immediately, not just audience members.</li>
|
|
<li><strong>Auto-sync on follow</strong> — Following someone immediately pulls their posts into your feed.</li>
|
|
<li><strong>Popover UI</strong> — Notifications, diagnostics, and message threads open as overlay windows instead of inline sections.</li>
|
|
<li><strong>Notification settings</strong> — Configure message, post, and nearby-user notifications from Settings.</li>
|
|
<li><strong>Smart DM polling</strong> — Message refresh rate scales with conversation recency (5s–daily).</li>
|
|
<li><strong>Reaction display</strong> — Posts show top 5 emoji reactions + total response count.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.3.0 — March 12, 2026</div>
|
|
<ul>
|
|
<li><strong>Full rename distsoc → ItsGoin</strong> — ALPN, crypto contexts, data paths, Android package ID all changed. Clean break — incompatible with prior versions.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.11 — March 12, 2026</div>
|
|
<ul>
|
|
<li><strong>Engagement system</strong> — Reactions (public + private encrypted), inline comments with ed25519 signatures, and author-controlled comment/react policies. Full UI with emoji picker, reaction pills, and expandable comment threads.</li>
|
|
<li><strong>CDN tree for all posts</strong> — New <code>post_downstream</code> table gives every post (including text-only) a propagation tree. Engagement diffs flow through the file layer via BlobHeaderDiff (0xD0), never mesh.</li>
|
|
<li><strong>4 new wire messages</strong> — BlobHeaderDiff (0xD0), BlobHeaderRequest/Response (0xD1/0xD2), PostDownstreamRegister (0xD3). Policy enforcement in handlers (blocklist, audience-only, permission checks).</li>
|
|
<li><strong>Thread splitting</strong> — Headers exceeding 16KB automatically split oldest comments into linked thread posts, keeping engagement propagation lightweight.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.10 — March 12, 2026</div>
|
|
<ul>
|
|
<li><strong>Per-family NAT classification</strong> — IPv4 and IPv6 public reachability detected independently. Fixes false "public (v4+v6)" when only IPv6 is public, which was silently breaking IPv4 hole punches.</li>
|
|
<li><strong>STUN always runs</strong> — IPv6-only anchors now correctly probe their IPv4 NAT type instead of assuming "Public". Only <code>--bind</code> (explicit server) skips STUN.</li>
|
|
<li><strong>Anchor address fallback</strong> — Anchors without <code>--bind</code> or UPnP now advertise their public IPv6 address, so peers save them in known_anchors for preferential reconnection.</li>
|
|
<li><strong>Bootstrap deprioritization</strong> — Discovered anchors are tried before hardcoded bootstrap anchors at startup, reducing bootstrap server load as the network grows.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.9 — March 12, 2026</div>
|
|
<ul>
|
|
<li><strong>ConnectionManager actor redesign</strong> — Replaced global mutex with actor pattern (ConnHandle + ConnectionActor). Network operations no longer block each other — 14 I/O code paths that previously held the lock for up to 15 seconds now run concurrently.</li>
|
|
<li><strong>60+ call sites migrated</strong> — All network and node code uses the new lock-free ConnHandle API. Public mutex accessor removed.</li>
|
|
<li><strong>I/O extraction</strong> — Broadcast, push, pull, relay, anchor register, and address resolution all execute outside state locks.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.8 — March 11, 2026</div>
|
|
<ul>
|
|
<li><strong>NAT filter probe</strong> — Anchor probes your NAT filtering type (address-restricted vs port-restricted) by attempting to reach you from a different source port. Eliminates unnecessary port scanning for the majority of connections.</li>
|
|
<li><strong>Role-based NAT traversal</strong> — Each side now takes the correct role based on its NAT profile: EIM nodes punch every 2s (stable port), EDM nodes walk outward at 100/sec (opening firewall entries). Previous burst-scan design replaced with steady ~100 ports/sec outward walk.</li>
|
|
<li><strong>IPv4 vs IPv6 public</strong> — Public reachability now distinguished by protocol family (v4 only, v6 only, v4+v6). Prevents false assumptions when only one family is public.</li>
|
|
<li><strong>Scanning cleanup</strong> — Scan tasks properly cancelled via JoinSet between attempts. Previous design spawned 37K+ fire-and-forget tasks.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.7 — March 11, 2026</div>
|
|
<ul>
|
|
<li><strong>Focused port scanning</strong> — Scanning now targets only the anchor-observed IP address instead of all self-reported addresses, reducing wasted scan budget on unreachable VPN/cellular IPs.</li>
|
|
<li><strong>Scan on unknown NAT</strong> — Port scanning now triggers when peer NAT type is unknown (e.g. peer running older version), not just when explicitly EDM.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.6 — March 11, 2026</div>
|
|
<ul>
|
|
<li><strong>Anchor self-verification</strong> — Nodes with public addresses now verify their reachability via cold-connect probes from N2 strangers. Two consecutive failures revoke anchor status.</li>
|
|
<li><strong>Advanced NAT traversal</strong> — Hard+hard NAT pairs are no longer skipped. Port scanning (tiered: ±500, ±2000, full ephemeral range) attempts direct connection before falling back to relay.</li>
|
|
<li><strong>NAT profile sharing</strong> — Peers exchange mapping (EIM/EDM) and filtering (open/port-restricted) classification during connection, enabling smarter hole punch decisions.</li>
|
|
<li><strong>Behavioral NAT inference</strong> — Filtering type is refined from actual connection outcomes — no unreliable upfront probing needed.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">v0.2.3 — March 11, 2026</div>
|
|
<ul>
|
|
<li><strong>NAT type detection</strong> — STUN probing on startup classifies your NAT as Public, Easy, or Hard. Shared with peers during connection.</li>
|
|
<li><strong>Skip futile hole punches</strong> — When both peers are behind hard/symmetric NATs, skip the 30-second hole punch attempt entirely.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">March 10, 2026 (v2)</div>
|
|
<ul>
|
|
<li><strong>Anchor advertised address</strong> — Anchors advertise their stable bind address in initial exchange, so peers always store the correct reconnection address.</li>
|
|
<li><strong>Observed address notification</strong> — Peers tell each other "I see you at <ip:port>" during connection — lightweight STUN-like address feedback.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">March 10, 2026</div>
|
|
<ul>
|
|
<li><strong>UPnP port mapping</strong> — Devices behind NAT routers automatically request a port forward via UPnP, becoming directly reachable without manual configuration.</li>
|
|
<li><strong>Auto-anchor promotion</strong> — Devices with a successful UPnP mapping self-declare as anchors, improving bootstrap diversity for all peers.</li>
|
|
<li><strong>Hole punch fix</strong> — Target-side hole punch connections were silently discarded; now properly registered as sessions so both sides of a NAT punch succeed.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">February 24, 2026 (v2)</div>
|
|
<ul>
|
|
<li><strong>Request Referrals button</strong> — On-demand peer referral requesting in Network Diagnostics.</li>
|
|
<li><strong>Docker bridge IP filtering</strong> — Peer introductions no longer leak Docker bridge IPs.</li>
|
|
<li><strong>Keepalive fix</strong> — Sender-side last_activity update prevents false zombie detection.</li>
|
|
<li><strong>Message threads</strong> — DM conversations grouped by partner with expandable thread view.</li>
|
|
<li><strong>Mesh/reach diagnostics</strong> — Peer cards show reach level badges (Mesh/N1/N2/N3).</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">February 24, 2026</div>
|
|
<ul>
|
|
<li><strong>Audience request button</strong> — "Ask to join audience" on followed peers.</li>
|
|
<li><strong>DMs filtered from feed</strong> — Direct messages show only in Messages tab.</li>
|
|
<li><strong>Peer bios displayed</strong> — Bio text shown below peer names in People tab.</li>
|
|
<li><strong>People tab auto-refresh</strong> — Follows, peers, audience refresh every 10 seconds.</li>
|
|
<li><strong>Button feedback</strong> — Loading state and toast confirmation on diagnostics refresh.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">February 23, 2026</div>
|
|
<ul>
|
|
<li><strong>Fix connection lock contention</strong> — QUIC connect no longer blocks all tasks.</li>
|
|
<li><strong>Image attachments display</strong> — Fixed CSP blocking blob: URLs.</li>
|
|
<li><strong>Non-blocking startup</strong> — Referral connections run in background.</li>
|
|
<li><strong>Connect timeout</strong> — 15-second cap on connection attempts.</li>
|
|
<li><strong>Android foreground service</strong> — Mesh stays alive in background.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">February 20, 2026</div>
|
|
<ul>
|
|
<li><strong>IPv4-mapped address fix</strong> — Normalized dual-stack addresses for NAT traversal.</li>
|
|
<li><strong>Mesh keepalive</strong> — 30-second pings prevent zombie detection on idle connections.</li>
|
|
<li><strong>Audience management</strong> — Approve/Deny/Remove audience members.</li>
|
|
<li><strong>Network diagnostics overhaul</strong> — Summary grid, peer cards, connection breakdown.</li>
|
|
<li><strong>Manual rebalance</strong> — Trigger immediate mesh rebalancing from Settings.</li>
|
|
<li><strong>Reset all data</strong> — Clear local data while preserving identity key.</li>
|
|
</ul>
|
|
|
|
<div class="changelog-date">February 19, 2026</div>
|
|
<ul>
|
|
<li><strong>Reactive mesh growth loop</strong> — New peers connect within seconds.</li>
|
|
<li><strong>Anchor matchmaking only</strong> — Anchors introduce peers, never proxy bytes.</li>
|
|
<li><strong>Parallel hole punching</strong> — NAT traversal tries all addresses simultaneously.</li>
|
|
<li><strong>Relay-observed address injection</strong> — Fixes NAT-to-NAT hole punching.</li>
|
|
<li><strong>Growth loop introduction fallback</strong> — Bilateral hole punching when direct fails.</li>
|
|
</ul>
|
|
</div>
|
|
</section>
|
|
|
|
<section>
|
|
<h2>Help build ItsGoin</h2>
|
|
<p>This project is open source and could use your help. Whether you're a developer, tester, or just have ideas — jump in.</p>
|
|
<p style="margin-top: 0.75rem;">
|
|
<a href="https://discord.gg/pCjMbY9PmN" class="btn btn-primary" style="margin-right: 0.5rem;">Join the Discord</a>
|
|
<a href="https://git.itsgoin.net/Sologretto/itsgoin" class="btn btn-secondary">Source code</a>
|
|
</p>
|
|
</section>
|
|
</div>
|
|
|
|
<footer>
|
|
<p>ItsGoin — Apache 2.0 License — <a href="https://itsgoin.com">itsgoin.com</a> · <a href="https://discord.gg/pCjMbY9PmN">Discord</a> · <a href="https://git.itsgoin.net/Sologretto/itsgoin">Source Code</a></p>
|
|
</footer>
|
|
</body>
|
|
</html>
|