Lots of rss readers, especially podcatchers make use of read/unread as a state for entries. the GUID is the primary identifier for handling state. As such, it's generally good to have an identifier that is stable across minor/common refactors. Output URLs are prone to change when refactoring a site or theme making. Personally, I think slugs would be a better default when GUID is unspecified but there are use cases where a UUID is the best option (esp. podcasts).
You make a good point for not storing a UUID in the post by default, though I still like it as a configuration option. I still think it would be good to move away from output URL as the default GUID value when unspecified in a post. --George On Mon, Apr 16, 2018 at 12:26 AM Chris Warrick <kwpol...@gmail.com> wrote: > On 16 April 2018 at 05:09, George Leslie-Waksman <waks...@gmail.com> > wrote: > > Nikola already supports a `guid` metadata field for use as the feed post > > identifier and it defaults to url when unspecified. I'm proposing adding > the > > option to autogenerate this field on `nikola new_post` > > Is there any specific reason why? RSS readers don’t care about the > specific value, path, or guid, or yesterday’s lottery numbers. The > only issue with our path GUIDs is when you change the source file > paths/destinations, which I suppose is rare. Having a random number in > all generated posts doesn’t seem necessary to me — and doing it by > default would just be confusing. > > -- > Chris Warrick <https://chriswarrick.com/> > PGP: 5EAAEA16 > > -- > You received this message because you are subscribed to the Google Groups > "nikola-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nikola-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "nikola-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to nikola-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
