<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Watching Those Watching Me</title>
	<atom:link href="http://www.gringod.com/2005/03/30/watching-those-watching-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gringod.com/2005/03/30/watching-those-watching-me/</link>
	<description>Randomised nonsense.</description>
	<lastBuildDate>Tue, 13 May 2025 05:33:38 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.9.40</generator>
	<item>
		<title>By: Phrixus</title>
		<link>http://www.gringod.com/2005/03/30/watching-those-watching-me/comment-page-1/#comment-4360</link>
		<dc:creator><![CDATA[Phrixus]]></dc:creator>
		<pubDate>Fri, 01 Apr 2005 09:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gringod.com/2005/03/30/watching-those-watching-me/#comment-4360</guid>
		<description><![CDATA[I used another app called wp-stattraq for a while that showed everything. Unfortunately it started bloating the db after 6 months of use so I now just rely on the Server logs. Let us know how you get on what you do as I will be interested to see what your solution is.]]></description>
		<content:encoded><![CDATA[<p>I used another app called wp-stattraq for a while that showed everything. Unfortunately it started bloating the db after 6 months of use so I now just rely on the Server logs. Let us know how you get on what you do as I will be interested to see what your solution is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gringod</title>
		<link>http://www.gringod.com/2005/03/30/watching-those-watching-me/comment-page-1/#comment-4359</link>
		<dc:creator><![CDATA[gringod]]></dc:creator>
		<pubDate>Fri, 01 Apr 2005 08:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.gringod.com/2005/03/30/watching-those-watching-me/#comment-4359</guid>
		<description><![CDATA[That plugin looks like the sort of thing I need, however, &lt;a href=&quot;http://www.xav.com/scripts/axs/features.html&quot;&gt;AXS has the following limitations&lt;/a&gt; which phpOpenTracker doesn&#039;t:

&lt;blockquote&gt;
&lt;strong&gt;What it doesn&#039;t do&lt;/strong&gt;

AXS does not analyze your standard web server logs -- instead, it builds its own log based on the traffic it detects from the HTML snippets you&#039;ve pasted into your HTML pages. Traffic analyzers that use standard server logs are much more efficient than AXS.

AXS is pretty inefficient. It is suitable for low-traffic sites receiving a few hundred hits per day (if logs are stored for months), or sites receiving a few thousand hits per day (if logs are stored for days). For high-traffic sites, or for cases where you want to analyze years&#039; worth of data at once, AXS is not the right tool for the job.

&lt;strike&gt;AXS resides entirely on your server, unlike common remotely-hosted trackers. This means you need to be able to install and maintain a CGI script. You need to be hosted on a CGI-capable web server.&lt;/strike&gt;

&lt;strike&gt;AXS does not set cookies to track your visitors.&lt;/strike&gt; Thus, it can only count raw page views -- it cannot track unique visitors, repeat visitors, number of pages viewed per visitor, or neat things like that.
&lt;/blockquote&gt;

The only downside to phpOpenTracker is that in order to get the best reports I&#039;ll need to be doing some PHP coding of my own... nm. I&#039;ve already done most of the hard work when I wrote CrashNet.]]></description>
		<content:encoded><![CDATA[<p>That plugin looks like the sort of thing I need, however, <a href="http://www.xav.com/scripts/axs/features.html">AXS has the following limitations</a> which phpOpenTracker doesn&#8217;t:</p>
<blockquote><p>
<strong>What it doesn&#8217;t do</strong></p>
<p>AXS does not analyze your standard web server logs &#8212; instead, it builds its own log based on the traffic it detects from the HTML snippets you&#8217;ve pasted into your HTML pages. Traffic analyzers that use standard server logs are much more efficient than AXS.</p>
<p>AXS is pretty inefficient. It is suitable for low-traffic sites receiving a few hundred hits per day (if logs are stored for months), or sites receiving a few thousand hits per day (if logs are stored for days). For high-traffic sites, or for cases where you want to analyze years&#8217; worth of data at once, AXS is not the right tool for the job.</p>
<p><strike>AXS resides entirely on your server, unlike common remotely-hosted trackers. This means you need to be able to install and maintain a CGI script. You need to be hosted on a CGI-capable web server.</strike></p>
<p><strike>AXS does not set cookies to track your visitors.</strike> Thus, it can only count raw page views &#8212; it cannot track unique visitors, repeat visitors, number of pages viewed per visitor, or neat things like that.
</p></blockquote>
<p>The only downside to phpOpenTracker is that in order to get the best reports I&#8217;ll need to be doing some PHP coding of my own&#8230; nm. I&#8217;ve already done most of the hard work when I wrote CrashNet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phrixus</title>
		<link>http://www.gringod.com/2005/03/30/watching-those-watching-me/comment-page-1/#comment-4341</link>
		<dc:creator><![CDATA[Phrixus]]></dc:creator>
		<pubDate>Thu, 31 Mar 2005 17:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.gringod.com/2005/03/30/watching-those-watching-me/#comment-4341</guid>
		<description><![CDATA[How about this  http://thedeadone.net/?p=184. Seems like what you are after maybe?!?!]]></description>
		<content:encoded><![CDATA[<p>How about this  <a href="http://thedeadone.net/?p=184" >http://thedeadone.net/?p=184</a>. Seems like what you are after maybe?!?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
