<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openai on Ian&#39;s (not so) technical blog</title>
    <link>https://dev-www.0x69616e.com/tags/openai/</link>
    <description>Recent content in Openai on Ian&#39;s (not so) technical blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Ian Wilson.</copyright>
    <lastBuildDate>Tue, 21 Nov 2023 00:23:04 -0600</lastBuildDate>
    <atom:link href="https://dev-www.0x69616e.com/tags/openai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenAI and AImageddon</title>
      <link>https://dev-www.0x69616e.com/posts/openai-ma-geddon/</link>
      <pubDate>Tue, 21 Nov 2023 00:23:04 -0600</pubDate>
      <guid>https://dev-www.0x69616e.com/posts/openai-ma-geddon/</guid>
      <description>&lt;p&gt;Well, if you haven&amp;rsquo;t heard, there&amp;rsquo;s some drama afoot in the world of AI.&lt;/p&gt;&#xA;&lt;p&gt;I don&amp;rsquo;t think I could effectively re-hash what&amp;rsquo;s going on here, but, from a security engineering point of view, AI/AGI is so new that there&amp;rsquo;s still a really untapped world of vulnerabilities that is out there to explore.  Can you trust your company&amp;rsquo;s data with a vendor (OpenAI, in this case) who had a 95% staff turnover rate?  Do you think that a new team of engineers could promptly resolve and mitigate any vulnerabilities that could spring up in the next few years (because if some Investment firm gobbles it up in its present state, they&amp;rsquo;re probably going to put the tech on cruise control and let the software stagnate until it loses all velocity and basically becomes another piece of ghost SaaS that is out there)?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
