<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="/layout/rss.xsl" media="screen"?>
<!-- generator="blogHi!/1.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
>

<channel>
	<title>blogHi! development</title>
	<link>http://dev.bloghi.com/</link>
	<description>blogHi! internal development log</description>
	<pubDate>Fri, 20 Nov 2009 22:32:28 +0000</pubDate>
	<generator>http://bloghi.com/</generator>
	<image>
		<url>http://dev.bloghi.com/img_ch.hi?id=1</url>
		<title>blogHi! development</title>
		<link>http://dev.bloghi.com/</link>
	</image>

	<item>
		<title>adsense rotation algorithm</title>
		<link>http://dev.bloghi.com/2006/09/26/adsense-rotation-algorithm.html</link>
		<comments>http://dev.bloghi.com/2006/09/26/adsense-rotation-algorithm.html#comments</comments>
		<pubDate>Tue, 26 Sep 2006 13:20:18 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/09/26/adsense-rotation-algorithm.html</guid>
		<description> We have just implemented a rotation algorithm for the google adsense box. Until now, you had these options within the google adsense module:make it go away, by saving &quot;clean&quot; in the google admin panel.leaving the box empty, and letting blogHi profit...</description>
		<content:encoded><![CDATA[We have just implemented a rotation algorithm for the <a href="http://dev.bloghi.com/2005/06/30/new-blog-integration-google-adsense-box.html">google adsense box.</a> Until now, you had these options within the google adsense module:<br><ul><li>make it go away, by saving "clean" in the <a href="http://bloghi.com/blog/manage/modules">google admin panel</a>.<br></li><li>leaving the box empty, and letting blogHi profit from the traffic that your blog generates.</li><li>filling the box with your own adsense id. <span style="color: rgb(0, 102, 0); font-weight: bold;">Here</span> we implemented a small change:<br></li></ul>At a random rate of 1/5, or 20%, instead of the google_ad_client that is set by you, the blogHi's google_ad_client will appear. This move comes in on a global scale,&nbsp; and also affects the adsense box present <a href="http://dev.bloghi.com/2006/02/24/new-adsense-placement-towards-website-costs.html">in the post</a>. Therefore, as a compensation, this box no longer runs the blogHi adwords code, but also your own. <br><br>Please let us know if you experience problems with this change,<br>yours blogHi.com<br>

]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/09/26/adsense-rotation-algorithm.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>running server upgrade</title>
		<link>http://dev.bloghi.com/2006/09/20/running-server-upgrade.html</link>
		<comments>http://dev.bloghi.com/2006/09/20/running-server-upgrade.html#comments</comments>
		<pubDate>Wed, 20 Sep 2006 11:09:08 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/09/20/running-server-upgrade.html</guid>
		<description> The hardware upgrade is about to be performed. The steps are as follows:current server is made &quot;read only&quot; (no more new posts, comments, settings etc).latest data is copied over to the new server.the domain name bloghi.com points over to the new...</description>
		<content:encoded><![CDATA[The <a href="http://dev.bloghi.com/2006/09/19/interruptions-of-servuce-because-of-server-upgrade.html">hardware upgrade</a> is about to be performed. The steps are as follows:<br><ol><li>current server is made "read only" (no more new posts, comments, settings etc).</li><li>latest data is copied over to the new server.</li><li>the domain name bloghi.com points over to the new server</li><li>the new server is opened to the public <br></li></ol>These are the upgrade steps, and we will inform you as we progress.<br>]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/09/20/running-server-upgrade.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>interruptions of servuce because of server upgrade</title>
		<link>http://dev.bloghi.com/2006/09/19/interruptions-of-servuce-because-of-server-upgrade.html</link>
		<comments>http://dev.bloghi.com/2006/09/19/interruptions-of-servuce-because-of-server-upgrade.html#comments</comments>
		<pubDate>Tue, 19 Sep 2006 01:31:42 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/09/19/interruptions-of-servuce-because-of-server-upgrade.html</guid>
		<description> We had a temporary problem this morning with the domain name transfer, which is solved for the main domain, we're working on restoring the blogs now.We plan to run a server upgrade later on today, and there might be small interruptions of service. We...</description>
		<content:encoded><![CDATA[We had a temporary problem this morning with the domain name transfer, which is solved for the main domain, we're working on restoring the blogs now.<br>We plan to run a server upgrade later on today, and there might be small interruptions of service. We have to transfer data to the new machine, then restore the services one by one. The total delay should be less than 15 minutes.<br>

]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/09/19/interruptions-of-servuce-because-of-server-upgrade.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>youtube and google video integration</title>
		<link>http://dev.bloghi.com/2006/09/02/youtube-and-google-video-integration.html</link>
		<comments>http://dev.bloghi.com/2006/09/02/youtube-and-google-video-integration.html#comments</comments>
		<pubDate>Sat, 02 Sep 2006 12:43:46 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/09/02/youtube-and-google-video-integration.html</guid>
		<description> 
   As recently requested, you have now the ability to&amp;nbsp; integrate&amp;nbsp; videos from youtube and google video into your posts. Youtube integration: Just place an opening bracket, then youtube=, then the youtube URL (the one from the browser...</description>
		<content:encoded><![CDATA[
   As recently requested, you have now the ability to&nbsp; integrate&nbsp; videos from <a href="http://www.youtube.com/">youtube</a> and <a href="http://video.google.com/">google video</a> into your posts. <br><br><span style="font-weight: bold;">Youtube</span> integration: Just place an opening bracket, then youtube=, then the youtube URL (the one from the browser address), then a closing bracket into your post editor. (see the example below the video box)<br><br>[youtube=http://www.youtube.com/watch?v=iHztbHP6oNo]<br><br>[youtube=http://www.youtube.com/watch?v=iHztbHP6oNo]<br><br>and <span style="font-weight: bold;">google video</span>: Just place an opening bracket, then googlevideo=, then the google video URL (the one from the browser address), then a closing bracket into your post editor. (see the example below the video box)<br><br>[googlevideo=http://video.google.com/videoplay?docid=953248532858975298]<br><br>[googlevideo=http://video.google.com/videoplay?docid=953248532858975298]<br><br>Because of flash integration, the posts containing these videos might load a bit slower. The integration is compatible with wordpress.com's <a href="http://wordpress.com/blog/2006/01/26/youtube-support/">youtube</a> and <a href="http://wordpress.com/blog/2006/02/06/google-video/">google video</a>, therefore your eventual transition there will remain easy<img src="/images/smilies/phpbb/icon_cool.gif" alt="cool" title="cool"> . Please let us know if you experience problems with this integration. <br><span style="font-style: italic;"><br>yours,</span><br style="font-style: italic;"><span style="font-style: italic;">blogHi.com</span>&nbsp;     
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/09/02/youtube-and-google-video-integration.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>blogHi doesn't close anymore!</title>
		<link>http://dev.bloghi.com/2006/09/01/bloghi-doesn-t-close-anymore.html</link>
		<comments>http://dev.bloghi.com/2006/09/01/bloghi-doesn-t-close-anymore.html#comments</comments>
		<pubDate>Fri, 01 Sep 2006 08:00:02 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/09/01/bloghi-doesn-t-close-anymore.html</guid>
		<description> 
  I made some posts announcing a possible closure of blogHi in November, then declared for sure that blogHi will close. Meanwhile, your community support encouraged me, and I also received some private buying offers. This led me thinking that it...</description>
		<content:encoded><![CDATA[
  I made some posts announcing a <a href="http://dev.bloghi.com/2006/08/09/04-nov-2006-bloghi-com-deadline.html">possible closure</a> of blogHi in November, then declared for sure that blogHi will close. Meanwhile, your community support encouraged me, and I also received some private buying offers. This led me thinking that it would be possible and more than welcomed for you that somebody else owns blogHi and takes this platform further.<br><br>In about 20 days blogHi will therefore just change ownership and I'm now looking for a suitable future owner via a <a href="http://www.sitepoint.com/marketplace/auction/1212?">sitepoint auction</a>. Therefore blogHi is here to stay, and your blogs <span style="font-weight: bold;">are safe here</span>, and I am sorry about the trouble that I took you through.<br><br><span style="font-style: italic;">yours,</span><br style="font-style: italic;"><span style="font-style: italic;">blogHi.com</span><br style="font-style: italic;">    
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/09/01/bloghi-doesn-t-close-anymore.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>migration guide to a WordPress blog</title>
		<link>http://dev.bloghi.com/2006/08/14/migration-guide-to-a-wordpress-blog.html</link>
		<comments>http://dev.bloghi.com/2006/08/14/migration-guide-to-a-wordpress-blog.html#comments</comments>
		<pubDate>Mon, 14 Aug 2006 13:41:53 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/08/14/migration-guide-to-a-wordpress-blog.html</guid>
		<description> 
Update: blogHi stays open. However this feature remains implemented; if you ever need it.Since we are about to close in less than three months, here is a guide in migrating your blog to a WordPress blog. 1. Open a WordPress blog, either via the...</description>
		<content:encoded><![CDATA[
<img style="width: 313px; height: 138px;" src="http://img116.imageshack.us/img116/4120/wordpressxmlfeedcv3.gif" alt="http://img116.imageshack.us/img116/4120/wordpressxmlfeedcv3.gif" title="http://img116.imageshack.us/img116/4120/wordpressxmlfeedcv3.gif" align="right" border="0"><span style="font-weight: bold;">Update:</span> <a href="http://dev.bloghi.com/2006/09/01/bloghi-doesn-t-close-anymore.html">blogHi stays open</a>. However this feature remains implemented; if you ever need it.<br><br>Since we are about to close in less than three months, here is a guide in migrating your blog to a <a href="http://en.wikipedia.org/wiki/Wordpress">WordPress</a> blog. <br><br>1. Open a WordPress blog, either via the popular <a href="http://wordpress.com">wordpress.com</a>, or via a hosted solution.<br>2. Go to your blogHi control panel, into the <a href="http://bloghi.com/blog/manage/syndication">Syndication section</a>, there you will notice a new column called WordPress XML Feed. You can either open the document (it is a XML file) and then save it, or chose to save it locally to your hard-disk (via right clicking on the link then chosing Save). Downloading this file can take a long time, since this is a full backup of your blog and comments.<br>3. Go to Manage/Import section in your fresh new wordpress blog, and select the local file that you just downloaded. Importing it will also take a while if you used to run a big blog, so please be patient.<br><br>Your wonderful blogging skills and the WordPress blog hosting will make a great combination!<br><br><br>  
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/08/14/migration-guide-to-a-wordpress-blog.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>04-Nov-2006 - blogHi.com deadline</title>
		<link>http://dev.bloghi.com/2006/08/09/04-nov-2006-bloghi-com-deadline.html</link>
		<comments>http://dev.bloghi.com/2006/08/09/04-nov-2006-bloghi-com-deadline.html#comments</comments>
		<pubDate>Wed, 09 Aug 2006 11:21:48 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/08/09/04-nov-2006-bloghi-com-deadline.html</guid>
		<description> 
        	 	 	 	 	 	  Dear blogHi community,  This post is about an imminent closure of blogHi, please read it. I have just received an e-mail from a new user, trying to explain something that puzzles most blog hosting websites out there: why most...</description>
		<content:encoded><![CDATA[
        	 	 	 	 	 	  <p style="margin-bottom: 0in;">Dear blogHi community,</p>  <p style="margin-bottom: 0in;">This post is about an <b>imminent closure</b> of blogHi, please read it.<br></p> <p style="margin-bottom: 0in;">I have just received an e-mail from a new user, trying to explain something that puzzles most blog hosting websites out there: why most people abandon their blog in the first days after opening it:</p>  <p style="margin-bottom: 0in;">“<i>My opinion most people abandon the blog before they use it is simply because they can't figure out what how to operate it.. I am ome of rhem...” </i><span style="font-style: normal;">(thank you, Frank for your message!)</span></p>  <p style="margin-bottom: 0in;">This led me thinking how much would blogHi benefit from a clean and simple wiki (<a href="http://en.wikipedia.org/wiki/Wiki">http://en.wikipedia.org/wiki/Wiki</a>), and how much sense would it make to create one. Then  I thought again that I won't probably have the time to install this wiki, and more important maintain it. And this is a real pity. In fact there are so many things that the community could benefit from, and it's a real pity that I am not doing anything about it. All in all this is a lack of service to you, the blogHi community, and it's not something that I am proud of.  </p>   <p style="margin-bottom: 0in;">some monetary aspects now:<br><br>On the 4th of November, blogHi will be 2 years old. It has operational costs of around $300 per month. Until now, the website operational costs were covered in the range of 40-50% by adsense, and the rest comes from my personal pocket (in the hope that the website will become profitable). If by that date I still won't be able to cover the operational costs of the website, the website will have to be shut down.</p>  <p style="margin-bottom: 0in;">I'm also considering selling the whole website, but I have no time to launch in complex<a href="http://www.google.com/search?q=blogexplosion+sale"> blogexplosion-like  sales</a>. I'm open to ideas here. Actually, I am open to any kind of ideas. To be honest, I hate as much as you do the deadline-tone of this post.<br></p>  <p style="margin-bottom: 0in;">If you want to host your blog somewhere else, please use the RSS feeds to move your blog away. If you need some special construct to transfer your posts and <br>comments, please contact us.<br></p><p style="margin-bottom: 0in;">It has been great to have you guys here! Thank you for chosing blogHi!<br></p><p style="margin-bottom: 0in;">Calin<br>blogHi.com<br><br> </p>      
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/08/09/04-nov-2006-bloghi-com-deadline.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>deleted comment posts</title>
		<link>http://dev.bloghi.com/2006/08/02/deleted-comment-posts.html</link>
		<comments>http://dev.bloghi.com/2006/08/02/deleted-comment-posts.html#comments</comments>
		<pubDate>Wed, 02 Aug 2006 14:26:43 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/08/02/deleted-comment-posts.html</guid>
		<description> During one of our rutine SPAM comments check, we accidentally removed some legitimate comments from the blogs hosted with us. We are working on restoring these comments back to life from our daily backups. If however some comments are still not...</description>
		<content:encoded><![CDATA[During one of our rutine SPAM comments check, we accidentally removed some legitimate comments from the blogs hosted with us. We are working on restoring these comments back to life from our daily backups. If however some comments are still not present after our restore procedures, this means they are lost (they came in after the daily backup was done). In such a case, restoring these comments is impossible. <br><br>If this is the case, we're sorry for the inconvenience this might have caused to you.<br><br><span style="font-style: italic;">yours,</span><br style="font-style: italic;"><span style="font-style: italic;">blogHi.com</span><br style="font-style: italic;">

]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/08/02/deleted-comment-posts.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>ban comments by IP address</title>
		<link>http://dev.bloghi.com/2006/06/26/ban-comments-by-ip-address.html</link>
		<comments>http://dev.bloghi.com/2006/06/26/ban-comments-by-ip-address.html#comments</comments>
		<pubDate>Mon, 26 Jun 2006 13:57:16 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/06/26/ban-comments-by-ip-address.html</guid>
		<description> 
   Banning by IP address: A new commenting feature awaits you in your blog control panel: A banned IP addresses field allows you to ban multiple persons that left comments in your blog from further commenting. You can get to this field by either...</description>
		<content:encoded><![CDATA[
   Banning by <a href="http://en.wikipedia.org/wiki/IP_address">IP address</a>: <br><br><img src="http://img413.imageshack.us/img413/1282/ipban3cr.jpg" alt="http://img413.imageshack.us/img413/1282/ipban3cr.jpg" title="http://img413.imageshack.us/img413/1282/ipban3cr.jpg" align="right" border="0">A new commenting feature awaits you in your blog control panel: A banned IP addresses field allows you to ban multiple persons that left comments in your blog from further commenting. You can get to this field by either visiting your <a href="http://bloghi.com/blog/edit">posts edit</a> section, then click on the link to the comments to a certain post, and then click on the ban list, as you can see in the image. Another way is to visit your <a href="http://bloghi.com/blog/manage/comments">comments control panel</a>, and edit the IP addresses field by yourself. Your new comment e-mail notifications already contain an anonymized comment author IP address that you can use for the banning list.<br><br>If you prefer to control the IPs manually, please place there comma separated IP addresses, in the format: 111.222.333.444, or 111.222.333.XXX, or just 111.222.333     
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/06/26/ban-comments-by-ip-address.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>server downtime</title>
		<link>http://dev.bloghi.com/2006/06/12/server-downtime.html</link>
		<comments>http://dev.bloghi.com/2006/06/12/server-downtime.html#comments</comments>
		<pubDate>Mon, 12 Jun 2006 10:55:08 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/06/12/server-downtime.html</guid>
		<description> We had some server ups and downs this morning for about 12 hours, these issues are solved now.                                                                                                                                                            </description>
		<content:encoded><![CDATA[We had some server ups and downs this morning for about 12 hours, these issues are solved now.]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/06/12/server-downtime.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>system stability issues</title>
		<link>http://dev.bloghi.com/2006/05/02/system-stability-issues.html</link>
		<comments>http://dev.bloghi.com/2006/05/02/system-stability-issues.html#comments</comments>
		<pubDate>Tue, 02 May 2006 09:57:01 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/05/02/system-stability-issues.html</guid>
		<description> As you all know we have experienced repeated downtimes latelly, and they are mostly related to current hardware limits and buggy database queries. During the last weeks we gathered knowledge why these downtimes occured, and hopefully we have found...</description>
		<content:encoded><![CDATA[As you all know we have experienced repeated downtimes latelly, and they are mostly related to current hardware limits and buggy database queries. During the last weeks we gathered knowledge why these downtimes occured, and hopefully we have found the right fixes. Thank you for your patience<br><br><span style="font-style: italic; color: rgb(102, 102, 102);">your blogHi.com</span><br>]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/05/02/system-stability-issues.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>tags cloud</title>
		<link>http://dev.bloghi.com/2006/03/06/tags-cloud.html</link>
		<comments>http://dev.bloghi.com/2006/03/06/tags-cloud.html#comments</comments>
		<pubDate>Mon, 06 Mar 2006 13:56:13 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/03/06/tags-cloud.html</guid>
		<description> 
 You can use post tags for a while now to mark relevant tags and keywords related to your posts. Once you start assigning tags, they pile up a categorization structure for your blog; which in time helps eventual visitors classify your blog in an...</description>
		<content:encoded><![CDATA[
<a href="http://en.wikipedia.org/wiki/Tag_cloud"><img src="http://upload.wikimedia.org/wikipedia/en/thumb/a/a7/Flickr_Tag_Cloud.gif/200px-Flickr_Tag_Cloud.gif" alt="tag cloud" title="tag cloud" align="right" border="0"></a> You can use <a href="http://help.bloghi.com/2005/11/21/what-are-post-tags.html">post tags</a> for a while now to mark relevant tags and keywords related to your posts. Once you start assigning tags, they pile up a categorization structure for your blog; which in time helps eventual visitors classify your blog in an instant. These tags are also present in your RSS feed; which means increased chances to be found using keyword searches. We launched a new blog feature called <span style="font-weight: bold;">tags cloud</span>; here is the detailed <a href="http://en.wikipedia.org/wiki/Tag_cloud">wikipedia explanation</a>. The more tags you assign to your posts, the more proeminent this tag will be in your blog tags cloud.<br><br>If you use a customized blog menu template, in order to enable this feature you should add this code to your template:<br><br>&nbsp;&nbsp;&nbsp;&nbsp; &lt;li id="links"&gt;<br>&lt;!-- Tag cloud --&gt;<br>&nbsp;&nbsp;&nbsp; &lt;/li&gt;<br><br>An example can be found <a href="http://php9.bloghi.com/">here</a>. This is enabled by default, but (as always) you can remove it anytime from your <a href="http://bloghi.com/blog/manage/template">blog menu template</a>.<br><span id="gtbmisp_0" style="border: 0pt none ; margin: 0pt; padding: 0pt; background: transparent none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: bold; font-size: 100%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: static; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: red; text-decoration: underline; cursor: pointer;"></span> <div style="border: 0pt none ; margin: 2px 0px; padding: 0pt; background: rgb(195, 217, 255) none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 100%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: absolute; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: rgb(0, 0, 0); text-decoration: none; cursor: default; z-index: 2147483647; left: 343px; top: 35px; display: none;" id="gtbspellmenu_0"><span style="border: 0pt none ; margin: 0pt; padding: 0pt; background: transparent none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 90%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: static; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: rgb(0, 0, 0); text-decoration: none; cursor: pointer;">asdasd</span><br><span id="gtbspellmenu_edit_0" style="border: 0pt none ; margin: 0pt; padding: 0pt; background: transparent none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 90%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: static; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: rgb(0, 0, 0); text-decoration: none; cursor: pointer;">Edit...</span><br><span id="gtbspellmenu_ignoreall_0" style="border: 0pt none ; margin: 0pt; padding: 0pt; background: transparent none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 90%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: static; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: rgb(0, 0, 0); text-decoration: none; cursor: pointer;">Ignore all</span><br><span id="gtbspellmenu_dictadd_0" style="border: 0pt none ; margin: 0pt; padding: 0pt; background: transparent none repeat scroll 0% 50%; font-family: serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 90%; line-height: normal; font-size-adjust: none; font-stretch: normal; position: static; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; text-align: left; text-indent: 0pt; text-transform: none; color: rgb(0, 0, 0); text-decoration: none; cursor: pointer;">Add to dictionary</span></div>
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/03/06/tags-cloud.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>new adsense placement towards website costs.</title>
		<link>http://dev.bloghi.com/2006/02/24/new-adsense-placement-towards-website-costs.html</link>
		<comments>http://dev.bloghi.com/2006/02/24/new-adsense-placement-towards-website-costs.html#comments</comments>
		<pubDate>Fri, 24 Feb 2006 10:54:11 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/02/24/new-adsense-placement-towards-website-costs.html</guid>
		<description> 
 Your blogs become more and more popular each day. This is great news for you, but for us, as the blog hosting company powering your blogs, this means more and more traffic directed to our servers. You might have noticed that we've been playing...</description>
		<content:encoded><![CDATA[
 Your blogs become more and more popular each day. This is great news for you, but for us, as the blog hosting company powering your blogs, this means more and more traffic directed to our servers. You might have noticed that we've been playing around with the latest comments module, enabling and disabling it in order to enhance overall performance.<br><br>There's a new adsense placement test; inside the post. Since our small company goes in minus every month (expenses exceed revenues); please allow this new placement. We hope that it will make a difference. Also, please consider <a href="http://bloghi.com/donate">donating to us</a> in order to keep this free blog hosting service operational.<br><br>Yours,<br>blogHi.com<br>   
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/02/24/new-adsense-placement-towards-website-costs.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>cute, easy to use poll boxes in your posts</title>
		<link>http://dev.bloghi.com/2006/02/16/cute-easy-to-use-poll-boxes-in-your-posts.html</link>
		<comments>http://dev.bloghi.com/2006/02/16/cute-easy-to-use-poll-boxes-in-your-posts.html#comments</comments>
		<pubDate>Thu, 16 Feb 2006 14:27:44 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/02/16/cute-easy-to-use-poll-boxes-in-your-posts.html</guid>
		<description> You can create polls for your blog. In your post management too, near the smileys icon, there's a new dPoll icon; once clicked, it leads you through a light one-time registration process by dPolls.com; and then lets you easily paste nice looking...</description>
		<content:encoded><![CDATA[<P><IFRAME src="http://www.dpolls.com/DisplayPoll.aspx?PollID=2326" frameBorder=0 width=250 scrolling=no height=150 allowTransparency></IFRAME><BR><A title="Create polls and vote for free. dPolls.com" href="http://www.dpolls.com/" target=_blank><IMG alt="Create polls and vote for free. dPolls.com" src="http://www.dpolls.com/dPollsLink.aspx" border=0></A><BR><BR><FONT size=4><FONT size=2>You can create polls for your blog. In your post management too, near the smileys icon, there's a new dPoll icon; once clicked, it leads you through a light one-time registration process by </FONT><A href="http://dpolls.com/"><FONT size=2>dPolls.com</FONT></A><FONT size=2>; and then lets you easily paste nice looking polls directly in your post. If you copy the dPolls.com code; you can also paste it in your blog </FONT><A href="http://bloghi.com/blog/manage/template"><FONT size=2>menu template</FONT></A><FONT size=2>.</FONT><BR></FONT><FONT size=4></FONT></P>
<P><FONT size=4>Polls quick summary:</FONT><BR></P>
<UL>
<LI>Create polls for your blog in less than 3 minutes! 
<LI>Get opinions from your blog readers about any subject you wish to. 
<LI>Keep the users in your blog, with refresh-free, Ajax powered poll box. 
<LI>Use an integrated 4 step quick and easy poll creation wizard. 
<LI>Do daily polls, weekly polls,monthly polls or even longer. 
<LI>You can choose to include the poll in dPolls polls repository, and get opinions from dPolls site users too.</LI></UL><FONT size=4>A few tips:</FONT><BR>
<UL>
<LI>Click on a poll question to get the poll details and statistics page. 
<LI>Hover your mouse over a question or answer to make it scroll sideways automaticly if its too long. 
<LI>If the poll has more than 4 answers, use the right scroll arrows to see the other answers. 
<LI>Hover your mouse over the answers results bars to see how many people voted for each answer. 
<LI>Check out the poll's page for related polls and maintenance options.</LI></UL>enjoy!<BR>yours, blogHi.com<BR>]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/02/16/cute-easy-to-use-poll-boxes-in-your-posts.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>threaded comments</title>
		<link>http://dev.bloghi.com/2006/02/09/threaded-comments.html</link>
		<comments>http://dev.bloghi.com/2006/02/09/threaded-comments.html#comments</comments>
		<pubDate>Thu, 09 Feb 2006 13:19:51 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/02/09/threaded-comments.html</guid>
		<description> Since commenting seems to be a popular feature used by your blog visitory; there's a new enhancement to it: threaded comments. Near each comment there's a new link which says (Reply); once clicked, the visitor will be able to reply to that particular...</description>
		<content:encoded><![CDATA[Since commenting seems to be a popular feature used by your blog visitory; there's a new enhancement to it: threaded comments. Near each comment there's a new link which says (<span style="color: rgb(51, 51, 255); text-decoration: underline;">Reply</span>); once clicked, the visitor will be able to reply to that particular comment from the comments list. <br><br>Then, by the time the comments are displayed, if there are replies to certain comments, these replies are displayed below the comment they replied to; so that one can easier follow comment threads. The display hierarchy is a tree style; this tree is also present in the Reply to selection box.<br>


<br>As I read this brief introduction; it sounds really complicated. The feature itself should be pretty self-explanatory though.&nbsp;]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/02/09/threaded-comments.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>new blog feature: trackback pings</title>
		<link>http://dev.bloghi.com/2006/01/11/new-blog-feature-trackback-pings.html</link>
		<comments>http://dev.bloghi.com/2006/01/11/new-blog-feature-trackback-pings.html#comments</comments>
		<pubDate>Wed, 11 Jan 2006 13:47:15 +0000</pubDate>
		<guid>http://dev.bloghi.com/2006/01/11/new-blog-feature-trackback-pings.html</guid>
		<description> We implemented the trackback feature (wiki, help) to your blogs. It is enabled by default, but can be taken off anytime under your blog comments management module. Put in simple words, this feature allows automatic comment posting from other blogs...</description>
		<content:encoded><![CDATA[We implemented the trackback feature (<a href="http://en.wikipedia.org/wiki/Trackback">wiki</a>, <a href="http://madskills.com/public/xml/rss/module/trackback/">help</a>) to your blogs. It is enabled by default, but can be taken off anytime under your blog <a href="http://bloghi.com/blog/manage/comments">comments management module</a>. Put in simple words, this feature allows automatic comment posting from other blogs that reference your posts.<br><br>The trackback feature closes itself after one week after a post has been published; therefore it's biased towards fresh content. There's also some pretty extensive checks involved; also anti-spam protection. Let us know your eventual problems with it.<br>

]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2006/01/11/new-blog-feature-trackback-pings.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>splog reports queue</title>
		<link>http://dev.bloghi.com/2005/12/24/splog-reports-queue.html</link>
		<comments>http://dev.bloghi.com/2005/12/24/splog-reports-queue.html#comments</comments>
		<pubDate>Sat, 24 Dec 2005 10:03:05 +0000</pubDate>
		<guid>http://dev.bloghi.com/2005/12/24/splog-reports-queue.html</guid>
		<description> 
This is just to announce the newest splogs removal queue; a webpage where you can check the current status of the blogs that were identified as SPAM blogs. The blogs that have more votes against them are in colored rows; therefore one can easily...</description>
		<content:encoded><![CDATA[
This is just to announce the newest <a href="http://bloghi.com/report/manage__reports">splogs removal queue</a>; a webpage where you can check the current status of the blogs that were identified as SPAM blogs. The blogs that have more votes against them are in colored rows; therefore one can easily spot the ones that were rejected by most blogHi members. As soon as your splog report is approved; the spam blog is frozen. You can ask for removal privileges by <a href="http://bloghi.com/contact">contacting us</a>.<br><br>Merry <a href="http://www.gotfuturama.com/Information/Encyc-87-Xmas/">x-mas</a> from the entire blogHi team.<br>  
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2005/12/24/splog-reports-queue.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>members can report spam blogs</title>
		<link>http://dev.bloghi.com/2005/12/22/members-can-report-spam-blogs.html</link>
		<comments>http://dev.bloghi.com/2005/12/22/members-can-report-spam-blogs.html#comments</comments>
		<pubDate>Thu, 22 Dec 2005 13:14:13 +0000</pubDate>
		<guid>http://dev.bloghi.com/2005/12/22/members-can-report-spam-blogs.html</guid>
		<description> 
We were recently flooded with SPAM blogs; from China and all around. It's a shame so many so called search engine optimization companies employ such dirty web techniques. These splogs (wikipedia: splog) affect not only the image of our small but...</description>
		<content:encoded><![CDATA[
<p>We were recently flooded with SPAM blogs; from China and all around. It's a shame so many so called search engine optimization companies employ such dirty web techniques. These splogs (<a href="http://en.wikipedia.org/wiki/Splog">wikipedia: splog</a>) affect not only the image of our small but fast growing blog hosting website, but also the blogging experience of older blogHi members. Therefore, at the request of a few helpful members, we&nbsp;roll out&nbsp;a new members-only feature on blogHi: the possibility to report SPAM blogs. </p> <p>Down the <a href="http://bloghi.com/dir">blogHi directory</a>, or in the <a href="http://bloghi.com/posts">latest posts list</a>, you will notice a small green link titled <font color="#009900"><strong>report</strong></font>. If you click on it, you are presented with a report page. At your wish, you can detail the reasons you find this blog doesn't deserve to be alive, and then click "Report Blog" to have your report sent to us.&nbsp;We monitor the reports queue, and react whenever you use this form.</p> <p>If your report is accepted, your action&nbsp;improves your member karma, which will most likely be used as a criteria to sort member blogs. We thank Mark for the idea, and all other members for all their help.</p>
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2005/12/22/members-can-report-spam-blogs.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>cheap spam around</title>
		<link>http://dev.bloghi.com/2005/11/25/cheap-spam-around.html</link>
		<comments>http://dev.bloghi.com/2005/11/25/cheap-spam-around.html#comments</comments>
		<pubDate>Fri, 25 Nov 2005 07:32:11 +0000</pubDate>
		<guid>http://dev.bloghi.com/2005/11/25/cheap-spam-around.html</guid>
		<description> 
 The cheap spammer infecting blogs here with advertisment for &quot;Buy WoW Gold&quot; will have his blog deleted. As well all the spamming comments he&amp;nbsp; spread around will be wiped out. Please let us know if you encounter such behaviour in the...</description>
		<content:encoded><![CDATA[
 The cheap spammer infecting blogs here with advertisment for "Buy WoW Gold" will have his blog deleted. As well all the spamming comments he&nbsp; spread around will be wiped out. Please <a href="http://bloghi.com/contact">let us know</a> if you encounter such behaviour in the future.<br><span style="font-weight: bold;">Updated:</span> we deleted that person's account and blog. Any blogHi user that tries to spread spam into other blogs will suffer the same consequences.<br>   
]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2005/11/25/cheap-spam-around.html#comments</wfw:commentRSS>
	</item>
	<item>
		<title>a few site updates</title>
		<link>http://dev.bloghi.com/2005/11/24/a-few-site-updates.html</link>
		<comments>http://dev.bloghi.com/2005/11/24/a-few-site-updates.html#comments</comments>
		<pubDate>Thu, 24 Nov 2005 13:00:38 +0000</pubDate>
		<guid>http://dev.bloghi.com/2005/11/24/a-few-site-updates.html</guid>
		<description> We introduced a spell checked button in the toolbar; hopefully we will make less typing mistakes . Unfortunatelly the spell check works only with Internet Explorer, but it's implemented with an open source speller, and the library could be ported to...</description>
		<content:encoded><![CDATA[We introduced a spell checked button in the toolbar; hopefully we will make less typing mistakes <IMG title=eusa_shhh alt=eusa_shhh src="/images/smilies/eusasmiles/eusa_shhh.gif">. Unfortunatelly the spell check works only with Internet Explorer, but it's implemented with an open source speller, and the library could be ported to other browsers in the future. There are also a few smileys packages there. Let us know if you need some more of these. <IMG title=http://img174.imageshack.us/img174/3411/toolbar4hc.jpg alt=http://img174.imageshack.us/img174/3411/toolbar4hc.jpg src="http://img174.imageshack.us/img174/3411/toolbar4hc.jpg" align=right border=0><BR>On the comments level, we also introduced an opt-in checkbox for users outside of blogHi, as well as an opt-out for blogHi members. We created this in order to avoid eventual SPAM complaints, since e-mail is such a sensitive issue.<BR>]]></content:encoded>
		<wfw:commentRSS>http://dev.bloghi.com/2005/11/24/a-few-site-updates.html#comments</wfw:commentRSS>
	</item>
</channel>
</rss>