<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>#uuids · Louche Cannon</title>
    <link>https://gbilder.com/tags/uuids/</link>
    <description>#uuids from Louche Cannon</description>
    <language>en</language>
    <lastBuildDate>Sun, 13 Oct 2024 08:08:39 +0200</lastBuildDate>
    <atom:link href="https://gbilder.com/tags/uuids/index.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Analyzing New Unique Identifier Formats (UUIDv6, UUIDv7, and UUIDv8)</title>
      <link>https://gbilder.com/bookmarks/01M4EHSAGK8T4HYTZEFKRP3R5F/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHSAGK8T4HYTZEFKRP3R5F/</guid>
      <pubDate>Sun, 13 Oct 2024 08:08:39 +0200</pubDate>
      <category>identifiers</category>
      <category>uuids</category>
      <category>grokme</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://blog.scaledcode.com/blog/analyzing-new-unique-id/&#34;&gt;https://blog.scaledcode.com/blog/analyzing-new-unique-id/&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>RFC 9562: Universally Unique IDentifiers (UUIDs)</title>
      <link>https://gbilder.com/bookmarks/01M4EHS7H966W5C47E9EXN65XC/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHS7H966W5C47E9EXN65XC/</guid>
      <pubDate>Mon, 13 May 2024 19:22:52 +0200</pubDate>
      <category>identifiers</category>
      <category>uuids</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://www.rfc-editor.org/rfc/rfc9562.html#name-name-based-uuid-generation&#34;&gt;https://www.rfc-editor.org/rfc/rfc9562.html#name-name-based-uuid-generation&lt;/a&gt;&lt;/p&gt;&#xA;  &lt;div class=&#34;e-content&#34;&gt;&lt;p&gt;6.12. Opacity&#xD;&lt;br&gt;&#xA;&#xD;&lt;br&gt;&#xA;As general guidance, avoiding parsing UUID values unnecessarily is recommended; instead, treat UUIDs as opaquely as possible. Although application-specific concerns could, of course, require some degree of introspection (e.g., to examine Sections 4.1 or 4.2 or perhaps the timestamp of a UUID), the advice here is to avoid this or other parsing unless absolutely necessary. Applications typically tend to be simpler, be more interoperable, and perform better when this advice is followed.&lt;/p&gt;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Why Choose ULIDs Over Traditional UUIDs or IDs for Database Identification?</title>
      <link>https://gbilder.com/bookmarks/01M4EHS7CNXH2H8JHMQ8XZV3K1/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHS7CNXH2H8JHMQ8XZV3K1/</guid>
      <pubDate>Mon, 06 May 2024 08:46:05 +0200</pubDate>
      <category>identifiers</category>
      <category>uuids</category>
      <category>pidantic</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://sotergreco.com/why-choose-ulids-over-traditional-uuids-or-ids-for-database-identification&#34;&gt;https://sotergreco.com/why-choose-ulids-over-traditional-uuids-or-ids-for-database-identification&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
