<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Zaryn docs</title>
  <id>https://zaryn.xyz/docs/feed.xml</id>
  <link rel="self" href="https://zaryn.xyz/docs/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en"/>
  <updated>2026-10-30T00:00:00Z</updated>
  <author><name>Zaryn</name><uri>https://zaryn.xyz/</uri></author>
  <entry>
    <title>zev and Git</title>
    <id>https://zaryn.xyz/docs/en/zev-vs-git</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/zev-vs-git"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>What zev does that Git doesn't, what stays the same, and every everyday Git command next to its zev form.</summary>
  </entry>
  <entry>
    <title>VPN for the whole computer (zev vpn)</title>
    <id>https://zaryn.xyz/docs/en/vpn</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/vpn"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>sudo zev vpn on sends every program through your own proxy server, with its DNS and IPv6, a kill switch, sites that need no proxy kept direct, and a leak test (zev vpn check) that proves nothing gets around it.</summary>
  </entry>
  <entry>
    <title>A better internet line (zev tune)</title>
    <id>https://zaryn.xyz/docs/en/tune</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/tune"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>zev tune measures your internet line in full (latency, jitter and loss to the router and beyond, speed both ways, bufferbloat, DNS, path MTU, IPv6, Wi-Fi), then fixes what holds it back one change at a time, keeps only what measurably helped, and never leaves you without a connection.</summary>
  </entry>
  <entry>
    <title>Your own proxy (zev proxy)</title>
    <id>https://zaryn.xyz/docs/en/proxy</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/proxy"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>When sites are blocked, use your own VLESS, VMess, Trojan, Shadowsocks, Hysteria2 or WireGuard servers for zev, every app or the whole computer; zev learns per network which sites need it, says why each goes the way it does, counts the data and shows a server as a QR code.</summary>
  </entry>
  <entry>
    <title>The internet in pictures</title>
    <id>https://zaryn.xyz/docs/en/internet-in-pictures</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/internet-in-pictures"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>How a web page reaches you, and what DNS, a proxy, a VPN, a full line (bufferbloat) and a second connection are, explained with pictures, each with the one zev command for it. No networking knowledge needed.</summary>
  </entry>
  <entry>
    <title>How do I…?</title>
    <id>https://zaryn.xyz/docs/en/how-do-i</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/how-do-i"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>Short answers to the things people most often need to do. Find yours in the list on the right, or press / to search.</summary>
  </entry>
  <entry>
    <title>Moving from Git</title>
    <id>https://zaryn.xyz/docs/en/from-git</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/from-git"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>Move a Git repository to zev in three commands. Preview what comes over, import it in place or straight from its address, and get proof that every commit and file matches Git. Real examples for an open source project, a company repository with LFS, submodules and hooks, and a team that switches gradually.</summary>
  </entry>
  <entry>
    <title>When the internet doesn't work (zev doctor)</title>
    <id>https://zaryn.xyz/docs/en/doctor</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/doctor"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>zev doctor checks this computer's internet layer by layer, from the Wi-Fi to HTTPS, names the one thing that's actually wrong, and fixes it. Each fix is checked afterwards, a fix that didn't help is put back, and undo puts back the rest.</summary>
  </entry>
  <entry>
    <title>DNS that works on any network (zev dns)</title>
    <id>https://zaryn.xyz/docs/en/dns</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/dns"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>zev dns finds which DNS resolvers really work from your network and how (encrypted, another port, TCP, through your proxy), throws away a censor's answers, checks DNSSEC signatures itself, and falls back to the network's own DNS so names never stop.</summary>
  </entry>
  <entry>
    <title>All commands</title>
    <id>https://zaryn.xyz/docs/en/commands</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/commands"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>Every zev command, with the ones you'll use every day first. Each entry says what it does, how to type it, and shows examples.</summary>
  </entry>
  <entry>
    <title>Why zev, when Git exists</title>
    <id>https://zaryn.xyz/docs/en/why-zev</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/why-zev"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Git solved sharing source code in 2005. zev is built for how software is made now, with large files, AI agents writing code, small reviews and supply-chain attacks, so you can't lose work, conflicts don't stop you, and trust is built in.</summary>
  </entry>
  <entry>
    <title>Undo anything</title>
    <id>https://zaryn.xyz/docs/en/undo</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/undo"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>zev undo takes back the last thing you did, whether a commit, merge, rebase, deleted branch or add, without ever overwriting work that isn't saved anywhere. zev recover brings back edits a command threw away. zev op log shows every change.</summary>
  </entry>
  <entry>
    <title>Subrepositories</title>
    <id>https://zaryn.xyz/docs/en/subrepos</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/subrepos"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Another repository inside yours, pinned to a commit: a shared UI kit, a vendored library, a dataset. zev fetches and updates it on clone, checkout and pull by itself, keeps the pin in a file you review, and never throws away work done inside it. What Git's submodules should have been.</summary>
  </entry>
  <entry>
    <title>Stacked changes</title>
    <id>https://zaryn.xyz/docs/en/stacked-changes</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/stacked-changes"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Split big work into a chain of small branches, each on the one below. zev stack restacks them together after an edit, pushes them as one pull request each, and cleans up as they merge.</summary>
  </entry>
  <entry>
    <title>Signed commits</title>
    <id>https://zaryn.xyz/docs/en/signed-commits</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/signed-commits"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>zev signs every new commit on your computer with the repository's Ed25519 key. Add the key to your account once and Zaryn shows those commits as Verified, with your name.</summary>
  </entry>
  <entry>
    <title>Get started with code hosting</title>
    <id>https://zaryn.xyz/docs/en/get-started-code</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/get-started-code"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>A guided path from your first repository to signed, provable history: what code hosting is, how zev and Zaryn work, the everyday loop, branches and pull requests, finding and undoing things, and the advanced features. Pictures first, every step explained.</summary>
  </entry>
  <entry>
    <title>Merge conflicts</title>
    <id>https://zaryn.xyz/docs/en/conflicts</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/conflicts"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>When two branches changed the same lines. zev shows each conflict with your side, the base and theirs, settles them with one command instead of an editor, and lets you commit them now and resolve later. Every step is data for scripts and AI agents.</summary>
  </entry>
  <entry>
    <title>Branches and merging</title>
    <id>https://zaryn.xyz/docs/en/branches</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/branches"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Work on new ideas without touching your main code, then bring them back in. Includes fixing merge conflicts, step by step.</summary>
  </entry>
  <entry>
    <title>Scripting and AI Agents</title>
    <id>https://zaryn.xyz/docs/en/automation-and-agents</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/automation-and-agents"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Use zev from scripts, CI, servers and AI agents: tokens, JSON output and the MCP server.</summary>
  </entry>
  <entry>
    <title>Verified storage</title>
    <id>https://zaryn.xyz/docs/en/verified-storage</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/verified-storage"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Check with cryptographic proofs, instead of taking anyone's word for it, that Zaryn really stores everything you pushed.</summary>
  </entry>
  <entry>
    <title>S3-compatible storage</title>
    <id>https://zaryn.xyz/docs/en/s3-storage</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/s3-storage"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Use Zaryn as S3 storage with aws-cli, rclone, restic and any S3 SDK. Make a key, point the tool at the endpoint, and every object is checked on every read and counted once on your storage plan.</summary>
  </entry>
  <entry>
    <title>Ransomware protection: locked backups and a trash</title>
    <id>https://zaryn.xyz/docs/en/ransomware-protection</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/ransomware-protection"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Keep backups that ransomware can't delete, overwrite or encrypt, even with your own keys. Object lock (S3's API), a trash that puts a bucket back as it was, and delays on anything that lowers protection.</summary>
  </entry>
  <entry>
    <title>Connect your tools in 60 seconds</title>
    <id>https://zaryn.xyz/docs/en/connect-storage</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/connect-storage"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Step-by-step setup of Zaryn storage in rclone, restic, Kopia, Veeam, Synology Hyper Backup and Cloud Sync, aws-cli and any S3 tool. Three settings, copy, paste, done.</summary>
  </entry>
  <entry>
    <title>Backup: encrypted snapshots with zev backup</title>
    <id>https://zaryn.xyz/docs/en/backups</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/backups"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Encrypted, deduplicated backups of folders, servers and Postgres databases with one command. To your Zaryn storage, any S3-compatible bucket, or a disk. Only changes are sent, every restore is checked, and a schedule runs it for you.</summary>
  </entry>
  <entry>
    <title>Datasets and models: versions you can prove</title>
    <id>https://zaryn.xyz/docs/en/ai-datasets</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/ai-datasets"/>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary>Freeze a folder of a bucket as a dataset or model version. Exact files by their hashes under one root, kept when the bucket changes, linked to what they were trained on, downloaded in checked pieces that resume where they stopped.</summary>
  </entry>
  <entry>
    <title>What Zaryn can do</title>
    <id>https://zaryn.xyz/docs/en/what-zaryn-can-do</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/what-zaryn-can-do"/>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>Every Zaryn product in plain words, who it's for, where it is on the site, what's free, and where its guides start. Pick yours and read only that.</summary>
  </entry>
  <entry>
    <title>Storing and sharing files</title>
    <id>https://zaryn.xyz/docs/en/storing-files</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/storing-files"/>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>Put a file on Zaryn and get a link anyone can open. How much space you have, what &quot;public&quot; means here, and how to remove a file.</summary>
  </entry>
  <entry>
    <title>Get started with files, storage and encryption</title>
    <id>https://zaryn.xyz/docs/en/get-started-storage</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/get-started-storage"/>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>A guided path from &quot;where do I put this file?&quot; to proofs that your data is kept: links that keep working because they name the content, sharing and updating, end-to-end encrypted repositories, and checking Zaryn without trusting it. Pictures first, every step explained.</summary>
  </entry>
  <entry>
    <title>Mirrors for pypi.org, npm, Go, crates.io, Rust, Zig and their compilers</title>
    <id>https://zaryn.xyz/docs/en/package-mirrors</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/package-mirrors"/>
    <updated>2026-10-26T00:00:00Z</updated>
    <summary>Make pip, uv, npm, go, cargo, rustup and zig download through Zaryn when pypi.org, npmjs.com, proxy.golang.org, crates.io, GitHub or ziglang.org are slow or unreachable. Every file is checked against a hash your tools already know, so the mirror can't change anything.</summary>
  </entry>
  <entry>
    <title>Network design repository</title>
    <id>https://zaryn.xyz/docs/en/network-design</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/network-design"/>
    <updated>2026-10-26T00:00:00Z</updated>
    <summary>The network design as text in a repository, reviewed like code, compared with what the devices really say, and tested: intents the design must keep, what-if failures, and a merge gate.</summary>
  </entry>
  <entry>
    <title>Made on Zaryn: four packages to try</title>
    <id>https://zaryn.xyz/docs/en/made-on-zaryn</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/made-on-zaryn"/>
    <updated>2026-10-26T00:00:00Z</updated>
    <summary>tinyhash (Python), @arvand/envguard (npm), portcheck (Rust) and humanize (Zig) are real tools published on Zaryn's registries, each installed with one command; how each was built, tested and published, to copy for your own.</summary>
  </entry>
  <entry>
    <title>Installation</title>
    <id>https://zaryn.xyz/docs/en/installation</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/installation"/>
    <updated>2026-10-26T00:00:00Z</updated>
    <summary>Install zev on Linux, macOS or Windows with one command, or from your package manager. Then keep it updated.</summary>
  </entry>
  <entry>
    <title>Version control in pictures</title>
    <id>https://zaryn.xyz/docs/en/version-control-in-pictures</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/version-control-in-pictures"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>What version control is, and what a repository, commit, diff, branch, merge, conflict, push, pull and pull request are, explained with pictures you can play step by step. No experience needed.</summary>
  </entry>
  <entry>
    <title>When something goes wrong</title>
    <id>https://zaryn.xyz/docs/en/troubleshooting</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/troubleshooting"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>zev's messages, what they mean, and what to do. Search for the words of the message you got.</summary>
  </entry>
  <entry>
    <title>Semantic (AST) diffing</title>
    <id>https://zaryn.xyz/docs/en/semantic-diff</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/semantic-diff"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>zev sdiff compares Zig code by function (added, removed, signature or body changed) from the compiler's own parser, not lines of text.</summary>
  </entry>
  <entry>
    <title>Quick start</title>
    <id>https://zaryn.xyz/docs/en/quickstart</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/quickstart"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>From nothing to your first project on Zaryn in about five minutes. Every command is explained as you go.</summary>
  </entry>
  <entry>
    <title>Share your work on Zaryn</title>
    <id>https://zaryn.xyz/docs/en/pushing-and-pulling</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/pushing-and-pulling"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>Sign in, put a project on Zaryn, clone someone else's, and keep everyone in sync with push and pull.</summary>
  </entry>
  <entry>
    <title>Publish your first Python package in 5 minutes</title>
    <id>https://zaryn.xyz/docs/en/publish-python-package</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/publish-python-package"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>A real Python package from an empty folder to pip install, step by step, using tinyhash (published on Zaryn) as the example. Project layout, a name that's free, building, a publish token, uploading, installing, putting the code on Zaryn, and the next version.</summary>
  </entry>
  <entry>
    <title>Private networks</title>
    <id>https://zaryn.xyz/docs/en/private-networks</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/private-networks"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>Connect your laptops, servers, CI runners and apps into one private network, so they reach each other directly and securely, wherever they are.</summary>
  </entry>
  <entry>
    <title>Pinning and IPFS Cluster</title>
    <id>https://zaryn.xyz/docs/en/pinning-and-cluster</id>
    <link rel="alternate" type="text/html" href="https://zaryn.xyz/docs/en/pinning-and-cluster"/>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary>How zev keeps content available: pinning to IPFS (standard CIDs) and replicating across nodes with IPFS Cluster.</summary>
  </entry>
</feed>
