<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nikita Karamov</title>
    <description></description>
    <link>https://speakerdeck.com/kytta</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/kytta.rss"/>
    <lastBuildDate>2026-06-27 08:32:46 -0400</lastBuildDate>
    <item>
      <title>Should you trust Trusted Publishing?</title>
      <description>First presented at &lt;a href="https://ep2026.europython.eu/"&gt;EuroPython 2026&lt;/a&gt; in Kraków, Poland.

In 2023, PyPI started supporting Trusted Publishers: A way to publish Python packages to PyPI without relying on insecure password and short-lived tokens. Three years later, this approach has become the default answer to package registries' security, as it found its way into NPM, crates.io, and RubyGems. But does it actually offer the benefits we hoped it would? Can you really trust the green checkmark, and if you can't, what's the point?

In this talk, I want to look closely at what Trusted Publishers are, and what we might think they are; who they do and do not protect. We'll explore the potential centralization problem of relying on Big Tech, US-based CI providers, leaving little room for smaller players like Codeberg and Sourcehut, as well as self-hosted Git forges and CI engines.</description>
      <media:content url="https://files.speakerdeck.com/presentations/9da48626d08d43b1a7685504dc9ef3fe/preview_slide_0.jpg?39997955" type="image/jpeg" medium="image"/>
      <content:encoded>First presented at &lt;a href="https://ep2026.europython.eu/"&gt;EuroPython 2026&lt;/a&gt; in Kraków, Poland.

In 2023, PyPI started supporting Trusted Publishers: A way to publish Python packages to PyPI without relying on insecure password and short-lived tokens. Three years later, this approach has become the default answer to package registries' security, as it found its way into NPM, crates.io, and RubyGems. But does it actually offer the benefits we hoped it would? Can you really trust the green checkmark, and if you can't, what's the point?

In this talk, I want to look closely at what Trusted Publishers are, and what we might think they are; who they do and do not protect. We'll explore the potential centralization problem of relying on Big Tech, US-based CI providers, leaving little room for smaller players like Codeberg and Sourcehut, as well as self-hosted Git forges and CI engines.</content:encoded>
      <pubDate>Wed, 15 Jul 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/kytta/should-you-trust-trusted-publishing</link>
      <guid>https://speakerdeck.com/kytta/should-you-trust-trusted-publishing</guid>
    </item>
    <item>
      <title>Start contributing to OpenStreetMap today!</title>
      <description>Lightning talk given at &lt;a href="https://2025.pycon.ee/"&gt;PyCon Estonia 2025&lt;/a&gt;.</description>
      <media:content url="https://files.speakerdeck.com/presentations/094ea53df99741dc9965b1e7f11655a0/preview_slide_0.jpg?39831241" type="image/jpeg" medium="image"/>
      <content:encoded>Lightning talk given at &lt;a href="https://2025.pycon.ee/"&gt;PyCon Estonia 2025&lt;/a&gt;.</content:encoded>
      <pubDate>Thu, 02 Oct 2025 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/kytta/start-contributing-to-openstreetmap-today</link>
      <guid>https://speakerdeck.com/kytta/start-contributing-to-openstreetmap-today</guid>
    </item>
  </channel>
</rss>
