<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

  <channel>
    <title>Blogging category of Luke Hutteman's public virtual MemoryStream</title>
    <link>http://www.hutteman.com/weblog/cat_blogging.html</link>
    <description>Get a complete rss feed (all categories) at &lt;a href="http://www.hutteman.com/weblog/rss.xml"&gt;http://www.hutteman.com/weblog/rss.xml&lt;/a&gt;</description>
    <dc:language>en-us</dc:language>
    <dc:creator>luke@hutteman.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2006-03-17T22:28:21-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.33" />
    <admin:errorReportsTo rdf:resource="mailto:luke@hutteman.com"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
    

    <item>
      <title>Digg manipulation</title>
      <link>http://www.hutteman.com/weblog/2006/03/17-247.html</link>
      <description>Silicon Valley Sleuth reported this morning how several stories about Google buying Sun suspiciously made it to the front page of Digg.com. These &quot;baseless rumours&quot; were all submitted and promoted by a small group of Digg members that seemed to be working together. I found this story through Digg itself, where it was posted on the front page. It later... (381 words)</description>
      <guid isPermaLink="false">247@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p><a href="http://www.siliconvalleysleuth.com/2006/03/digg_is_used_fo.html">Silicon Valley Sleuth</a> reported this morning how several stories about Google buying Sun suspiciously made it to the front page of <a href="http://www.digg.com">Digg.com</a>. These "baseless rumours" were all submitted and promoted by a small group of Digg members that seemed to be working together.
</p><p>
I found this story through <a href="http://www.digg.com/technology/Digg_is_used_for_Sun_stock_manipulation">Digg itself</a>, where it was posted on the front page. It later mysteriously disappeared from Digg though, and a <a href="http://www.digg.com/search?search=http%3A%2F%2Fwww.siliconvalleysleuth.com%2F2006%2F03%2Fdigg_is_used_fo.html&submit=Search&area=all&type=both&age=60&search-buried=on">URL search</a> indicated that the story was since marked as "buried".
</p><p>
<a href="http://diggtheblog.blogspot.com/2006/02/small-update.html">The Digg Blog</a> says the following about this burying feature:
</p>
<blockquote>
Digg now allows logged in users to bury stories as 'inaccurate'. Once enough people bury the story, it is removed from the queue and the following banner is displayed at the top:<br><br>
<img src="http://photos1.blogger.com/blogger/4139/1647/400/warning.jpg"><br><br>
</blockquote>
<p>
No banner is displayed though, which makes me wonder if it was buried because enough people marked it as inaccurate (the same people who were promoting these Google+Sun stories maybe?) or whether an admin removed it in an effort to hide how easily Digg can be manipulated. There's currently an update on Silicon Valley Sleuth stating that it seems unlikely the Digg system was actually manipulated in this case, but this update wasn't there when the story was buried, and also doesn't make the theoretical possibility of this happening any less likely.
</p><p>
Due to the automated nature of Digg (which uses user-votes to determine how prominently to display a story) it certainly seems possible for a group of people to get together and promote stories in order to get them onto the coveted front page, while at the same time burying stories they don't like. Worse than that, what would stop someone from automating this process and creating a couple hundred accounts for this purpose? To reduce suspicion, these accounts could digg random stories from time to time, or even undigg stories once they've made it to the front page.
</p><p>
If this is not going on already, I predict it will soon. Compared to the trouble BlogSpammers are going through in order to game sites like Google, DayPop or Blogdex, gaming Digg seems relatively easy. While Digg claims to <a href="http://www.businessweek.com/the_thread/blogspotting/archives/2006/03/digg_argues_it.html">have ways to prevent manipulation</a>, one can't help but wonder whether it's enough, and I'm sure there are plenty of spammers out there just dying to beat the system...
</p>]]></content:encoded>
              <category>Blogging</category>
      
      <dc:date>2006-03-17T22:28:21-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2006/03/17-247.html#comments</comments>
      
    </item>
    <item>
      <title>behold the power of the internet</title>
      <link>http://www.hutteman.com/weblog/2005/11/30-240.html</link>
      <description>where scammers live, their victims blog about it and digg their story, and lynchmobs form that barrage the vendor with prank calls, emails, faxes, ddos attacks and poor online ratings. All without anyone verifying whether there's any truth to the original story of course... UPDATE: Ed Lopez, owner of PriceRitePhoto sent an apology letter to Thomas Hawk. The next day,... (90 words)</description>
      <guid isPermaLink="false">240@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>where scammers live, their victims <a href="http://thomashawk.com/2005/11/priceritephoto-abusive-bait-and-switch.html">blog about it</a> and <a href="http://digg.com/deals/Abusive_New_York_Camera_Store_Threatens_Blogger">digg their story</a>, and lynchmobs form that barrage the vendor with prank calls, emails, faxes, ddos attacks and poor online ratings.</p>

