<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prism on slopistry</title>
    <link>https://blog.slopistry.com/tags/prism/</link>
    <description>Recent content in Prism on slopistry</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.slopistry.com/tags/prism/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>prism gets auth, goes to production, and fights safari</title>
      <link>https://blog.slopistry.com/posts/prism-auth-safari-production/</link>
      <pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.slopistry.com/posts/prism-auth-safari-production/</guid>
      <description>&lt;p&gt;Prism is an interview practice tool — you pick a topic (elocution, system design, etc.), get matched with AI panelists who have distinct personas, and do push-to-talk voice sessions that get transcribed and critiqued. Today was about hardening it for real users.&lt;/p&gt;&#xA;&lt;h2 id=&#34;sign-in-with-everything&#34;&gt;sign in with everything&lt;/h2&gt;&#xA;&lt;p&gt;Added OAuth for Google, GitHub, and Apple. Google and GitHub are standard OAuth2 flows. Apple is its own thing:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The client secret is a short-lived ES256 JWT you sign with a &lt;code&gt;.p8&lt;/code&gt; private key — not a static string&lt;/li&gt;&#xA;&lt;li&gt;The callback is &lt;code&gt;POST&lt;/code&gt; (form_post), not &lt;code&gt;GET&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;User info comes from the &lt;code&gt;id_token&lt;/code&gt; JWT, not a userinfo endpoint&lt;/li&gt;&#xA;&lt;li&gt;Apple only sends the user&amp;rsquo;s name on the &lt;em&gt;first&lt;/em&gt; authorization — subsequent logins only have email + sub&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Generated a fresh client secret per request to avoid stale-secret bugs. Used &lt;code&gt;ParseUnverified&lt;/code&gt; on the id_token since it comes server-to-server from Apple&amp;rsquo;s token endpoint over TLS.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
