<?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>Caldav on Timur Davletshin</title><link>https://davletshin.com/tags/caldav/</link><description>Recent content in Caldav on Timur Davletshin</description><generator>Hugo -- 0.147.7</generator><language>en-us</language><lastBuildDate>Tue, 29 Sep 2026 20:00:00 +0100</lastBuildDate><atom:link href="https://davletshin.com/tags/caldav/index.xml" rel="self" type="application/rss+xml"/><item><title>One Agenda, Two Private Calendars</title><link>https://davletshin.com/one-agenda-two-private-calendars/</link><pubDate>Tue, 29 Sep 2026 20:00:00 +0100</pubDate><guid>https://davletshin.com/one-agenda-two-private-calendars/</guid><description>&lt;p>My assistant used to plan from only half of my life.&lt;/p>
&lt;p>Personal and work events lived in Google Calendar. Family outings, holidays and school dates belonged in a privately shared Apple Family calendar. Both choices made sense, but the split created a dangerous failure mode: an automated daily brief could look at Google, see an empty afternoon and confidently call it free while the family calendar said otherwise.&lt;/p>
&lt;p>The fix was not to merge the calendars. It was to build one read path across both while preserving their different privacy boundaries.&lt;/p></description></item></channel></rss>