<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Permissions on Sankara&#39;s Blog</title>
    <link>https://sankara.me/tags/permissions/</link>
    <description>Recent content in Permissions on Sankara&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sankara.me/tags/permissions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Siri AI and DMA</title>
      <link>https://sankara.me/posts/tech/siri-ai-and-dma/</link>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://sankara.me/posts/tech/siri-ai-and-dma/</guid>
      <description>&lt;p&gt;Treating &amp;ldquo;let Siri use a different model&amp;rdquo; as a configuration toggle skips the hard part. Permission mediation has to live in the operating system to exist at all.&lt;/p&gt;&#xA;&lt;p&gt;Take file access in a sandboxed browser. Websites have legitimate reasons to read files, and the correct design is a system file picker that any browser can invoke. The user grants scoped access deliberately, once, and never gets worn down into handing over the whole disk. Safari building its own version would defeat the purpose. That paradigm took years to arrive at.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
