<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clydara</title>
    <description>Clydara is a web and software studio. We design and build custom websites, SaaS platforms, business dashboards, workflow tools and AI integrations for startups and growing businesses around the world, with UI/UX and brand design in-house.</description>
    <link>https://speakerdeck.com/clydara</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/clydara.rss"/>
    <lastBuildDate>2026-10-15 10:54:01 -0400</lastBuildDate>
    <item>
      <title>Release asset swaps: lessons from the OVHcloud CLI incident</title>
      <description>Six slides on the October 19, 2026 OVHcloud CLI release swap: what happened, which install paths were exposed, why a checksums.txt in the same release did not help, and what users and maintainers can do (pinned hashes, gh release verify-asset, immutable releases, private vulnerability reporting). Sources: https://github.com/ovh/ovhcloud-cli/issues/300, https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases, https://thehackernews.com/2026/10/hackers-hijack-five-ovhcloud-cli.html. Longer write-up: https://dev.to/clydaralab/the-ovhcloud-cli-release-swap-why-the-checksum-file-didnt-help-5h27. Written with AI assistance.</description>
      <media:content url="https://files.speakerdeck.com/presentations/d68702baba6c4712a930654b8e3d0ee7/preview_slide_0.jpg?40987658" type="image/jpeg" medium="image"/>
      <content:encoded>Six slides on the October 19, 2026 OVHcloud CLI release swap: what happened, which install paths were exposed, why a checksums.txt in the same release did not help, and what users and maintainers can do (pinned hashes, gh release verify-asset, immutable releases, private vulnerability reporting). Sources: https://github.com/ovh/ovhcloud-cli/issues/300, https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases, https://thehackernews.com/2026/10/hackers-hijack-five-ovhcloud-cli.html. Longer write-up: https://dev.to/clydaralab/the-ovhcloud-cli-release-swap-why-the-checksum-file-didnt-help-5h27. Written with AI assistance.</content:encoded>
      <pubDate>Tue, 20 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/release-asset-swaps-lessons-from-the-ovhcloud-cli-incident</link>
      <guid>https://speakerdeck.com/clydara/release-asset-swaps-lessons-from-the-ovhcloud-cli-incident</guid>
    </item>
    <item>
      <title>Key custody check after the OpenCode Console incident</title>
      <description>A 6-slide summary of what OpenCode disclosed on Oct 17, 2026, what is still unknown, and a short checklist for any API key you hand to a gateway. Sources: The Hacker News https://thehackernews.com/2026/10/opencode-console-breach-may-have.html and OpenCode's notice https://x.com/opencode/status/2111519637049319818 .</description>
      <media:content url="https://files.speakerdeck.com/presentations/09f8f771d7af4622a112aec9f2c017ef/preview_slide_0.jpg?40974838" type="image/jpeg" medium="image"/>
      <content:encoded>A 6-slide summary of what OpenCode disclosed on Oct 17, 2026, what is still unknown, and a short checklist for any API key you hand to a gateway. Sources: The Hacker News https://thehackernews.com/2026/10/opencode-console-breach-may-have.html and OpenCode's notice https://x.com/opencode/status/2111519637049319818 .</content:encoded>
      <pubDate>Mon, 19 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/key-custody-check-after-the-opencode-console-incident</link>
      <guid>https://speakerdeck.com/clydara/key-custody-check-after-the-opencode-console-incident</guid>
    </item>
    <item>
      <title>Reflection's Beam: 23B active, 501B in memory</title>
      <description>Four slides on Reflection's Beam open-weight release (Oct 16, 2026, Apache 2.0): what shipped, the weight-memory estimate per precision, the official quantized benchmarks, and a self-hosting checklist. Sources: https://reflection.ai/blog/beam-is-available and https://huggingface.co/reflection/Beam-1.0-501B-A23B</description>
      <media:content url="https://files.speakerdeck.com/presentations/a1254ddea11e4e99917479cc1cfa39cc/preview_slide_0.jpg?40964553" type="image/jpeg" medium="image"/>
      <content:encoded>Four slides on Reflection's Beam open-weight release (Oct 16, 2026, Apache 2.0): what shipped, the weight-memory estimate per precision, the official quantized benchmarks, and a self-hosting checklist. Sources: https://reflection.ai/blog/beam-is-available and https://huggingface.co/reflection/Beam-1.0-501B-A23B</content:encoded>
      <pubDate>Sun, 18 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/reflections-beam-23b-active-501b-in-memory</link>
      <guid>https://speakerdeck.com/clydara/reflections-beam-23b-active-501b-in-memory</guid>
    </item>
    <item>
      <title>Perplexity open-sourced SPACE: the VM held, the network rules did not</title>
      <description>Six slides on SPACE, the open-source (Apache 2.0) sandbox platform behind Perplexity Computer, released October 15, 2026: what it is, Perplexity's own performance claims, its red-team results (0 of 108 VM escapes, 11 of 54 network bypasses with partial network access, both fixed), what coverage skipped (8 of 10 other sandbox platforms had bypasses; KVM host requirements; partial E2B compatibility), and facts vs our read. Sources: https://www.perplexity.ai/hub/blog/open-sourcing-space , https://www.perplexity.ai/hub/blog/escaping-space-part-i , https://github.com/perplexityai/SPACE</description>
      <media:content url="https://files.speakerdeck.com/presentations/e39f632032a849a7b6ae4d48a0c04f42/preview_slide_0.jpg?40954826" type="image/jpeg" medium="image"/>
      <content:encoded>Six slides on SPACE, the open-source (Apache 2.0) sandbox platform behind Perplexity Computer, released October 15, 2026: what it is, Perplexity's own performance claims, its red-team results (0 of 108 VM escapes, 11 of 54 network bypasses with partial network access, both fixed), what coverage skipped (8 of 10 other sandbox platforms had bypasses; KVM host requirements; partial E2B compatibility), and facts vs our read. Sources: https://www.perplexity.ai/hub/blog/open-sourcing-space , https://www.perplexity.ai/hub/blog/escaping-space-part-i , https://github.com/perplexityai/SPACE</content:encoded>
      <pubDate>Sat, 17 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/perplexity-open-sourced-space-the-vm-held-the-network-rules-did-not</link>
      <guid>https://speakerdeck.com/clydara/perplexity-open-sourced-space-the-vm-held-the-network-rules-did-not</guid>
    </item>
    <item>
      <title>Muse Spark Open: what Meta's open-weight license actually lets you do</title>
      <description>Meta released Muse Spark Open's weights on Oct 15, 2026 (816B total, 42B active, 1M context). Five slides on what shipped, the three license clauses (credit line, derivatives that reach outputs, the $20M API clause), and what to check before you build. Sources: https://research.meta.ai/blog/muse-spark-open and https://huggingface.co/meta-models/Muse-Spark-Open-816B-A42B/blob/main/LICENSE.md</description>
      <media:content url="https://files.speakerdeck.com/presentations/105dcf4acae34fa98bb716ef64cec4e7/preview_slide_0.jpg?40944740" type="image/jpeg" medium="image"/>
      <content:encoded>Meta released Muse Spark Open's weights on Oct 15, 2026 (816B total, 42B active, 1M context). Five slides on what shipped, the three license clauses (credit line, derivatives that reach outputs, the $20M API clause), and what to check before you build. Sources: https://research.meta.ai/blog/muse-spark-open and https://huggingface.co/meta-models/Muse-Spark-Open-816B-A42B/blob/main/LICENSE.md</content:encoded>
      <pubDate>Fri, 16 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/muse-spark-open-what-metas-open-weight-license-actually-lets-you-do</link>
      <guid>https://speakerdeck.com/clydara/muse-spark-open-what-metas-open-weight-license-actually-lets-you-do</guid>
    </item>
    <item>
      <title>NVIDIA open-sourced Run:ai: what changed for Kubernetes GPU teams</title>
      <description>A five-slide summary of NVIDIA's October 13, 2026 Run:ai open-source release: the four components, what most coverage misses (CUDA 13.4 fractions, no enterprise support on the free build), and where to start. Source: https://developer.nvidia.com/blog/nvidia-runai-is-now-open-source-as-part-of-nvidia-dsx-ai-factory-platform/</description>
      <media:content url="https://files.speakerdeck.com/presentations/47c534ebffe74af990e3e5838446cbdc/preview_slide_0.jpg?40926160" type="image/jpeg" medium="image"/>
      <content:encoded>A five-slide summary of NVIDIA's October 13, 2026 Run:ai open-source release: the four components, what most coverage misses (CUDA 13.4 fractions, no enterprise support on the free build), and where to start. Source: https://developer.nvidia.com/blog/nvidia-runai-is-now-open-source-as-part-of-nvidia-dsx-ai-factory-platform/</content:encoded>
      <pubDate>Thu, 15 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/clydara/nvidia-open-sourced-run-ai-what-changed-for-kubernetes-gpu-teams</link>
      <guid>https://speakerdeck.com/clydara/nvidia-open-sourced-run-ai-what-changed-for-kubernetes-gpu-teams</guid>
    </item>
  </channel>
</rss>
