Comments on: An MT Plugin for Banned IP Lists http://www.shaftek.org/blog/2005/02/01/an-mt-plugin-for-banned-ip-lists/ ShafTek.org = SHAFranovich TECHnologies Sun, 05 Feb 2012 15:43:17 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: netwizard http://www.shaftek.org/blog/2005/02/01/an-mt-plugin-for-banned-ip-lists/comment-page-1/#comment-126 netwizard Wed, 02 Feb 2005 00:18:41 +0000 http://www.shaftek.org/blog/2005/02/01/an-mt-plugin-for-banned-ip-lists/#comment-126 You may be right, I just put together RSS as a quick and dirty hack. However, due to the way MovableType keeps its internal blacklists it doesn't leave much other information available. So there is plenty of work for me to do still on this :) You may be right, I just put together RSS as a quick and dirty hack. However, due to the way MovableType keeps its internal blacklists it doesn’t leave much other information available. So there is plenty of work for me to do still on this :)

]]> By: Grumpy http://www.shaftek.org/blog/2005/02/01/an-mt-plugin-for-banned-ip-lists/comment-page-1/#comment-125 Grumpy Wed, 02 Feb 2005 00:04:59 +0000 http://www.shaftek.org/blog/2005/02/01/an-mt-plugin-for-banned-ip-lists/#comment-125 Interesting, but do you think RSS is the right format? I agree it should probably be XML. After reading <a href="http://www.clagnut.com/blog/249/" rel="nofollow">this post</a>, I'm thinking the architecture should be one where each blog publishes its blacklist plus the intersection of entries in the blacklists being subscribed to. The intersection in XML would look something like: <ul> <li>source of entry - for accountability and determining how many people the spammer has hit</li> <li>hops - every time a blog propagates the entry, this value is incremented</li> <li>ip address/uri pair - perhaps ip addresses are not good enough because of big isp proxies, and uri's can always be forged by themselves. </li></ul> <br /> Just noodling. Interesting, but do you think RSS is the right format? I agree it should probably be XML. After reading this post, I’m thinking the architecture should be one where each blog publishes its blacklist plus the intersection of entries in the blacklists being subscribed to. The intersection in XML would look something like:

  • source of entry – for accountability and determining how many people the spammer has hit
  • hops – every time a blog propagates the entry, this value is incremented
  • ip address/uri pair – perhaps ip addresses are not good enough because of big isp proxies, and uri’s can always be forged by themselves.

Just noodling.

]]>