<rss
      xmlns:atom="http://www.w3.org/2005/Atom"
      xmlns:media="http://search.yahoo.com/mrss/"
      xmlns:content="http://purl.org/rss/1.0/modules/content/"
      xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      version="2.0"
    >
      <channel>
        <title><![CDATA[Tim Bouma]]></title>
        <description><![CDATA[Tim Bouma @trbouma on Twitter. Let's see how this goes!]]></description>
        <link>https://tim-bouma.npub.pro/tag/npub/</link>
        <atom:link href="https://tim-bouma.npub.pro/tag/npub/rss/" rel="self" type="application/rss+xml"/>
        <itunes:new-feed-url>https://tim-bouma.npub.pro/tag/npub/rss/</itunes:new-feed-url>
        <itunes:author><![CDATA[Tim Bouma]]></itunes:author>
        <itunes:subtitle><![CDATA[Tim Bouma @trbouma on Twitter. Let's see how this goes!]]></itunes:subtitle>
        <itunes:type>episodic</itunes:type>
        <itunes:owner>
          <itunes:name><![CDATA[Tim Bouma]]></itunes:name>
          <itunes:email><![CDATA[Tim Bouma]]></itunes:email>
        </itunes:owner>
            
      <pubDate>Mon, 05 May 2025 12:50:51 GMT</pubDate>
      <lastBuildDate>Mon, 05 May 2025 12:50:51 GMT</lastBuildDate>
      
      <itunes:image href="https://raw.githubusercontent.com/trbouma/assets/main/profile_pic_crop.png" />
      <image>
        <title><![CDATA[Tim Bouma]]></title>
        <link>https://tim-bouma.npub.pro/tag/npub/</link>
        <url>https://raw.githubusercontent.com/trbouma/assets/main/profile_pic_crop.png</url>
      </image>
      <item>
      <title><![CDATA[I am now %100 certain that…]]></title>
      <description><![CDATA[I am now %100 certain that I can build a permissionless, decentralized credential presentation and verification system.

In the example below, the only unencrypted channel is the visual invocation and acquisition of a #nauth presented as a QR code. Once acquired, the rest of the communication, including the request for,…]]></description>
             <itunes:subtitle><![CDATA[I am now %100 certain that I can build a permissionless, decentralized credential presentation and verification system.

In the example below, the only unencrypted channel is the visual invocation and acquisition of a #nauth presented as a QR code. Once acquired, the rest of the communication, including the request for,…]]></itunes:subtitle>
      <pubDate>Mon, 05 May 2025 12:50:51 GMT</pubDate>
      <link>https://tim-bouma.npub.pro/post/note1rl4jmk294qn40vds74rm5tndks9ztzdfgtkskf4cx8wy8v4gw3ms2uwdum/</link>
      <comments>https://tim-bouma.npub.pro/post/note1rl4jmk294qn40vds74rm5tndks9ztzdfgtkskf4cx8wy8v4gw3ms2uwdum/</comments>
      <guid isPermaLink="false">note1rl4jmk294qn40vds74rm5tndks9ztzdfgtkskf4cx8wy8v4gw3ms2uwdum</guid>
      <category>nauth</category>
      
      <noteId>note1rl4jmk294qn40vds74rm5tndks9ztzdfgtkskf4cx8wy8v4gw3ms2uwdum</noteId>
      <npub>npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5</npub>
      <dc:creator><![CDATA[Tim Bouma]]></dc:creator>
      <content:encoded><![CDATA[<p>I am now %100 certain that I can build a permissionless, decentralized credential presentation and verification system.<br><br>In the example below, the only unencrypted channel is the visual invocation and acquisition of a <a href='/tag/nauth/'>#nauth</a> presented as a QR code. Once acquired, the rest of the communication, including the request for, and presentation of a credential is done via negotiated encrypted channels.<br><br>The end user web apps (the UX front end of <a href='/tag/safebox/'>#safebox</a>) only communicate to their own user; they do not directly communicate with one another. Actually, each app has no clue, nor cares where the other app is running. All inter-app communication is done in real-time using  gift-wrapped encrypted messages. <br><br>It's the <a href='/tag/nostr/'>#nostr</a> protocol that enables this. IMHO, the killer-app for <a href='/tag/nostr/'>#nostr</a> is rather a killer-capability for every app tha wishes to securely communicate with any other app, so long as they have a <a href='/tag/npub/'>#npub</a>, and a pool of available relays. <br><br><br><np-embed nostr="nevent1qqsvpyjh26w8muqfe7fdr2smvt5takr4ctuvt8v6dxrwl0a4rnd3engpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqxk7qe6lcu0a28yyvzvmkhhj58shww4cy7xm4r5jhkvhrdrkpj0spsgqqqqqqsp6s8lz"><a href="/post/note1czf9w45u0hcqnnuj6x4pkchghmv8tshcckwe56vxa7lm28xmrnxsh6xgwe/">This is the user flow using…</a></np-embed></p>
]]></content:encoded>
      <itunes:author><![CDATA[Tim Bouma]]></itunes:author>
      <itunes:summary><![CDATA[<p>I am now %100 certain that I can build a permissionless, decentralized credential presentation and verification system.<br><br>In the example below, the only unencrypted channel is the visual invocation and acquisition of a <a href='/tag/nauth/'>#nauth</a> presented as a QR code. Once acquired, the rest of the communication, including the request for, and presentation of a credential is done via negotiated encrypted channels.<br><br>The end user web apps (the UX front end of <a href='/tag/safebox/'>#safebox</a>) only communicate to their own user; they do not directly communicate with one another. Actually, each app has no clue, nor cares where the other app is running. All inter-app communication is done in real-time using  gift-wrapped encrypted messages. <br><br>It's the <a href='/tag/nostr/'>#nostr</a> protocol that enables this. IMHO, the killer-app for <a href='/tag/nostr/'>#nostr</a> is rather a killer-capability for every app tha wishes to securely communicate with any other app, so long as they have a <a href='/tag/npub/'>#npub</a>, and a pool of available relays. <br><br><br><np-embed nostr="nevent1qqsvpyjh26w8muqfe7fdr2smvt5takr4ctuvt8v6dxrwl0a4rnd3engpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqxk7qe6lcu0a28yyvzvmkhhj58shww4cy7xm4r5jhkvhrdrkpj0spsgqqqqqqsp6s8lz"><a href="/post/note1czf9w45u0hcqnnuj6x4pkchghmv8tshcckwe56vxa7lm28xmrnxsh6xgwe/">This is the user flow using…</a></np-embed></p>
]]></itunes:summary>
      
      </item>
      
      </channel>
      </rss>
    