<p>All without anyone verifying whether there's any truth to the original story of course...</p>

<p><b>UPDATE:</b> Ed Lopez, owner of PriceRitePhoto <a href="http://thomashawk.com/2005/12/apology-letter-from-ed-lopez-owner-of.html">sent an apology letter to Thomas Hawk</a>. The next day, Howard Baker, a manager with PriceRitePhoto, <a href="http://publications.mediapost.com/index.cfm?fuseaction=Articles.showArticleHomePage&art_aid=37019">says they suffered "millions of dollars" worth of damages, are talking to their attorneys, and will probably be taking legal action</a>.</p>]]></content:encoded>
              <category>Blogging</category>
      
      <dc:date>2005-11-30T22:06:08-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2005/11/30-240.html#comments</comments>
      
    </item>
    <item>
      <title>Outage problems</title>
      <link>http://www.hutteman.com/weblog/2005/10/23-234.html</link>
      <description>My hosting company ran into some issues this weekend that, besides causing a two day outage for both my blog and for sharpreader.net, also potentially caused some email to get lost. If you sent me anything on Friday, Saturday or Sunday, you may need to resend it - I'm not sure how much is lost for good and how much... (331 words)</description>
      <guid isPermaLink="false">234@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>My <a href="http://www.netrillium.com">hosting company</a> ran into <a href="http://helpdesk.netrilliumclients.com/?_a=announcements&_m=details&_i=16">some issues</a> this weekend that, besides causing a two day outage for both my blog and for <a href="http://www.sharpreader.net">sharpreader.net</a>, also potentially caused some email to get lost. If you sent me anything on Friday, Saturday or Sunday, you may need to resend it - I'm not sure how much is lost for good and how much will be redelivered later :-(</p>

<p>Also, if anyone has any positive experiences with hosting a 50+ Gb/month site at a reasonable price (I currently only pay $17/month), please let me know. This wasn't the first outage I've had, nor do I expect it to be the last. Maybe it's time to move on.</p>

<p><b>update:</b> looks like my hosting company still has some issues to be worked out; I can't send any emails through outlook for getting some weird "503 valid RCPT command must precede DATA" error (though sending through the web-based interface seems to work fine), and for some reason my movable type install is not showing any of your comments. Comments have not been lost though, as I can see them through the MT admin interface, and am also getting the email notifications (i'm actually getting those twice now... weird) - I just need to figure out why it's not rebuilding the pages correctly...</p>

<p><b>update 2:</b> email issue has been fixed - for some reason I had to use some outlook setting that wasn't needed before their servers crashed... now all I need is to figure out what's going on with MT...</p>

<p><b>update 3:</b> turned out that all comments were in a pending status and needed to be manually approved (the email notifications conveniently failed to mention this though). My <a href="http://www.jayallen.org/projects/mt-blacklist/">MT-Blacklist</a> was setup to only force moderation on old posts, but since the crash-recovery it now seems to force it on new ones as well. Oh well - I'm long overdue for an upgrade to <a href="http://www.sixapart.com/movabletype/news/2005/08/movable_type_3_2.html">MT 3.2</a> + SpamLookup anyway; guess it's time to stop procrastinating (but not tonight).</p>]]></content:encoded>
              <category>Blogging</category>
              <category>Miscellaneous</category>
              <category>SharpReader</category>
      
      <dc:date>2005-10-23T22:59:14-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2005/10/23-234.html#comments</comments>
      
    </item>
    <item>
      <title>MT Upgrade: lessons learned</title>
      <link>http://www.hutteman.com/weblog/2004/09/04-210.html</link>
      <description> FTP'ing many small files is sloooooow, so it's important you copy the right set (MT 3.11), instead of re-copying the existing version (MT 2.6) - oops ;-) To FTP files to your server, don't ever use WS_FTP again. The damn thing steals focus on every completed file, which made it almost impossible to do anything else during a large... (225 words)</description>
      <guid isPermaLink="false">210@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<ul>
