<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Yjs on My Battles With Technology</title>
    <link>https://blog.shellnetsecurity.com/tags/yjs/</link>
    <description>Recent content in Yjs on My Battles With Technology</description>
    <generator>Hugo -- 0.151.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 09:00:00 -0500</lastBuildDate>
    <atom:link href="https://blog.shellnetsecurity.com/tags/yjs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Same Bytes, Different Language: Testing ygo&#39;s Claim of Byte-for-Byte Yjs Compatibility</title>
      <link>https://blog.shellnetsecurity.com/posts/2026/ygo-yjs-wire-compatibility-go/</link>
      <pubDate>Fri, 16 Oct 2026 09:00:00 -0500</pubDate>
      <guid>https://blog.shellnetsecurity.com/posts/2026/ygo-yjs-wire-compatibility-go/</guid>
      <description>ygo says a Go program and a JavaScript Yjs client produce identical bytes for the same edits. I checked, found where that holds and where my own test setup broke it, and probed what the decoder does with hostile input.</description>
    </item>
  </channel>
</rss>
