<?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"
	>
<channel>
	<title>Comments on: Scot&#8217;s Newsletter List Comes Together</title>
	<atom:link href="http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/</link>
	<description>Operating systems. Broadband. Issues. Reviews ... tech info you can use.</description>
	<pubDate>Thu, 24 Jul 2008 15:55:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Scot</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-538</link>
		<dc:creator>Scot</dc:creator>
		<pubDate>Sun, 20 Jul 2008 12:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-538</guid>
		<description>Simon, my apologies. The I steal bandwidth thing was an exercise that I quickly decided wasn't going to work. I disabled it after only a few days. However, I'm currently still blocking the display of images by serving them from my sites to other sites. (But the result now is a broken image.) I'd forgotten about the promo page, though. I think I would have to set up an exclusion and put the promo art in a different directory, which would break all the current promotion links. But as it is, they're all broken everywhere.

There is a very good reason for doing this, though -- esp. for people on a shared webhost who are meeting their bandwidth limits. If hundreds or thousands of links to images from my site are placed on other busy sites, the number of calls to my server could quickly chew through my bandwidth allotment. It's a rising problem for small websites.

It's obviously more complex, though, than I gave consideration to when I tried out this code that blocks "hot linking."

-- Scot</description>
		<content:encoded><![CDATA[<p>Simon, my apologies. The I steal bandwidth thing was an exercise that I quickly decided wasn&#8217;t going to work. I disabled it after only a few days. However, I&#8217;m currently still blocking the display of images by serving them from my sites to other sites. (But the result now is a broken image.) I&#8217;d forgotten about the promo page, though. I think I would have to set up an exclusion and put the promo art in a different directory, which would break all the current promotion links. But as it is, they&#8217;re all broken everywhere.</p>
<p>There is a very good reason for doing this, though &#8212; esp. for people on a shared webhost who are meeting their bandwidth limits. If hundreds or thousands of links to images from my site are placed on other busy sites, the number of calls to my server could quickly chew through my bandwidth allotment. It&#8217;s a rising problem for small websites.</p>
<p>It&#8217;s obviously more complex, though, than I gave consideration to when I tried out this code that blocks &#8220;hot linking.&#8221;</p>
<p>&#8211; Scot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: skiwi</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-530</link>
		<dc:creator>skiwi</dc:creator>
		<pubDate>Tue, 01 Jul 2008 21:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-530</guid>
		<description>Scott

I promote your newsletter on my website
(based on the code from your page http://scotsnewsletter.com/promo.htm).
Imagine my impleasent surprise when the code that you provided places an image on my website saying "I steal bandwidth'
(See http://kiwiwiki.co.nz/pmwiki/pmwiki.php/Test/ScotsNewsletter)

regards

Simon</description>
		<content:encoded><![CDATA[<p>Scott</p>
<p>I promote your newsletter on my website<br />
(based on the code from your page <a href="http://scotsnewsletter.com/promo.htm" rel="nofollow">http://scotsnewsletter.com/promo.htm</a>).<br />
Imagine my impleasent surprise when the code that you provided places an image on my website saying &#8220;I steal bandwidth&#8217;<br />
(See <a href="http://kiwiwiki.co.nz/pmwiki/pmwiki.php/Test/ScotsNewsletter" rel="nofollow">http://kiwiwiki.co.nz/pmwiki/pmwiki.php/Test/ScotsNewsletter</a>)</p>
<p>regards</p>
<p>Simon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scot</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-252</link>
		<dc:creator>Scot</dc:creator>
		<pubDate>Wed, 16 Jan 2008 12:53:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-252</guid>
		<description>That's true. The combination of my recuperation from surgery, promotion to editor-in-chief of Computerworld, and the advent of the holidays has left me with less time than usual to write over the last four or five weeks.

I've also put quite a few of my meager free hours into improvements to the blog and the newsletter:

&#8226; Merged newsletter lists and completely re-crafted, re-coded newsletter subscription tools. Benefits: Much easier to use subscription tools, reduced costs for me, reduced time to send newsletter.

&#8226; Research into, experimentation, and implementing both expanded bandwidth for database calls on the server and caching the blog site to hopefully eliminate problems with the blog server bogging down during the first few hours after the newsletter mails. That has been a problem each time we've mailed the newsletter since the blog site launched. Benefits: Faster blog-site performance during peak demand times.

&#8226; It may not be obvious, but I've added about 50 tweaks to the design of the blog site to improve visibility and usability. I haven't tackled the all-important navigation issue (yet), but several aspects work better than they did before. Benefit: Overall better experience and easier to read and understand blog pages.

Finally, I'm working in the background on trying to wrap up the software firewalls series, so I can give my recommendation and push onto the next series (whatever it may be). That has involved a lot of research. But I am getting closer.

I'm only going to send the newsletter when I've written enough new articles to make it worth everyone's while. I only have one substantive article since the last newsletter, so it's not time yet.

My best estimate for the next newsletter is the end of Jan. / early Feb. As a result, I will have skipped an "issue" -- something I do most years around the holidays.

-- Scot</description>
		<content:encoded><![CDATA[<p>That&#8217;s true. The combination of my recuperation from surgery, promotion to editor-in-chief of Computerworld, and the advent of the holidays has left me with less time than usual to write over the last four or five weeks.</p>
<p>I&#8217;ve also put quite a few of my meager free hours into improvements to the blog and the newsletter:</p>
<p>&bull; Merged newsletter lists and completely re-crafted, re-coded newsletter subscription tools. Benefits: Much easier to use subscription tools, reduced costs for me, reduced time to send newsletter.</p>
<p>&bull; Research into, experimentation, and implementing both expanded bandwidth for database calls on the server and caching the blog site to hopefully eliminate problems with the blog server bogging down during the first few hours after the newsletter mails. That has been a problem each time we&#8217;ve mailed the newsletter since the blog site launched. Benefits: Faster blog-site performance during peak demand times.</p>
<p>&bull; It may not be obvious, but I&#8217;ve added about 50 tweaks to the design of the blog site to improve visibility and usability. I haven&#8217;t tackled the all-important navigation issue (yet), but several aspects work better than they did before. Benefit: Overall better experience and easier to read and understand blog pages.</p>
<p>Finally, I&#8217;m working in the background on trying to wrap up the software firewalls series, so I can give my recommendation and push onto the next series (whatever it may be). That has involved a lot of research. But I am getting closer.</p>
<p>I&#8217;m only going to send the newsletter when I&#8217;ve written enough new articles to make it worth everyone&#8217;s while. I only have one substantive article since the last newsletter, so it&#8217;s not time yet.</p>
<p>My best estimate for the next newsletter is the end of Jan. / early Feb. As a result, I will have skipped an &#8220;issue&#8221; &#8212; something I do most years around the holidays.</p>
<p>&#8211; Scot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RabidWolf</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-250</link>
		<dc:creator>RabidWolf</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-250</guid>
		<description>Is this OK , that is. Stupid keyboard... :-)</description>
		<content:encoded><![CDATA[<p>Is this OK , that is. Stupid keyboard&#8230; <img src='http://blog.scotsnewsletter.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RabidWolf</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-249</link>
		<dc:creator>RabidWolf</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-249</guid>
		<description>I haven't seen an email since 12/6/2007. Is this for your newsletter, er sorry, blog?

Thanks,
Bob Martell
aka RabidWolf</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t seen an email since 12/6/2007. Is this for your newsletter, er sorry, blog?</p>
<p>Thanks,<br />
Bob Martell<br />
aka RabidWolf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LabCzar</title>
		<link>http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-244</link>
		<dc:creator>LabCzar</dc:creator>
		<pubDate>Tue, 15 Jan 2008 02:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scotsnewsletter.com/2008/01/07/scots-newsletter-list-comes-together/#comment-244</guid>
		<description>You might want to "watch" your NOD32 replies for issues with the iPhone.  (I had an iPod that worked fine with NOD32, version 2.7x)  But when I got the iPhone serious sync issues developed.  I finally tracked it down to the IMON (Internet Monitoring) module.  NOD told me that module would be replaced in version 3.x -- since 2.7 is working and not broke, I have been waiting and watching.  

Gordon (G41Potter@gmail.com)
Atlanta</description>
		<content:encoded><![CDATA[<p>You might want to &#8220;watch&#8221; your NOD32 replies for issues with the iPhone.  (I had an iPod that worked fine with NOD32, version 2.7x)  But when I got the iPhone serious sync issues developed.  I finally tracked it down to the IMON (Internet Monitoring) module.  NOD told me that module would be replaced in version 3.x &#8212; since 2.7 is working and not broke, I have been waiting and watching.  </p>
<p>Gordon (G41Potter@gmail.com)<br />
Atlanta</p>
]]></content:encoded>
	</item>
</channel>
</rss>