<li>FTP'ing many small files is <i>sloooooow</i>, so it's important you copy the right set (<a href="http://www.movabletype.org/news/2004/08/movable_type_31_launched.shtml#001193">MT 3.11</a>), instead of re-copying the existing version (MT 2.6) - oops ;-)</li>
<li>To FTP files to your server, don't <i>ever</i> use WS_FTP again. The damn thing steals focus on every completed file, which made it almost impossible to do anything else during a large upload - including trying to find a replacement FTP app. I remembered Scott <a href="http://scottwater.com/blog/archive/2003/12/23/FTPSuggestions.aspx">blogging</a> about FTP apps a while ago, and settled on <a href="http://www.smartftp.com/">Smart FTP</a> based on the comments to that post. It sure works a whole lot better than WS_FTP (even though its "global queue" feature didn't seem to work for me).</li>
<li>To execute a cgi-script, chmod it to be executable first. I remembered this for the MT upgrade, but then forgot about it for the <a href="http://www.jayallen.org/projects/mt-blacklist/">MT-BlackList</a> upgrade. This made my server return some generic error-message when trying to run the MTB-upgrade script, which had me worried for a while since <a href="http://www.jayallen.org/journey/2004/08/the_good_the_bad_and_the_ugly">Jay's out this week</a>, and I didn't want to leave my blog wide open to comment and trackback spam for a week.</li>
<li>And last but certainly not least, don't start a major upgrade like this after midnight - it's way too easy to make stupid little mistakes when you're tired and sleepy, and once you start, there's no going back.</li>
</ul>
]]></content:encoded>
              <category>Blogging</category>
      
      <dc:date>2004-09-04T15:23:08-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2004/09/04-210.html#comments</comments>
      
    </item>
    <item>
      <title>Help Make Blogs More Visible!</title>
      <link>http://www.hutteman.com/weblog/2004/08/07-206.html</link>
      <description>There are by some estimates more than a million weblogs. But most of them get no visibility in search engines. Only a few &quot;A-List&quot; blogs get into the top search engine results for a given topic, while the majority of blogs just don't get noticed. The reason is that the smaller blogs don't have enough links pointing to them. But... (353 words)</description>
      <guid isPermaLink="false">206@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>There are by some estimates more than a million weblogs. But most of them get no visibility in search engines. Only a few "A-List" blogs get into the top search engine results for a given topic, while the majority of blogs just don't get noticed. The reason is that the smaller blogs don't have enough links pointing to them. But this posting could solve that. Let's help the smaller blogs get more visibility!</p>

<p>This posting is <a href="http://novaspivack.typepad.com/nova_spivacks_weblog/2004/08/what_is_a_gomem.html">GoMeme 4.0</a>. It is part of an experiment to see if we can create a blog posting that helps 1000's of blogs get higher rankings in Google. So far we have tried 3 earlier variations. Our first test, <a href="http://novaspivack.typepad.com/nova_spivacks_weblog/2004/08/a_sonar_ping_of.html">GoMeme 1.0</a>, spread to nearly 740 blogs in 2.5 days. This new version 4.0 is shorter, simpler, and fits more easily into your blog. </p>

<p>Why are we doing this? We want to help thousands of blogs get more visibility in Google and other search engines. How does it work? Just follow the instructions below to re-post this meme in your blog and add your URL to the end of the Path List below. As the meme spreads onwards from your blog, so will your URL. Later, when your blog is indexed by search engines, they will see the links pointing to your blog from all the downstream blogs that got this via you, which will cause them to rank your blog higher in search results. Everyone in the Path List below benefits in a similar way as this meme spreads. Try it! </p>

<p><b>Instructions:</b> Just copy this entire post and paste it into your blog. Then add your URL to the end of the path list below, and pass it on!  (Make sure you add your URLs as live links or HTML code to the Path List below.)</p>

<p><b><u>Path List</b></u><br />
1. <a href="http://www.mindingtheplanet.net">Minding the Planet</a><br />
2. <a href="http://www.hutteman.com/weblog/">Luke Hutteman's public virtual MemoryStream</a><br />
3. (your URL goes here! But first, please copy this line and move it down to the next line for the next person).</p>

<p><br />
(NOTE: Be sure you paste live links for the Path List or use HTML code.)<br />
</p>
]]></content:encoded>
              <category>Blogging</category>
      
      <dc:date>2004-08-07T13:28:55-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2004/08/07-206.html#comments</comments>
      
    </item>


  </channel>
</rss>
