<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Chaos Computer Club - BOB Konferenz 2026 (high quality mp4)</title>
    <link>https://media.ccc.de/c/bobkonf2026</link>
    <description> This feed contains all events from bobkonf2026 as mp4</description>
    <copyright>see video outro</copyright>
    <lastBuildDate>Tue, 19 May 2026 16:38:45 -0000</lastBuildDate>
    <image>
      <url>https://static.media.ccc.de/media/events/bobkonf/2026/logo.png</url>
      <title>Chaos Computer Club - BOB Konferenz 2026 (high quality mp4)</title>
      <link>https://media.ccc.de/c/bobkonf2026</link>
    </image>
    <item>
      <title>Keynote: „Digital Sovereignty“ – Searching for Meaning in a Magical Concept (bobkonf2026)</title>
      <link>https://media.ccc.de/v/bob11-2026-digital-sovereignity-kaufmann</link>
      <description>We&#39;ve been using the term &quot;digital sovereignty&quot; going on ten years
          now.  But what does that &quot;digital sovereignty&quot; even mean? Looking at
          research connected to the term shows that it has been used as an
          argument for very different, sometimes diametrically opposed goals and
          ideas.  Does it even make sense to use it anymore?

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/stk.html
</description>
      <enclosure url="https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-1-eng-Keynote_Digital_Sovereignty_-_Searching_for_Meaning_in_a_Magical_Concept_hd.mp4"
        length="373293056"
        type="video/mp4"/>
      <pubDate>Fri, 13 Mar 2026 09:00:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-1-eng-Keynote_Digital_Sovereignty_-_Searching_for_Meaning_in_a_Magical_Concept_hd.mp4?1779207680</guid>
      <dc:identifier>8f370b8c-6e08-4fc3-a8ea-6e16741f1ab6</dc:identifier>
      <dc:date>2026-03-13T09:00:00+01:00</dc:date>
      <itunes:author>Stefan Kaufmann</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>1, 2026, bob2026, Talk, Talks #1, bob2026-eng, BOB, BOB Konferenz, Day 1</itunes:keywords>
      <itunes:summary>We&#39;ve been using the term &quot;digital sovereignty&quot; going on ten years
          now.  But what does that &quot;digital sovereignty&quot; even mean? Looking at
          research connected to the term shows that it has been used as an
          argument for very different, sometimes diametrically opposed goals and
          ideas.  Does it even make sense to use it anymore?

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/stk.html
</itunes:summary>
      <itunes:duration>00:49:54</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/bobkonf/2026/1-8f370b8c-6e08-4fc3-a8ea-6e16741f1ab6.jpg"/>
    </item>
    <item>
      <title>Accessibility by Design: Practical A11y for Everyday Software Engineering (bobkonf2026)</title>
      <link>https://media.ccc.de/v/bob11-2026-accessibility-design-engelbrecht</link>
      <description>Accessibility is often treated as a mere compliance checkbox or something the “UI people” worry about at the end of a project. In reality, accessibility is a core quality attribute of software systems, and many of the biggest wins come from small decisions developers make every day: how we structure HTML, name components, log errors, design APIs, or write tests.
          In this talk, we look at accessibility from a software engineering perspective. I will introduce the most common types of disabilities and assistive technologies, then show how they map to concrete engineering practices across the stack: semantics (and ARIA) in the frontend, accessible design systems, error message design, and test automation for accessibility. Attendees will leave with a practical checklist they can use in coding and code reviews. 
          The goal is not to make everyone an accessibility expert, but to make accessibility a natural part of our everyday engineering work.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/engelbrecht.html
