BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//talk//9PU3PN
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-9PU3PN@pretalx.devconf.info
DTSTART;TZID=EST:20260924T130000
DTEND;TZID=EST:20260924T131500
DESCRIPTION:For edge devices with limited bandwidth or spotty connectivity\
 , the size of container image updates is a critical issue. This is where t
 ar-diff comes in. In just two key steps\, it permits the user to seamlessl
 y update their container image within a fraction of the time and with sign
 ificantly less system overhead. This lightning talk focuses on the interse
 ction of that technology and the personal experience of how I\, an an inte
 rn with minimal industry experience\, took a 6-year-old project and fine-t
 uned it for Fedora and RHEL distributions. I'll be talking about bridging 
 the gap between existing logic and modern container standards\, including 
 what it’s like to take ownership of a tool that will be a key feature in
  bootable container images.
DTSTAMP:20260727T174806Z
LOCATION:Hewitt Boardroom (Capacity 35)
SUMMARY:Optimizing Container Image Updates: Modernizing Tar-diff From an In
 tern’s Perspective - Rosy-Glorious Miki
URL:https://pretalx.devconf.info/devconf-us-2026/talk/9PU3PN/
END:VEVENT
END:VCALENDAR