Welcome to spokanevalleymarketing.com

Following Up on Fallacies about Getting Free Stuff “Free stuff” – the mere whisper of the words is often enough to make many people throw common sense out the window and head for the free goods like a missile to a target. And then there are those people whose eyes glaze over when they hear those words, because they can’t believe anything worth having can actually be free. The truth about free stuff is really somewhere in the middle. Yes, you can really and truly cash in on many freebie deals for things that you want to have, but a healthy sense of cynicism about free gear is also useful. Here are some of the important things to keep in mind about free stuff. The first myth you should throw out the window is that nothing good comes for free. The fact of the matter is that the price tag on a good doesn’t always match up to the quality, and there are many great free things out there. Case in point: music. Sure, everyone has heard the scare stories about file sharing online, and maybe some big record labels will come after you if you focus on their artists. Dig a little below the surface, however, and you can find a whole new world of really great bands that are more than happy for you to listen to their music over and over again. The same goes for free software. People on the cutting edge of technology who have a passion for creating new and efficient applications often develop open source code software. They’re doing it for the love of it, and they often have more talent than any ten suit-and-tie tech guys trying to hock their latest product for a mega profit margin. Here is where the reality part comes in, however. Yes, you can find wonderful things that are completely free – but yes, you can also find a lot of free things that aren’t worth your time at all and in some cases can cause you a lot of trouble. The net is a great place to fall victim to a “free stuff” scam, but you can also sometimes come across these scams in the mail as well. If something is free, but requires you to give your credit card number or bank details, run the other way. Another myth people have about free stuff, especially free stuff on the internet, is that when you try to cash in, the only free stuff you will be getting is an inbox full of more spam than you can handle. The truth about this is, well, that is can certainly be true. Many companies give away free things in exchange for your email address, so they can try to hit you up to purchase things in the future. What makes this a myth, however, is that it can be avoided. If you don’t want to choke on an inbox of spam, and who could blame you, set up a special (free) email account that you will use exclusively for freebie hunting. You’ll have the best of both worlds. The last myth about free stuff involves the “catch” people are always looking for. Often, for free stuff, the catch is a bit of junk mail or email or the fact that you have to submit to a time consuming survey. Sometimes, the catch is that if you get free stuff through a trial offer, if you don’t cancel it, it keeps coming, and this time you have to pay. The truth about these catches is, however, that the catch is in the eye of the beholder. These things don’t make products any less free; so don’t write off every free offer offhand. You might just find a catch you can live with to get a great free product you really want.

Web Hosting - Domain Name Changes and How They Affect You New domain names are registered all the time, and ones previously registered expired. Sometimes that's the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else to use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to just let it go or sell it. When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties. One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. IP addresses are what are actually used 'under the covers' when one computer communicates with another. Note that there isn't always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we'll stick to the common case here. DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request to be forwarded when the particular DNS server doesn't have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low. In the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was. A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed. The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world. Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching. In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don't move your address or change your name every minute. Since that's true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn't have to be communicated with every request for a web page or data. A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that's your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed. Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random. But DNS servers don't do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies. That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the 'official' range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that's an average. The actual time in any given case can (and does) vary widely. In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can't be resolved properly, you don't reach the server you want. Your browser points to the old one (in the rare case it's still accessible by that name and address), or it simply reports there's no such name at that address. So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being 'not at home' when they call.

Web Hosting - FTP and Other File Transfer Tools Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.