All the sites I run use RSS feeds as a way to monitor changes to the
website and that includes edits.
I guess it depends on what the purpose of your wiki is. For
collaborative-style wiki's (like pmwiki.org), monitoring edits is
needed. If you're running a blog-style site, just new entries added to
the WikiTrail used for RSS generation is needed.
So, the current default for RSS is geared toward more of a blog-style
website. I'd like to switch the default to wiki-like edit monitoring
(we are a wiki, after all), but I don't know what the majority of
PmWiki admins do with their sites.
Edit monitoring includes new entry monitoring, but the opposite is not
true. New entry monitoring skips over edits to old pages. I'd rather
have extra updates than miss some by default.
Avast!
Daniel Roesler
diaf...@gmail.com
On Sat, Jan 2, 2010 at 11:47 AM, Patrick R. Michaud <pmich...@pobox.com> wrote:
> On Sat, Jan 02, 2010 at 11:33:01AM -0600, Daniel Roesler wrote:
>> I say we have the <link> element contain {$PageUrl} (like it does now)
>> and add a separate <guid> element that adds on a unique identifier by
>> default. I'm ok with the uid being ISO instead of Unix, but we really
>> need unique links for RSS feeds.
>
> We *do* have unique links for RSS feeds -- each page url serves
> as its own guid (by virtue of there not being a guid entry by
> default).
>
> The question I'm posing is whether each separate edit to a page
> should default to generating a new guid for the page. I think
> that should be a per-site decision, not something that PmWiki
> dictates to be the case.
>
> On the other hand, if the vast majority of sites expect that
> every edit should result in a new entry in an aggregator, then
> I'm willing to change the default, as long as we make it clear
> how to get back to the other behavior.
>
> Pm
>
_______________________________________________
pmwiki-devel mailing list
pmwiki-devel@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-devel
