Re: [nikola-discuss] Generating UUID4 GUIDs on new_post?

[Roberto Alsina]

I am ok with it as long as it is hidden nehind a flag.

Can't be default or every Nikola user will flood every planet or newsreader.

El lun., 16 de abr. de 2018 7:03 PM, George Leslie-Waksman <
waks...@gmail.com> escribió:

> 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  wrote:
>
>> On 16 April 2018 at 05:09, George Leslie-Waksman 
>> 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 
>> 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.
>

-- 
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.

Re: [nikola-discuss] Generating UUID4 GUIDs on new_post?

[George Leslie-Waksman]

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  wrote:

> On 16 April 2018 at 05:09, George Leslie-Waksman 
> 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 
> 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.

Re: [nikola-discuss] Generating UUID4 GUIDs on new_post?

[Chris Warrick]

On 16 April 2018 at 05:09, George Leslie-Waksman  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 
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.

Re: [nikola-discuss] Generating UUID4 GUIDs on new_post?

[George Leslie-Waksman]

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`

On Sun, Apr 15, 2018, 3:55 PM Roberto Alsina  wrote:

> You meas as slug? Or for what specific purpose?
>
> On Sun, Apr 15, 2018 at 6:33 PM George Leslie-Waksman 
> wrote:
>
>> I like GUIDs because they're fantastically stable (when you hard-code
>> them for your posts) unlike URLs (which are config dependent). I don't
>> particularly like generating a new UUID4 every time I create a new post,
>> and it seems like we could add that to `nikola new_post`.
>>
>> I'm happy to implement it and gate it behind a configuration variable
>> just curious about feedback on a few things:
>>
>>- do folks think it's a good idea?
>>- should the configuration for generating guids default to True or
>>False?
>>- is there a generation mechanism other than uuid4 that folks prefer?
>>
>> --George
>>
>> --
>> 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.
>

-- 
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.

Re: [nikola-discuss] Generating UUID4 GUIDs on new_post?

[Roberto Alsina]

You meas as slug? Or for what specific purpose?

On Sun, Apr 15, 2018 at 6:33 PM George Leslie-Waksman 
wrote:

> I like GUIDs because they're fantastically stable (when you hard-code them
> for your posts) unlike URLs (which are config dependent). I don't
> particularly like generating a new UUID4 every time I create a new post,
> and it seems like we could add that to `nikola new_post`.
>
> I'm happy to implement it and gate it behind a configuration variable just
> curious about feedback on a few things:
>
>- do folks think it's a good idea?
>- should the configuration for generating guids default to True or
>False?
>- is there a generation mechanism other than uuid4 that folks prefer?
>
> --George
>
> --
> 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.