</description>
      <enclosure url="https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-9-eng-Accessibility_by_Design_Practical_A11y_for_Everyday_Software_Engineering_hd.mp4"
        length="156237824"
        type="video/mp4"/>
      <pubDate>Fri, 13 Mar 2026 10:15:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-9-eng-Accessibility_by_Design_Practical_A11y_for_Everyday_Software_Engineering_hd.mp4?1779208380</guid>
      <dc:identifier>2224d8eb-5642-4c18-9880-7eac3c185428</dc:identifier>
      <dc:date>2026-03-13T10:15:00+01:00</dc:date>
      <itunes:author>Ariadne Engelbrecht</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>9, 2026, bob2026, Talk, Talks #2, bob2026-eng, BOB, BOB Konferenz, Day 1</itunes:keywords>
      <itunes:summary>Accessibility is often treated as a mere compliance checkbox or something the “UI people” worry about at the end of a project. In reality, accessibility is a core quality attribute of software systems, and many of the biggest wins come from small decisions developers make every day: how we structure HTML, name components, log errors, design APIs, or write tests.
          In this talk, we look at accessibility from a software engineering perspective. I will introduce the most common types of disabilities and assistive technologies, then show how they map to concrete engineering practices across the stack: semantics (and ARIA) in the frontend, accessible design systems, error message design, and test automation for accessibility. Attendees will leave with a practical checklist they can use in coding and code reviews. 
          The goal is not to make everyone an accessibility expert, but to make accessibility a natural part of our everyday engineering work.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/engelbrecht.html
</itunes:summary>
      <itunes:duration>00:43:07</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/bobkonf/2026/9-2224d8eb-5642-4c18-9880-7eac3c185428.jpg"/>
    </item>
    <item>
      <title>A crash course on the OCaml module language (bobkonf2026)</title>
      <link>https://media.ccc.de/v/bob11-2026-ocaml-module-language-woestyne</link>
      <description>Many programming languages offer modules, namespaces, or package systems. But very few provide **a true module language**. In this talk, we’ll explore OCaml’s powerful module system as a core language feature. We’ll learn how to use modules effectively, understand their design principles and limitations, and discuss the challenges posed by type equalities, type preservation, and strengthening. We’ll also look at ongoing work clarifying their semantics, including recursive modules, type anchoring, and signature avoidance. We’ll see how modules solve real problems, discover clever and expressive encodings, and identify their practical limits. 
          
          Along the way, we’ll build familiarity with key concepts such as functors, applicative and generative functors, ascriptions, and strengthening and understand how OCaml’s module language enables elegant, modular, and type-safe program design.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/woestyne.html
</description>
      <enclosure url="https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-2-eng-A_crash_course_on_the_OCaml_module_language_hd.mp4"
        length="138412032"
        type="video/mp4"/>
      <pubDate>Fri, 13 Mar 2026 10:15:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-2-eng-A_crash_course_on_the_OCaml_module_language_hd.mp4?1779208027</guid>
      <dc:identifier>da9a9d6f-dafd-48c1-8dd4-47f6a2eb34b8</dc:identifier>
      <dc:date>2026-03-13T10:15:00+01:00</dc:date>
      <itunes:author>Xavier Van de Woestyne</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>2, 2026, bob2026, Talk, Talks #1, bob2026-eng, BOB, BOB Konferenz, Day 1</itunes:keywords>
      <itunes:summary>Many programming languages offer modules, namespaces, or package systems. But very few provide **a true module language**. In this talk, we’ll explore OCaml’s powerful module system as a core language feature. We’ll learn how to use modules effectively, understand their design principles and limitations, and discuss the challenges posed by type equalities, type preservation, and strengthening. We’ll also look at ongoing work clarifying their semantics, including recursive modules, type anchoring, and signature avoidance. We’ll see how modules solve real problems, discover clever and expressive encodings, and identify their practical limits. 
          
          Along the way, we’ll build familiarity with key concepts such as functors, applicative and generative functors, ascriptions, and strengthening and understand how OCaml’s module language enables elegant, modular, and type-safe program design.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/woestyne.html
