<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quic on Thiago Avelino</title><link>https://avelino.run/tags/quic/</link><description>Recent content in Quic on Thiago Avelino</description><generator>Hugo</generator><language>en-us</language><copyright>© Avelino</copyright><lastBuildDate>Thu, 25 Jun 2026 15:35:33 -0300</lastBuildDate><atom:link href="https://avelino.run/tags/quic/index.xml" rel="self" type="application/rss+xml"/><item><title>The op log was peer-to-peer the whole time</title><link>https://avelino.run/from-icloud-to-peers/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://avelino.run/from-icloud-to-peers/</guid><description>&lt;p&gt;A month ago I wrote about &lt;a href="https://avelino.run/from-paper-to-outliner"&gt;building outl on the Kleppmann move-op paper&lt;/a&gt;. That post ended with a working sync: a terminal client on macOS and an iOS app, converging over iCloud Drive, no server, no merge dialogs.&lt;/p&gt;
&lt;p&gt;iCloud was a deliberate shortcut, and I want to be honest about that before I bury it. I had one question to answer first: does this CRDT actually converge across real devices, two separate machines, not two processes on my laptop pretending to be peers? iCloud Drive answered it without me writing a line of networking. Drop the per-actor &lt;code&gt;ops-*.jsonl&lt;/code&gt; files in the ubiquitous container, let Apple's daemon push them between devices, watch two replicas merge. A file-pusher I borrowed to validate the algorithm, and for that job it was exactly right.&lt;/p&gt;</description></item></channel></rss>