Post B33SpkGDrbN1tsjLBg by mitch@podcastindex.social
 (DIR) More posts by mitch@podcastindex.social
 (DIR) Post #B33Spgn2ldFP8W3Un2 by mitch@podcastindex.social
       2026-02-06T16:18:48Z
       
       0 likes, 0 repeats
       
       @dave @alecksgates @suorcd I think we discussed this before, but wanted to confirm.The PI docs said a podcast:guid should be v5, but you also said that shouldn't be a strict requirement.I'd like to implement at least some validation on that column in our database. Do you think v4 and v5 would be enough? Or just validate that it follows any of the uuid schemas? (apparently there are 8 versions)
       
 (DIR) Post #B33SpiENPUhnbZqq24 by mitch@podcastindex.social
       2026-02-06T16:22:41Z
       
       0 likes, 0 repeats
       
       @dave @alecksgates @suorcd LLM suggests v1, v2, v4, and v5.v3 apparently is deprecated.v6, v7 seem reasonable.v8 is "custom" which maybe we don't want.
       
 (DIR) Post #B33SpjAVvLD4Vt3GeO by ericpp@podcastindex.social
       2026-02-06T16:54:59Z
       
       0 likes, 0 repeats
       
       @mitch @dave @alecksgates @suorcd The uuid versions all have different purposes https://ntietz.com/blog/til-uses-for-the-different-uuid-versions/Uuid v5 is generated from a piece of data, which the PI docs say to use the feed URL for the data.
       
 (DIR) Post #B33SpkGDrbN1tsjLBg by mitch@podcastindex.social
       2026-02-06T17:11:06Z
       
       0 likes, 0 repeats
       
       @ericpp @dave @alecksgates @suorcd that makes sense. However since the feed URL can change at a later time, I believe from the v5 requirement is not actually required any more.I'll just add validation that it is any uuid (36 chars, 8-4-4-4-12).
       
 (DIR) Post #B33SpknXri1dZEJx7w by dave@podcastindex.social
       2026-02-06T19:56:25Z
       
       0 likes, 0 repeats
       
       @mitch @ericpp @alecksgates @suorcd v5 was just to have a know starting point. As long as the value is in-spec format wise and globally unique it’s going to be fine.