</itunes:summary>
      <itunes:duration>00:44:08</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/bobkonf/2026/2-da9a9d6f-dafd-48c1-8dd4-47f6a2eb34b8.jpg"/>
    </item>
    <item>
      <title>Going back in time with the Undoable Monad (bobkonf2026)</title>
      <link>https://media.ccc.de/v/bob11-2026-undoable-monad-elliot</link>
      <description>Slipshow is a presentation tool. One of its specificity is that it is
          not based on slides, but on an infinite canvas on which you can zoom
          or scroll. Yet, compared to Prezi, the source of a presentation is
          text.
          
          The way the author defines the dynamic of its presentation is by
          intertwining actions in its textual content. Slipshow allows many
          actions, such as revealing new content, scrolling or zooming, starting
          an animation, or even starting a script defined by the user. This
          gives the author freedom in how they want to present.
          
          However, for Slipshow itself, this is a programming challenge: How to
          allow to go back in your presentation&#39;s steps? How to organize the
          code so that it&#39;s not restricting to adding new actions, and that it&#39;s
          easy to maintain?
          
          Originally written in JavaScript, Slipshow has suffered from bad
          design in this space. However, since its rewrite in OCaml, the
          opportunity to tackle this problem has been taken, with great success
          and much more stability, using the Undoable Monad.
          
          Monads are a way to embed a &quot;computing&quot; DSL in a programming
          language. They allow to define a &quot;variant&quot; of computation (for
          instance &quot;concurrent programming&quot;) and let the user program in that
          new way, almost transparently.
          
          The Undoable Monad provides an excellent example of monad: it is
          simple enough, yet solves a real problem in an elegant way. This talk
          is a fun and practical introduction to monadic programming.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/paul-elliot.html
</description>
      <enclosure url="https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-3-eng-Going_back_in_time_with_the_Undoable_Monad_hd.mp4"
        length="145752064"
        type="video/mp4"/>
      <pubDate>Fri, 13 Mar 2026 11:05:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/bobkonf/2026/h264-hd/bob2026-3-eng-Going_back_in_time_with_the_Undoable_Monad_hd.mp4?1779208725</guid>
      <dc:identifier>aef73580-5ac6-437f-bf3e-7780af9123e7</dc:identifier>
      <dc:date>2026-03-13T11:05:00+01:00</dc:date>
      <itunes:author>Paul-Elliot</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>3, 2026, bob2026, Talk, Talks #1, bob2026-eng, BOB, BOB Konferenz, Day 1</itunes:keywords>
      <itunes:summary>Slipshow is a presentation tool. One of its specificity is that it is
          not based on slides, but on an infinite canvas on which you can zoom
          or scroll. Yet, compared to Prezi, the source of a presentation is
          text.
          
          The way the author defines the dynamic of its presentation is by
          intertwining actions in its textual content. Slipshow allows many
          actions, such as revealing new content, scrolling or zooming, starting
          an animation, or even starting a script defined by the user. This
          gives the author freedom in how they want to present.
          
          However, for Slipshow itself, this is a programming challenge: How to
          allow to go back in your presentation&#39;s steps? How to organize the
          code so that it&#39;s not restricting to adding new actions, and that it&#39;s
          easy to maintain?
          
          Originally written in JavaScript, Slipshow has suffered from bad
          design in this space. However, since its rewrite in OCaml, the
          opportunity to tackle this problem has been taken, with great success
          and much more stability, using the Undoable Monad.
          
          Monads are a way to embed a &quot;computing&quot; DSL in a programming
          language. They allow to define a &quot;variant&quot; of computation (for
          instance &quot;concurrent programming&quot;) and let the user program in that
          new way, almost transparently.
          
          The Undoable Monad provides an excellent example of monad: it is
          simple enough, yet solves a real problem in an elegant way. This talk
          is a fun and practical introduction to monadic programming.

Licensed to the public under https://creativecommons.org/licenses/by/3.0/de
about this event: https://bobkonf.de/2026/paul-elliot.html
</itunes:summary>
      <itunes:duration>00:42:23</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/bobkonf/2026/3-aef73580-5ac6-437f-bf3e-7780af9123e7.jpg"/>
    </item>
    <generator>media.ccc.de / RSS 0.3.2</generator>
    <itunes:category text="Technology"/>
    <itunes:image href="https://static.media.ccc.de/media/events/bobkonf/2026/logo.png"/>
    <itunes:owner>
      <itunes:name>CCC media team</itunes:name>
      <itunes:email>media@c3voc.de</itunes:email>
    </itunes:owner>
    <itunes:author>CCC media team</itunes:author>
    <itunes:explicit>No</itunes:explicit>
    <itunes:keywords>CCC Congress Hacking Security Netzpolitik</itunes:keywords>
    <itunes:subtitle>A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de</itunes:subtitle>
    <itunes:summary>A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from bobkonf2026 as mp4</itunes:summary>
  </channel>
</rss>