{ "attachments": [], "comments_archived": true, "date": "2003-06-25T23:12:08.000Z", "layout": "post", "title": "GUIDs in RSS rock", "wordpress_id": 431, "wordpress_slug": "guids-in-rss-rock", "wordpress_url": "http://www.decafbad.com/blog/?p=431", "year": "2003", "month": "06", "day": "25", "isDir": false, "slug": "guids-in-rss-rock", "type": "entry", "postName": "2003-06-25-guids-in-rss-rock", "html": "
Guids sure have a funny name, but they're quite useful. If your weblog tool supports them, use them. If not, ask the developer to add the support. It's not very hard.\n\n\n\n

Further, I strongly believe that all aggregators and readers should pay attention to guids where they are available. It's a convenience that many users will appreciate, especially people who are in a hurry

\n
Source:Guids are not just for geeks anymore ;->\n\n
\n\n\n\n\n\n

Haven't really been saying much lately about the recent plunge, albeit more amiable this time, back\ninto the RSS and weblog syndication frey. Mostly because I haven't had the time, and mostly because\npeople more eloquent than I were already saying what I thought.

\n

In the meantime, I've been working, and puttering around with \nmy own aggregator as spare time comes up.\nAnd you know, I'm tired of having to come up with some mechanism to detect new entries.\nThis GUID thing is what I need. I don't want to run MD5 on another RSS item, and I don't\ncare to track the minor edits people do on their entries, like Dave said.

\n

Personally, I think the GUID should be the permalink, if at all possible. I used \nto think that that was what the link of an RSS item should be, but then I never really\nmaintained a weblog in the quote-link-comment style for long stretches. My entries\naren't usually completely about someone else's article. But, some weblogs are \nlike that. So, link points to a subject under comment, GUID identifies the entry and\nideally does it via permalink.

\n

Nifty.

\n\n\n\n

shortname=guids_in_rss_rock

\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "
Guids sure have a funny name, but they're quite useful. If your weblog tool supports them, use them. If not, ask the developer to add the support. It's not very hard.\r\n

\r\nFurther, I strongly believe that all aggregators and readers should pay attention to guids where they are available. It's a convenience that many users will appreciate, especially people who are in a hurry
\r\n
Source:Guids are not just for geeks anymore ;->
\r\n

\r\nHaven't really been saying much lately about the recent plunge, albeit more amiable this time, back\r\ninto the RSS and weblog syndication frey. Mostly because I haven't had the time, and mostly because\r\npeople more eloquent than I were already saying what I thought.\r\n

\r\nIn the meantime, I've been working, and puttering around with \r\nmy own aggregator as spare time comes up.\r\nAnd you know, I'm tired of having to come up with some mechanism to detect new entries.\r\nThis GUID thing is what I need. I don't want to run MD5 on another RSS item, and I don't\r\ncare to track the minor edits people do on their entries, like Dave said.\r\n

\r\nPersonally, I think the GUID should be the permalink, if at all possible. I used \r\nto think that that was what the link of an RSS item should be, but then I never really\r\nmaintained a weblog in the quote-link-comment style for long stretches. My entries\r\naren't usually completely about someone else's article. But, some weblogs are \r\nlike that. So, link points to a subject under comment, GUID identifies the entry and\r\nideally does it via permalink.\r\n

\r\nNifty.\r\n\r\nshortname=guids_in_rss_rock\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2003", "path": "2003/06/25/guids-in-rss-rock", "summary": "Guids sure have a funny name, but they're quite useful. If your weblog tool supports them, use them. If not, ask the developer to add the support. It's not very hard.\n\n\n\nFurther, I strongly believe that all aggregators and readers should pay attention to guids where they are available. It's a convenience that many users will appreciate, especially people who are in a hurry\nSource:Guids are not just for geeks anymore ;->\n\n\n\n\n\n\n\nHaven't really been saying much lately about the recent plunge, albeit more amiable this time, back\ninto the RSS and weblog syndication frey. Mostly because I haven't had the time, and mostly because\npeople more eloquent than I were already saying what I thought.\nIn the meantime, I've been working, and puttering around with \nmy own aggregator as spare time comes up.\nAnd you know, I'm tired of having to come up with some mechanism to detect new entries.\nThis GUID thing is what I need. I don't want to run MD5 on another RSS item, and I don't\ncare to track the minor edits people do on their entries, like Dave said.\nPersonally, I think the GUID should be the permalink, if at all possible. I used \nto think that that was what the link of an RSS item should be, but then I never really\nmaintained a weblog in the quote-link-comment style for long stretches. My entries\naren't usually completely about someone else's article. But, some weblogs are \nlike that. So, link points to a subject under comment, GUID identifies the entry and\nideally does it via permalink.\nNifty.", "needsBuild": true, "prevPostPath": "2003/06/25/font-borken", "prevPostTitle": "Why is my Monaco Borken?", "nextPostPath": "2003/06/25/adsense-no", "nextPostTitle": "No Google AdSense for Me" }