<?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>phidgt.com</title>
	<atom:link href="http://phidgt.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://phidgt.com</link>
	<description>Its' Easy!</description>
	<lastBuildDate>Mon, 02 Aug 2010 17:53:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Domain Names Revisited</title>
		<link>http://phidgt.com/2010/08/02/domain-names-revisited/</link>
		<comments>http://phidgt.com/2010/08/02/domain-names-revisited/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 17:53:12 +0000</pubDate>
		<dc:creator>phidgt</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://phidgt.com/?p=72</guid>
		<description><![CDATA[Once again I find myself in the unfortunate position of having to explain the importance of domain names. I&#8217;m beginning to sound like a broken record even to myself, but here it goes. A domain name is as important as the title to your house or car. It is akin to being the title of [...]]]></description>
			<content:encoded><![CDATA[<p>Once again I find myself in the unfortunate position of having to explain the importance of domain names. I&#8217;m beginning to sound like a broken record even to myself, but here it goes.</p>
<p>A domain name is as important as the title to your house or car. It is akin to being the title of your business on the Internet. Even if your web site is simply a personal blog, that domain name is still your brand, your name, a way for people to find you on the web. So, <strong>it is imperative that you take 100% responsibility</strong> of it.</p>
<p>Regardless of which of the hundreds of registrars you choose to purchase your domain name from you will be required to create an account. The information you provide while setting up this account <strong>must be accurate and kept up to date</strong>. This is where most people screw things up. Registrars will send you renewal information to the e-mail address which you provided in the contact information. The registrars generally do not send information via any other means of communication. Therefore, if you change your e-mail address and do not update this information with your domain name registrar you will not receive renewal information and your domain name could expire without you even realizing it. <strong>YOU MUST KEEP YOUR CONTACT INFORMATION UP TO DATE</strong>.</p>
<p>Once your domain name has expired it will be become available for anyone to purchase &#8211; and it will most likely be purchased by what is known as a <a href="http://en.wikipedia.org/wiki/Cybersquatting">Cybersquatter</a>. These folks purchase up expired domains in the hopes of conning you into paying whatever exorbitant fees they want. It is not unusual for them to demand thousands of dollars for you to reclaim your domain name. While this is illegal in most countries it is not illegal in all of them. Attempting any sort of legal battle is going to be a waste of time and money as the law is fairly unenforceable. Your best option is to wait. The person who purchased your domain name may give up after awhile and not renew it. The tricky part is that if you show any interest that you want to buy back your domain name they will likely hang onto it in hopes that you become desperate enough to pay them. </p>
<p>Right now &#8211; ask yourself these questions:</p>
<p>Who owns my domain name?<br />
Where is it registered?<br />
Do you know the log-in and password for your account?<br />
What contact information is associated with you account?<br />
When does your domain name expire?</p>
<p>If you are unable to answer even one of these questions you may potentially have a serious problem on your hands. My advice is to get answers to all of these questions &#8211; right now.</p>
]]></content:encoded>
			<wfw:commentRss>http://phidgt.com/2010/08/02/domain-names-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.0.1</title>
		<link>http://phidgt.com/2010/08/01/wordpress-3-0-1/</link>
		<comments>http://phidgt.com/2010/08/01/wordpress-3-0-1/#comments</comments>
		<pubDate>Sun, 01 Aug 2010 18:33:19 +0000</pubDate>
		<dc:creator>phidgt</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://phidgt.com/?p=70</guid>
		<description><![CDATA[Today we have updated all of our client sites to WordPress version 3.0.1. Please check your sites to make sure that there are no compatibility issues.]]></description>
			<content:encoded><![CDATA[<p>Today we have updated all of our client sites to WordPress version 3.0.1. Please check your sites to make sure that there are no compatibility issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://phidgt.com/2010/08/01/wordpress-3-0-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Updates</title>
		<link>http://phidgt.com/2010/08/01/wordpress-updates/</link>
		<comments>http://phidgt.com/2010/08/01/wordpress-updates/#comments</comments>
		<pubDate>Sun, 01 Aug 2010 18:20:51 +0000</pubDate>
		<dc:creator>phidgt</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://phidgt.com/?p=68</guid>
		<description><![CDATA[The WordPress community is constantly updating and upgrading their software. At phidgt.com we automatically update your site whenever one of these updates happen. As we update your site you will receive an e-mail with the following subject heading: Your WordPress installation has been updated. There are occasions when the update may have compatibility issues with [...]]]></description>
			<content:encoded><![CDATA[<p>The WordPress community is constantly updating and upgrading their software. At phidgt.com we automatically update your site whenever one of these updates happen. </p>
<p>As we update your site you will receive an e-mail with the following subject heading: Your WordPress installation has been updated.</p>
<p>There are occasions when the update may have compatibility issues with aspects of your site. This may include your theme, plug-ins or any customized features that you may have installed. </p>
<p>When you receive one of these e-mails, please go to your site and make sure that everything is working properly. Send us an <a href="mailto:tery@phidgt.com">e-mail</a> if you notice any problems.</p>
]]></content:encoded>
			<wfw:commentRss>http://phidgt.com/2010/08/01/wordpress-updates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Little Something About Plug-ins</title>
		<link>http://phidgt.com/2010/07/01/a-little-something-about-plug-ins/</link>
		<comments>http://phidgt.com/2010/07/01/a-little-something-about-plug-ins/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 16:11:14 +0000</pubDate>
		<dc:creator>phidgt</dc:creator>
				<category><![CDATA[Plug-ins]]></category>

		<guid isPermaLink="false">http://phidgt.com/2007/07/10/a-little-something-about-plug-ins/</guid>
		<description><![CDATA[Word Press is purposefully light and compact. In other words, it doesn&#8217;t have a lot of bells and whistles associated with it when you first get started. The purpose of this is to keep it small, manageable and easy for everybody to use. The fun part of Word Press is the ability to install plug-ins [...]]]></description>
			<content:encoded><![CDATA[<p>Word Press is purposefully light and compact. In other words, it doesn&#8217;t have a lot of bells and whistles associated with it when you first get started. The purpose of this is to keep it small, manageable and easy for everybody to use. The fun part of Word Press is the ability to install plug-ins to add features to your site. A plug-in is similar to installing a software program onto your computer. Instead of installing anything onto your computer, the plug-in is installed directly into your site. A list of plug-ins is available at the <a href="http://codex.wordpress.org/Plugins">codex</a> page at Word Press. This is not a complete list and more plug-ins can be found by searching Google. However, by leaving the codex page, you may encounter plug-ins that are not free and not supported by the Word Press community.<br />
<span id="more-12"></span><br />
Here are a few tips on using plug-ins:
<ul>
<li><strong>Read all of the documentation associated with the plug-in <em>before</em> you download and install it.</strong>
<li>Make sure that the plug-in is compatible with the version of Word Press you are using. You can find that information by going to your Dashboard. In the box titled &#8220;Right Now&#8221; you will see what version of WordPress you are using.
<li>Read any comments left by others to see if there are any problems being reported and if the developer has responded. A plug-in that is no longer being supported may be one to avoid.
<li>Read the installation instructions. Most plug-ins are very easy to install and get working. There are some, however, that require a bit more work and knowledge on php or html code. Depending on your computer skills, you might need some help getting it to work.
<li>Some plug-ins come with very little information. Sometimes you just have to go for it. Maybe it&#8217;ll work; maybe it won&#8217;t.
<li>Don&#8217;t be afraid to test drive plug-ins. In some cases you may have to install 3 or 4 plug-ins to get the right functionality that you are looking for.
</li>
</ul>
<p>Plug-ins can get quite addictive. Don&#8217;t be surprised if you suddenly find yourself spending hours at your computer.</p>
]]></content:encoded>
			<wfw:commentRss>http://phidgt.com/2010/07/01/a-little-something-about-plug-ins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

