aboutsummaryrefslogtreecommitdiff
path: root/doc/tips/howto_avoid_flooding_aggregators.mdwn
diff options
context:
space:
mode:
authorPaulePanter <PaulePanter@web>2009-03-04 05:48:18 -0500
committerJoey Hess <joey@kitenet.net>2009-03-04 05:48:18 -0500
commit2d6bbdcf3f0878a870ce63a02f38eb8b95f0932e (patch)
tree59de706d0ea92f2cdbe02a1fceda124447fb0a14 /doc/tips/howto_avoid_flooding_aggregators.mdwn
parent2907bec3e6ebeb99c80985cf48fb5db45eee81bc (diff)
downloadikiwiki-2d6bbdcf3f0878a870ce63a02f38eb8b95f0932e.tar
ikiwiki-2d6bbdcf3f0878a870ce63a02f38eb8b95f0932e.tar.gz
typo and typography
Diffstat (limited to 'doc/tips/howto_avoid_flooding_aggregators.mdwn')
-rw-r--r--doc/tips/howto_avoid_flooding_aggregators.mdwn16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/tips/howto_avoid_flooding_aggregators.mdwn b/doc/tips/howto_avoid_flooding_aggregators.mdwn
index 98cef9249..e45b96689 100644
--- a/doc/tips/howto_avoid_flooding_aggregators.mdwn
+++ b/doc/tips/howto_avoid_flooding_aggregators.mdwn
@@ -1,27 +1,27 @@
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:
-* 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.
-* 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.
-* 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
+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:
feedpages=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 stil
+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.
Alternatively, you can add the [[plugins/meta]] guid directives to pages,