specifically something to block certain bad words

[git.ikiwiki.info.git] / doc / tips / howto_avoid_flooding_aggregators.mdwn

diff --git a/doc/tips/howto_avoid_flooding_aggregators.mdwn b/doc/tips/howto_avoid_flooding_aggregators.mdwn
index d432464fc21ba486101813acf1dd2e92b8f204b1..61d44ef5b0087c2c5bf9595e77dfdd0a4c8fcdce 100644 (file)
--- a/doc/tips/howto_avoid_flooding_aggregators.mdwn
+++ b/doc/tips/howto_avoid_flooding_aggregators.mdwn
@@ -1,25 +1,30 @@
+[[!meta date="2007-04-14 20:29:32 +0000"]]
+

 If you have a [[blog]] that is aggregated, either on a site like Planet
 Debian, or just through user subscriptions, one common problem is that
 If you have a [[blog]] that is aggregated, either on a site like Planet
 Debian, or just through user subscriptions, one common problem is that

-changes to the guids of items in the blog can "flood" the aggregator,
+changes to the guids of items in the blog can “flood” the aggregator,

 causing all recent blog entries to be posted to the top of it. 
 
 This can happen in a lot of situations:
 
 causing all recent blog entries to be posted to the top of it. 
 
 This can happen in a lot of situations:
 

-* Perhaps you've just switched to ikiwiki from some other blog engine and
+* Perhaps you’ve just switched to ikiwiki from some other blog engine and

   imported your data.
   imported your data.

-* Perhaps you've turned on the `usedirs` setting, which changes all the
+* Perhaps you’ve turned on the `usedirs` setting, which changes all the

   urls in your wiki. Even if you set up
   [[redirections|redirections_for_usedirs]] for the old urls, you still face
   the issue of flooding aggregators.
   urls in your wiki. Even if you set up
   [[redirections|redirections_for_usedirs]] for the old urls, you still face
   the issue of flooding aggregators.

-* Perhaps you've just moved stuff around in your wiki.
+* Perhaps you’ve just moved stuff around in your wiki.
+
+To avoid annoying readers in these situations, it’s a good idea to remove
+any existing items from your blog’s news feed. That way only new items will
+show up in the aggregator. The best way to do this is to add a `feedpages`
+parameter to the `inline` directive for your blog, with a condition such as:

 
 

-To avoid annoying readers in these situations, it's a good idea to remove
-and existing items from your blog's news feed. That way only new items will
-show up in the aggregator. The best way to do this is currently to modify
-the [[PageSpec]] for your [[blog]] and add a condition such as:
+       feedpages=created_after(blog/posts/old_post)

 
 

-       and created_after(blog/posts/old_post)
+Where “old_post” is the name of the last post you made to the blog before
+making the change. This will limit the feed to only newer posts, while still
+displaying the old posts in the blog page.

 
 

-Where "old_post" is the name of the last post you made to the blog before
-making the change. This will limit the feed to only newer posts (the older
-posts will still be available in the archives).
+Alternatively, you can add the [[plugins/meta]] guid directives to pages,
+to force the old url to be used.