<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HYVIEW</title>
	<atom:link href="http://hyview.ilotus.org/bsite/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://hyview.ilotus.org/bsite</link>
	<description>Seeing Beyond</description>
	<lastBuildDate>Fri, 14 Oct 2011 13:02:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>WordPress Language Pack &#8211; Chinese, Traditional</title>
		<link>http://hyview.ilotus.org/bsite/?p=363</link>
		<comments>http://hyview.ilotus.org/bsite/?p=363#comments</comments>
		<pubDate>Fri, 14 Oct 2011 09:08:40 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[language pack]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=363</guid>
		<description><![CDATA[The PO file of Traditional Chinese: -&#62; Version: 2.9.2 -&#62; Version 3.2 &#160;]]></description>
			<content:encoded><![CDATA[<p>The PO file of Traditional Chinese:</p>
<p>-&gt; <a href="https://www.dropbox.com/s/mf88aey8u2ri6l5/zh_TW_v292.po.txt">Version: 2.9.2</a></p>
<p>-&gt; <a href="https://www.dropbox.com/s/lqxxgm1reaaj722/zh_TW_v32.po.txt">Version 3.2</a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=363</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress MU</title>
		<link>http://hyview.ilotus.org/bsite/?p=297</link>
		<comments>http://hyview.ilotus.org/bsite/?p=297#comments</comments>
		<pubDate>Wed, 23 Mar 2011 16:42:19 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=297</guid>
		<description><![CDATA[WordPress MU is no longer under active development as a separate product. Its features were rolled into core and released with WordPress 3.0. You can install WordPress and Create A Network instead. It functions generally the same. WordPress MU, or WordPressµ, is the multi-user version of WordPress. It is ideal for people who want to [...]]]></description>
			<content:encoded><![CDATA[<h4><span style="color: #ff0000;">WordPress MU is  no longer under active development as a separate product. Its features  were rolled into core and released with WordPress 3.0</span>. You can <a title="Installing WordPress" href="http://codex.wordpress.org/Installing_WordPress">install WordPress</a> and <a title="Create A Network" href="http://codex.wordpress.org/Create_A_Network">Create A Network</a> instead. It functions generally the same.</h4>
<p><a title="WPMU" href="http://codex.wordpress.org/WPMU">WordPress MU</a>,  or WordPressµ, is the multi-user version of WordPress. It is ideal for  people who want to set up a large network of blogs. WordPress MU is the  underlying software that powers the <a title="http://wordpress.com/" href="http://wordpress.com/">WordPress.com</a> hosted blogging service. WordPress MU is also used by newspapers,  magazines, blog networks, universities and large companies running  corporate blogging systems behind firewalls.</p>
<p>Using the WordPress multi-user edition, you will be able offer  users an opportunity to sign up for a new blog. They will be able to  securely manage their templates and settings without affecting any other  users. You can have unlimited users with unlimited blogs, and users can  have various roles (administrator, editor, author, contributor,  subscriber) on each other&#8217;s blogs. One or more Site Administrators can  perform site-wide management tasks, including adding users and blogs,  altering permissions and granting access to themes.</p>
<h3>WordPress MU Features</h3>
<p>WordPress MU Plugins and Themes are controlled by a central system  administrator. Unlike the single-user version of WordPress, individual  WPMU bloggers cannot upload their own WordPress Plugins and Themes. The  users can only select from the ones made available by the system  administrator. Individual themes can be made available to all blogs or  just to specific ones.</p>
<p><a id="WordPress_Mu_Host_Benefits" name="WordPress_Mu_Host_Benefits"></a></p>
<h4>WordPress Mu Host Benefits</h4>
<ul>
<li> Ability to create a hosted &#8220;community&#8221; of users.</li>
<li> Ability to host thousands of users on one site.</li>
<li> Opportunity to provide free hosting as an alternative to paid hosting services.</li>
<li> Ability to limit sign-up to specific email domains if required.</li>
<li> Various options for adding Plugins and administration features.</li>
<li> Customization of the administration panels.</li>
<li> Ability to add WordPress Themes, increasing user choices.</li>
<li> Ability to control WordPress Themes, limiting user choices per site needs.</li>
<li> Security precautions and protections in place.</li>
<li> Easy addition of comment spam protection through Plugins.</li>
</ul>
<p><a id="WordPress_MU_User_Benefits" name="WordPress_MU_User_Benefits"></a></p>
<h4>WordPress MU User Benefits</h4>
<p>While WordPress MU users are blogging with a restricted version of  WordPress, able to choose from WordPress Themes and Plugin options as  set by the Administrator, there are still a lot of benefits.</p>
<ul>
<li> No installation or setup. Enter user name and password and blog.</li>
<li> A chance to test drive WordPress at little or no risk.</li>
<li> Choose WordPress Themes that have been tested and are ready for use &#8211; no fuss, no muss.</li>
<li> Part of a community, with potential for community relationships through competition and awareness.</li>
<li> Comment spam protection built-in.</li>
</ul>
<p>WordPress MU is designed for hosts to offer hosting of WordPress  blogs to individual users. WordPress MU is free, as is the single hosted  version of <a title="http://www.wordpress.org/download" href="http://www.wordpress.org/download">WordPress</a>.</p>
<p><a id="WordPress_MU_Support_and_Installation" name="WordPress_MU_Support_and_Installation"></a></p>
<h3>WordPress MU Support and Installation</h3>
<p>For information on installing and setting up a WordPress MU site, see <a title="Installing WPMU" href="http://codex.wordpress.org/Installing_WPMU">Installing WPMU</a>.</p>
<p>For support and information on installing and using WordPress MU, visit the <a title="http://mu.wordpress.org" href="http://mu.wordpress.org/">WordPress MU</a> website and <a title="http://mu.wordpress.org/forums" href="http://mu.wordpress.org/forums">WordPress MU Support Forum</a>.</p>
<p>If you are a WordPress MU user click on the Feedback button in  your Dashboard.  Some help may be found within the WordPress Codex in  the articles listed on <a title="WPMU" href="http://codex.wordpress.org/WPMU">WPMU</a> or in <a title="http://donncha.wordpress.com/2005/09/23/wordpresscom-faq/" href="http://donncha.wordpress.com/2005/09/23/wordpresscom-faq/">Donncha&#8217;s FAQ</a>.</p>
<ul>
<li> There are some special <a title="WPMU Plugins" href="http://codex.wordpress.org/WPMU_Plugins">WPMU Plugins</a> and not all WordPress Plugins work with WPMU, see <a title="WPMU Plugin Compatibility" href="http://codex.wordpress.org/WPMU_Plugin_Compatibility">WPMU Plugin Compatibility</a></li>
<li> There are <a title="WPMU Functions" href="http://codex.wordpress.org/WPMU_Functions">WPMU Functions</a> and <a title="WPMU Global Variables" href="http://codex.wordpress.org/WPMU_Global_Variables">WPMU Global Variables</a> that should use to interact with WPMU&#8217;s multiuser features</li>
<li> WordPress Plugins and Widgets can be modified to become <a title="WPMU Widgets" href="http://codex.wordpress.org/WPMU_Widgets">WPMU Widgets</a>.</li>
<li> The code can be checked out from the <a title="WPMU SVN Repository" href="http://codex.wordpress.org/WPMU_SVN_Repository">WPMU SVN Repository</a>.</li>
<li> There is the <a title="WPMU IRC Channel" href="http://codex.wordpress.org/WPMU_IRC_Channel">WPMU IRC Channel</a> for real time help and chat.</li>
<li> Information is available about how the tables are set up in <a title="WPMU Database Description" href="http://codex.wordpress.org/WPMU_Database_Description">WPMU Database Description</a>.</li>
</ul>
<p>For more information, see the Codex Table of Contents for <a title="WPMU" href="http://codex.wordpress.org/WPMU">WPMU</a> or the <a title="Category:WPMU" href="http://codex.wordpress.org/Category:WPMU">Category:WPMU</a>.</p>
<p><a id="Other_Helpful_Resources" name="Other_Helpful_Resources"></a></p>
<h4>Other Helpful Resources</h4>
<ul>
<li> <a title="http://wordpress.org/development/" href="http://wordpress.org/development/">WordPress Development Blog &#8211; Information on WordPress in General</a></li>
<li> <a title="http://www.devlounge.net/articles/using-wordpress-mu-to-power-multiple-blogs" href="http://www.devlounge.net/articles/using-wordpress-mu-to-power-multiple-blogs">Using WordPress MU to Power Multiple Blogs</a> at DevLounge (13DEC07)</li>
<li><a title="http://mu.word-press.hu" href="http://mu.word-press.hu/">WordPress Mu Magyar Információs oldal (Hungarian)</a></li>
<li> <a title="http://wordpress.org/extend/plugins/tags/wpmu" href="http://wordpress.org/extend/plugins/tags/wpmu">Plugins for WordPress MU</a></li>
<li> <a title="http://wpmututorials.com/" href="http://wpmututorials.com/">WordPress MU tutorials and how-to articles</a></li>
</ul>
<p>Source: http://codex.wordpress.org/WordPress_MU</p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=297</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Multi Languages: 5 Plugins To Build A Multilingual Website</title>
		<link>http://hyview.ilotus.org/bsite/?p=295</link>
		<comments>http://hyview.ilotus.org/bsite/?p=295#comments</comments>
		<pubDate>Wed, 23 Mar 2011 16:29:06 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[Web Page Design]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=295</guid>
		<description><![CDATA[If you are using WordPress as a CMS, then you probably want to present your content with multiple languages. Recently, I came across a WordPress blog that presents their content with three different languages, so I decided to investigate the methods and plugins to turn WordPress into a multilingual website, and share my findings with [...]]]></description>
			<content:encoded><![CDATA[<p>If you are using <strong>WordPress as a CMS</strong>,  then you probably want to present your content with multiple languages.  Recently, I came across a WordPress blog that presents their content  with three different languages, so I decided to investigate the methods  and plugins to turn WordPress into a <strong>multilingual website</strong>, and share my findings with WDB’s readers.</p>
<p>Maintaining a multilingual website is not easy. The best way to  present multilingual content to your visitors is to allow them to switch  between different languages anytime. So, the plugin needs to take care  of this and links different languages’ content together.</p>
<p>Beside linking the content, the URL of the translated content also important. There are two different ways to present your URL:</p>
<ol>
<li> You can have the same permalink for the translated content, and add  a language flag at the end of the URL (ex:  www.domain.com/multi-language-article/?lang=en,  www.domain.com/multi-language-article/?lang=es,  www.domain.com/multi-language-article/?lang=zh).</li>
<li>The translated content will have absolutely different URL.</li>
</ol>
<p>So, how to choose your URL is yet another main consideration before  you launch the multilingual website? In SEO point of view, having an  absolutely different URL will gain better advantages Later on, we are  going to look into <strong>5 different plugins to manage your multilingual WordPress website</strong>. These plugins have their pros and cons, so choosing the best plugin that suit your needs in the most important.</p>
<h3>1. <a title="WPML" href="http://wpml.org/" target="_blank">WPML</a></h3>
<p>In my opinion, WPML is the most powerful WordPress multilingual  plugin. WPML has a complete startup guide for new users and its  side-wide navigation adds top navigation with drop down menus,  breadcrumbs trail navigation and also sidebar navigation. WPML is rather  too powerful for a simple multilingual website. You can have a lot of  options and configurations through the backend admin menu. Adding a  non-support language is not that easy. For example, when I tried to add a  language which is not supported by default, I need to go to my MySQL  backend and manually add in the SQL queries. Hopefully future version  will make this easier.<br />
<img src="http://images.webdesignbooth.com/wp-multilingual/wpml.jpg" alt="" width="500" height="316" /></p>
<h3>2. <a title="qTranslate" href="http://wordpress.org/extend/plugins/qtranslate/" target="_blank">qTranslate</a></h3>
<p>qTranslate is yet another powerful multi languages WordPress plugin.  It has advantages over WPML because it allows users to add new languages  to the system through the Simplistic Configuration Page. In terms of  URL structure, qTranslate provides three modes to make your URLs pretty  and SEO friendly:- everywhere compatible <strong>?lang=en</strong>, simple and beautiful <strong>/en/foo</strong> or nice and neat subdomain <strong>en.domain.com</strong>.<br />
<img src="http://images.webdesignbooth.com/wp-multilingual/qtranslate.jpg" alt="" width="500" height="440" /></p>
<h3>3. <a title="ZdMultiLang" href="http://wordpress.org/extend/plugins/zdmultilang/" target="_blank">ZdMultiLang</a></h3>
<p>You can define multiple languages and translate posts/tags/categories  using the interface that will be added to your blog’s administration  panel. Adding a new user-defined language is very simple through the  admin panel, but there are a couple of important things that you should  check before adding a new language. For example, the language code and  the language permalink. You can read more about this is the plugin  website.<br />
<img src="http://images.webdesignbooth.com/wp-multilingual/zdmultilang.jpg" alt="" width="500" height="352" /></p>
<h3>4. <a title="Language Switcher WordPress Plugin" href="http://www.poplarware.com/languageplugin.html" target="_blank">Language Switcher WordPress Plugin</a></h3>
<p>Setting up the language switcher plugin to work with your WordPress  site does take some work. The official website provides a very  comprehensive startup guide which covers installing, theme and plugin  modifications, translating and Q &amp; A.<br />
<img src="http://images.webdesignbooth.com/wp-multilingual/language-switcher-wordpress-plugin.jpg" alt="" width="500" height="320" /></p>
<h3>5. <a title="xLanguage" href="http://wordpress.org/extend/plugins/xlanguage/" target="_blank">xLanguage</a></h3>
<p>xLanguage is a full featured plugin which allows you to blog in  different language. It works for blog post, page, tags and categories.  xLanguage uses tags to differentiate different languages and serve the  content to the user based on their selected language.<br />
<img src="http://images.webdesignbooth.com/wp-multilingual/xlanguage.jpg" alt="" width="500" height="268" /></p>
<div><strong>Tags:</strong> <a rel="tag" href="http://www.webdesignbooth.com/tag/cms/">CMS</a>, <a rel="tag" href="http://www.webdesignbooth.com/tag/multi-languages/">multi languages</a>, <a rel="tag" href="http://www.webdesignbooth.com/tag/multilingual/">multilingual</a>, <a rel="tag" href="http://www.webdesignbooth.com/tag/translate/">translate</a><br />
<strong>Under:</strong> <a title="View all posts in WordPress" rel="category tag" href="http://www.webdesignbooth.com/category/wordpress/">WordPress</a></div>
<div></div>
<div>Source: http://www.webdesignbooth.com/wordpress-multi-languages-5-plugins-to-built-a-multilingual-website/</div>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=295</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>svn switch &#8211; change to new IP</title>
		<link>http://hyview.ilotus.org/bsite/?p=291</link>
		<comments>http://hyview.ilotus.org/bsite/?p=291#comments</comments>
		<pubDate>Tue, 08 Feb 2011 20:40:22 +0000</pubDate>
		<dc:creator>shawn</dc:creator>
				<category><![CDATA[How-to]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=291</guid>
		<description><![CDATA[Name svn switch — Update working copy to a different URL. Synopsis svn switch URL[@PEGREV] [PATH] switch --relocate FROM TO [PATH...] Description The first variant of this subcommand (without the --relocate option) updates your working copy to point to a new URL—usually a URL that shares a common ancestor with your working copy, although not [...]]]></description>
			<content:encoded><![CDATA[<div>
<h2>Name</h2>
<p>svn switch — Update working copy to a different URL.</p>
</div>
<div lang="en">
<h2>Synopsis</h2>
<pre>svn switch URL[@PEGREV] [PATH]</pre>
<pre>switch --relocate FROM TO [PATH...]</pre>
</div>
<div lang="en">
<h2>Description</h2>
<p>The first variant of this subcommand (without the             <code>--relocate</code> option) updates your working             copy to point to a new URL—usually a URL that             shares a common ancestor with your working copy, although             not necessarily.  This is the Subversion way to move a             working copy to a new branch.  If specified,             <em><code>PEGREV</code></em> determines in which             revision the target is first looked up.  See <a title="Traversing Branches" href="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.switchwc.html">the section called “Traversing Branches”</a> for an in-depth look             at switching.</p>
<p>If <code>--force</code> is used, unversioned             obstructing paths in the working copy do not automatically             cause a failure if the switch attempts to add the same             path.  If the obstructing path is the same type (file or             directory) as the corresponding path in the repository, it             becomes versioned but its contents are left untouched in             the working copy.  This means that an obstructing             directory&#8217;s unversioned children may also obstruct and             become versioned.  For files, any content differences             between the obstruction and the repository are treated             like a local modification to the working copy.  All             properties from the repository are applied to the             obstructing path.</p>
<p>As with most subcommands, you can limit the scope of             the switch operation to a particular tree depth using the             <code>--depth</code> option.  Alternatively, you can             use the <code>--set-depth</code> option to set a new             “sticky” working copy depth on the switch             target.  Currently, the depth of a working copy directory             can only be increased (telescoped more deeply); you cannot             make a directory more shallow.</p>
<p>The <code>--relocate</code> option causes             <strong>svn switch</strong> to do something different:             it updates your working copy to point to <em>the             same</em> repository directory, only at a different             URL (typically because an administrator has moved the             repository to another server, or to another URL on the             same server).</p>
<p>Source: http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.switch.html</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=291</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BlueScreenView</title>
		<link>http://hyview.ilotus.org/bsite/?p=288</link>
		<comments>http://hyview.ilotus.org/bsite/?p=288#comments</comments>
		<pubDate>Mon, 17 Jan 2011 22:09:51 +0000</pubDate>
		<dc:creator>shawn</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[Software Tools]]></category>
		<category><![CDATA[Blue Screen]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=288</guid>
		<description><![CDATA[BlueScreenView scans all your minidump files created during &#8216;blue screen of death&#8217; crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of [...]]]></description>
			<content:encoded><![CDATA[<p>BlueScreenView scans all your minidump files created during &#8216;blue screen  of death&#8217; crashes, and displays the information about all crashes in  one table. For each crash, BlueScreenView displays the minidump filename, the  date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4  parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file  description, and file version).<br />
For each crash displayed in the upper pane, you can view the details of  the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the  crash stack, so you can easily locate the suspected drivers that  possibly caused the crash.</p>
<p><img src="http://www.nirsoft.net/utils/bluescreenview.gif" alt="" /></p>
<p><img src="http://www.nirsoft.net/utils/bluescreenview2.gif" alt="" /></p>
<p>Source: <a href="http://www.nirsoft.net/utils/blue_screen_view.html" target="_blank">NirSoft BlueScreenView v1.30</a></p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=288</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Request a malware review of your site</title>
		<link>http://hyview.ilotus.org/bsite/?p=280</link>
		<comments>http://hyview.ilotus.org/bsite/?p=280#comments</comments>
		<pubDate>Wed, 01 Dec 2010 20:36:23 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[Web Apps]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[malware]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=280</guid>
		<description><![CDATA[Once you&#8217;re sure your site is free from any infected code and content, you can request a malware review. The malware review is designed for sites that have previously been infected with malicious software. If your site hasn&#8217;t been flagged as having malware, but has been removed from Google&#8217;s index, or no longer performs as [...]]]></description>
			<content:encoded><![CDATA[<div id="article-content-div">
<p>Once you&#8217;re sure <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=163633">your site is free from any infected code and content</a>, you can request a malware review.</p>
<p>The malware review is designed for sites that have previously  been infected with malicious software. If your site hasn&#8217;t been flagged  as having malware, but has been removed from Google&#8217;s index, or no  longer performs as well as it did—perhaps because it violated the <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Guidelines</a>—you should file a <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=35843">reconsideration request</a> instead. You can also use the form to request reconsideration of a site  that has been identified in our search results with a &#8220;This site may be  compromised&#8221; warning message. In both cases, you should make sure that  your site now complies with the Webmaster Guidelines before submitting  the request. However, if your site has been flagged as containing <strong>malware</strong>, filing a reconsideration request isn&#8217;t enough. You <strong>must</strong> follow the process on this page to request a malware review.</p>
<ol>
<li>On the Webmaster Tools Home page, select the site you want.</li>
<li>Click <strong>Diagnostics</strong>, and then click <strong>Malware</strong>.</li>
<li>Click <strong>Request a review</strong>.</li>
</ol>
<p>Google&#8217;s automatic systems will scan your website. If no malware is  found, we&#8217;ll remove the warning from your site. This may take a day or  so to happen; you can check the status of your request in Webmaster  Tools on the <strong>Malware</strong> page under <strong>Diagnostics</strong>.</p>
<p>If you&#8217;ve cleaned your site, but the warning is still in place after a  couple of days, you may not have found and removed all the problematic  content on your site. (Our automatic scanners are far more accurate than  humans, and they may discover code that you have missed.) Check  Webmaster Tools for a list of URLs with potential problems—but remember  that the list contains only a sample of problematic URLs.</p>
<p>Very rarely, it can take up to a day for malware warnings (and links  to the malware review request form) to be visible in Webmaster Tools  after your search has been flagged in search results. If you don&#8217;t see a  warning in Webmaster Tools, but your site is flagged, please check back  later.</p>
<p>Source: <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=168328">http://www.google.com/support/webmasters/bin/answer.py?answer=168328</a></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=280</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips for Cleaning &amp; Securing Your Website</title>
		<link>http://hyview.ilotus.org/bsite/?p=277</link>
		<comments>http://hyview.ilotus.org/bsite/?p=277#comments</comments>
		<pubDate>Wed, 01 Dec 2010 20:28:22 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[Web Apps]]></category>
		<category><![CDATA[badware]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=277</guid>
		<description><![CDATA[This page provides information about identifying, removing, and preventing badware on your website. It does not cover every situation, only the most common cases that we see at StopBadware. Some cases may require further assistance from security professional. You may also find additional information and volunteer assistance in our online community. We provide this advice [...]]]></description>
			<content:encoded><![CDATA[<div id="contentblock">
<p>This page provides information about identifying, removing, and  preventing badware on your website. It does not cover every situation,  only the most common cases that we see at StopBadware. Some cases may  require further assistance from security professional. You may also find  additional information and volunteer assistance in <a href="http://badwarebusters.org/">our online community</a>.</p>
<p><em>We provide this advice as-is and cannot guarantee the results of following it. Like you, we do the best we can.</em></p>
<p><strong>There are three basic steps to restoring and maintaining a clean website:</strong></p>
<ol>
<li>Identifying badware behavior</li>
<li>Removing the badware behavior</li>
<li>Preventing future infection</li>
</ol>
<h3 id="identifying">Identifying badware behavior</h3>
<p>The first step to keeping your website badware-free is to check for  any badware or badware behaviors that may already be on your site.</p>
<h4>What to look for</h4>
<p>The three most common forms of badware that StopBadware sees on compromised sites are:</p>
<ol>
<li><a href="http://www.stopbadware.org/home/security#scripts">Malicious scripts</a></li>
<li><a href="http://www.stopbadware.org/home/security#htaccess">.htaccess redirects</a></li>
<li><a href="http://www.stopbadware.org/home/security#iframes">Hidden iframes</a></li>
</ol>
<h4 id="scripts">Malicious scripts</h4>
<p>Malicious scripts are often used to redirect site visitors to a  different website and/or load badware from another source. These scripts  will often be injected by an attacker into the content of your web  pages, or sometimes into other files on your server, such as images and  PDFs. Sometimes, instead of injecting the entire script into your web  pages, the attacker will only inject a pointer to a .js or other file  that the attacker saves in a directory on your web server.</p>
<p>Many malicious scripts use obfuscation to make them more difficult for anti-virus scanners to detect:</p>
<p><img title="picture of obfuscated script" src="http://www.stopbadware.org/images/obfuscated_script.png" alt="picture of obfuscated script" /></p>
<p>Some malicious scripts use names that look like they’re coming from legitimate sites (note the misspelling of “analytics”):</p>
<p><img title="picture of deceptive script" src="http://www.stopbadware.org/images/deceptive_script.png" alt="picture of deceptive script" /></p>
<h4 id="htaccess">.htaccess redirects</h4>
<p>The Apache web server, which is used by many hosting providers, uses a  hidden server file called .htaccess to configure certain access  settings for directories on the website. Attackers will sometimes modify  an existing .htaccess file on your web server or upload new .htaccess  files to your web server containing instructions to redirect users to  other websites, often ones that lead to badware downloads or fraudulent  product sales.</p>
<p><img title="picture of an htaccess redirect" src="http://www.stopbadware.org/images/htaccess_redirect.png" alt="picture of an htaccess redirect" /></p>
<h4 id="iframes">Hidden iframes</h4>
<p>An iframe is a section of a web page that loads content from another  page or site. Attackers will often inject malicious iframes into a web  page or other file on your server. Often, these iframes will be  configured so they don’t show up on the web page when someone visits the  page, but the malicious content they are loading will still load,  hidden from the visitor’s view.</p>
<p><img title="picture of a hidden iframe injected in a web page" src="http://www.stopbadware.org/images/iframe.png" alt="picture of a hidden iframe injected in a web page" /></p>
<h4>How to look for it</h4>
<p>If your site was reported as a badware site by Google, you can use Google’s <a href="http://google.com/webmasters/tools">Webmaster Tools</a> to get more information about what was detected. This includes a  sampling of pages on which the badware was detected and, using a Labs  feature, possibly even a sample of the bad code that was found on your  site. Certain information can also be found on the Google Diagnostics  page, which can be found by replacing <strong>example.com</strong> in the following URL with your own site’s URL: www.google.com/safebrowsing/diagnostic?site=example.com</p>
<p>There exist several free and paid website scanning services on the  Internet that can help you zero in on specific badware on your site.  There are also tools that you can use on your web server and/or on a  downloaded copy of the files from your website to search for specific  text. StopBadware does not list or recommend such services, but the  volunteers in our <a href="http://badwarebusters.org/">online community</a> will be glad to point you to their favorites.</p>
<h3 id="removing">Removing the badware behavior</h3>
<p>Once you have located the code that is causing the badware behavior,  removing it is often as simple as deleting the offending code from all  files in which it appears. Sometimes, it is easier, if you have a clean  backup of your site’s contents, to re-upload all of the site’s files,  though be careful about overwriting files that may have changed since  your last backup. In some cases, the bad content may be stored in one or  more database records, in which case restoring a recent backup of the  database or manually editing the relevant records may be necessary.</p>
<h3 id="preventing">Preventing future infection</h3>
<p>Preventing badware on your website requires protecting three things:  your site itself, the password(s) used to upload content to the site,  and the computer(s) used to upload content to the site. The site itself  must be protected because attackers often look for vulnerable software  to exploit so they can modify your site’s contents. The passwords are  critical because, if they are guessed or stolen, they can be used to  modify the site. Finally, computers are important because badware on  your computer can steal your password and/or modify the contents that  you are uploading.</p>
<h4>Protect your site</h4>
<ul>
<li>Ensure that any software you use (e.g., blogging software like  WordPress, third party scripts, etc.) is kept up to date with the latest  security fixes, either by you (if you installed the software) or by  your hosting provider.</li>
<li>Remove any scripts, services, or other software that you are no longer using.</li>
<li>Change any default passwords that come with the software you are using.</li>
<li>Use appropriate file permissions on your web server.</li>
</ul>
<h4>Protect your password</h4>
<ul>
<li>Use a strong password and change it occasionally, especially if you have reason to think it has been compromised.</li>
<li>Tips for choosing and protecting a strong password can be found at <a href="http://www.dowling.edu/mydowling/tech/good-passwords.html">this helpful page</a></li>
</ul>
<h4>Protect your computer</h4>
<ul>
<li>See <a href="http://www.stopbadware.org/home/badware_prevent">our guide to preventing badware on your computer</a></li>
</ul>
<h3>Additional resources</h3>
<p>Two members of our online community have guides to cleaning a badware-infected website:</p>
<ul>
<li><a href="http://25yearsofprogramming.com/blog/20070705.htm">How to prevent your website from getting hacked &amp; repair a damaged site</a></li>
<li><a href="http://www.unmaskparasites.com/malware-warning-guide/#cleanup">Practical Guide to Dealing With Google’s Malware Warnings</a></li>
</ul>
<p><em>Note: These sites may recommend, advertise, or link to products  or services. This does not indicate an endorsement by StopBadware of any  of these products or services.</em></p>
<p>Once your site is clean and protected, be sure to <a href="http://www.stopbadware.org/home/reviewinfo">remove it from our partners’ badware lists</a>.</p>
<p>Source: <a href="http://www.stopbadware.org/home/security">http://www.stopbadware.org/home/security</a></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=277</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PeerBlock 1.1, released November 22, 2010!</title>
		<link>http://hyview.ilotus.org/bsite/?p=268</link>
		<comments>http://hyview.ilotus.org/bsite/?p=268#comments</comments>
		<pubDate>Thu, 25 Nov 2010 17:19:33 +0000</pubDate>
		<dc:creator>editor</dc:creator>
				<category><![CDATA[Software Tools]]></category>
		<category><![CDATA[ip blocker]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=268</guid>
		<description><![CDATA[This is a Stable Release of PeerBlock.  It includes many bugfixes and a few new features over our last PeerBlock 1.0 Stable Release, and should work great on Windows 2000, XP, Vista, and 7 (plus server variants), both 32- and 64-bit versions.  New Stable 1.1.x bugfix releases should come out every few months from here [...]]]></description>
			<content:encoded><![CDATA[<p>This is a Stable Release of PeerBlock.  It includes many bugfixes and  a few new features over our last PeerBlock 1.0 Stable Release, and  should work great on Windows  2000, XP, Vista, and 7 (plus server variants), both 32- and 64-bit  versions.  New Stable 1.1.x bugfix releases should come out every few  months from here on in, but new feature development releases will be  PeerBlock 1.1+ <a title="PeerBlock Beta Release (latest)" href="http://www.peerblock.com/latest-interim-release">Beta Releases</a>.</p>
<h3>What&#8217;s New?</h3>
<p>Here are the most important changes present in this new Stable Release, as compared to our previous Stable Release <a title="PeerBlock 1.0 (r181) Stable Release" href="http://www.peerblock.com/releases/public-releases/peerblock-1.0.0-r181">PeerBlock 1.0 (r181)</a>.</p>
<ul>
<li><strong>Signed Driver </strong>- We now have a signed driver!  If you&#8217;re using  a 64-bit version of Windows Vista or 7, you will no longer need to  test-sign the driver, or hit F8 during boot, or anything else.  It  should all just work!</li>
<li><strong>iBlocklist Lists </strong>- We&#8217;ve updated our standard list URLs to point at <a href="http://www.iblocklist.com/">iblocklist.com</a> lists instead of the original peerguardian.sourceforge.net ones.  They  are faster, and are much more reliable &#8211; no more &#8220;Error contacting URL&#8221;  messages!  We will also upgrade your pre-existing lists from  sourceforge.net hosted ones to iblocklist.com ones.  Also note that the  &#8220;Gov&#8221; list has been removed, since its contents were merged with the  &#8220;P2P&#8221; list long ago.</li>
<li><strong>Installer Rewrite </strong>- Our newest Dev Team member, XhmikosR, has  pretty much completely rewritten the installer from scratch.  Most  importantly, it should actually work now, even during uninstall!  (Not  that you&#8217;ll ever want to uninstall PeerBlock, of course, but just in  case&#8230;)</li>
<li><strong>Updated List Manager </strong>- Reworked this window a bit, to make it easier to get back to the lists originally presented to you in the Startup Wizard.</li>
<li><strong>Allowed Connections Displayed </strong>- By default, the &#8220;Show allowed  connections&#8221; option will be disabled.  (This is due to performance  reasons, as the tool will consume considerably more CPU if displaying of  allowed connections is enabled.)  We are still logging the first 9  allowed packets though, so that you know that we&#8217;re actually working!</li>
<li><strong>Save Settings </strong>- We&#8217;ve added a &#8220;Save&#8221; button to the settings panel, so that you can be sure your settings updates have been saved.</li>
<li><strong>List Verification </strong>- After downloading an updated list, we&#8217;ll  now make sure that the file contains at least one ip-address range  before we&#8217;ll overwrite your old list.  This way you will be protected  against your lists being corrupted while downloading them.</li>
</ul>
<h3>Installation</h3>
<p>New install?  No problem, just download the above .exe file and run  it, and it will take care of everything for you . . . even migrating  over your old PeerGuardian 2 settings if you had that installed on your  machine already.</p>
<p>Upgrading from an older release?  No need to uninstall that previous  version of PeerBlock before installing PeerBlock 1.1 &#8211; you just need to  exit any currently-running version, then download and run the  installer.  You can exit PeerBlock by right-clicking on the little  cube/&#8221;block&#8221; PeerBlock icon in the lower-right corner of your screen, by  the clock, and selecting &#8220;Exit&#8221;.</p>
<h3>Other Download Options</h3>
<p>If you&#8217;d rather not use the Installer based version of PeerBlock, you  can instead download a &#8220;Portable&#8221; .zip version.  Those files, along  with checksum information for all our files if you&#8217;d like to verify that  your download hasn&#8217;t been corrupted, can be found on our <a href="http://www.peerblock.com/releases/public-releases/peerblock-1.1-r518-other-downloads">Other Downloads</a> page.</p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=268</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Convert video clips for portable media player</title>
		<link>http://hyview.ilotus.org/bsite/?p=265</link>
		<comments>http://hyview.ilotus.org/bsite/?p=265#comments</comments>
		<pubDate>Mon, 01 Nov 2010 16:37:53 +0000</pubDate>
		<dc:creator>shawn</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[Video Tools]]></category>
		<category><![CDATA[converter]]></category>
		<category><![CDATA[mp4]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=265</guid>
		<description><![CDATA[Most likely the portable media player can handle mp4 file format. Use WinAVI Video Converter to handle iPod, PSP, 3GP and MP4 files. For mp4 file, the best bet would be convert all size to 320&#215;240 format, most media player support this size. If keeping the original size like 720&#215;480 (for DVD size), PC can [...]]]></description>
			<content:encoded><![CDATA[<p>Most likely the portable media player can handle mp4 file format.</p>
<p>Use WinAVI Video Converter to handle iPod, PSP, 3GP and MP4 files.</p>
<p>For mp4 file, the best bet would be convert all size to 320&#215;240 format, most media player support this size. If keeping the original size like 720&#215;480 (for DVD size), PC can play it, but media player might reject it.</p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=265</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to display only unread mails in Gmail?</title>
		<link>http://hyview.ilotus.org/bsite/?p=263</link>
		<comments>http://hyview.ilotus.org/bsite/?p=263#comments</comments>
		<pubDate>Fri, 29 Oct 2010 16:33:54 +0000</pubDate>
		<dc:creator>shawn</dc:creator>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[How-to]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[gmail]]></category>

		<guid isPermaLink="false">http://hyview.ilotus.org/bsite/?p=263</guid>
		<description><![CDATA[Type in is:unread in the search box.]]></description>
			<content:encoded><![CDATA[<p>Type in is:unread in the search box.</p>
]]></content:encoded>
			<wfw:commentRss>http://hyview.ilotus.org/bsite/?feed=rss2&#038;p=263</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

