Closed ltsavar closed 12 years ago
Why would we want to do that?
If we would change the GUID of a post, all podcatchers would download this episode again, even if the user already listened to the episode. As a user, I certainly wouldn't want that.
Is there any valid use case for this that wouldn't upset our listeners?
if a corrupt version is uploaded in the first place we definitely want hat every client downloads again
Would it work for you to have an optional field in the post metadata like "guid_append" or something like that which is appended to the GUID when it is set?
E.g:
layout: post
...
guid_append: "-2"
yes
You can now use
release: 2342
Which will be appended to the normal guid entry. E.g:
<guid isPermaLink="false">http://blog.binaergewitter.de/blog/2012/03/22/binaergewitter-talk-number-7-asscrypt-2342</guid>
maybe as release in metadata
if shownotes or anythingelse is updates guid has to change