Welcome to www.antones.net
Can Facebook or MySpace Help You Land a Job?
The Internet is quickly becoming the vehicle of choice for people looking for a job and for employers looking for people to hire. There are many job sites on the Internet dedicated to matching up employees and employers, and most people turn to the Internet today when they are hunting for a job instead of turning to the classified ads in the local paper. Job hunting websites may all be well and good when you are looking for a job, but what about social networking sites. Everyone knows how popular sites like Facebook and MySpace are online, but can they help you get a job? If you are in the job market, can these sites be your foot in the door, or a one way ticket to the unemployment line?
The answer is that there is no easy answer. To know if you can find a job using Facebook or MySpace, you have to know how employers feel about these sites, and employers have mixed feeling about them. Some companies are actively using social networking sites to track down employees that meet their company?s employee profile and have had great success finding workers via social networking sites. Other companies wouldn?t touch these sites as a hiring tool with a ten-foot poll ? in fact, many companies don?t even want you to access these websites from their company computers. The real answer to this question has more to do with exactly what kind of job you are looking for.
Are you looking for an executive position at a company? Then stay off of the social networking sites, at least for job hunting (and maybe all together). No company is going to look for its top brass on a social networking site, and you will be wasting your time. However, if you are looking for entry level or hourly wage work, the social networking sites like MySpace and Facebook may be the answer for you. Many hourly wage employers in particular, like fast food restaurant chains and mall stores, use MySpace and Facebook to look for potential employees in their area. If a potential employer sees your profile and thinks you may be a good fit for their company, they will send you an email or an instant message and get the ball rolling.
You should also, however, carefully consider the downsides of using social networking sites as a job tool ? and you should carefully consider how and if you use these sites at all if you are in the market for a new job. Most people wouldn?t want their parents to see their social networking site profile, let alone potential employers. If you have rude and off color material, political or religious material, and inappropriate photos of yourself on your profile, a potential employer will be turned off, and you might lose your chance at that job. Most people give up way too much of their privacy when they use these kinds of sites, and your social networking site profile may offer a window into a side of you an employer might not be overly impressed with.
Further, you can open yourself up to danger by using these sites to job hunt. If someone approached you in the street and offered you a job, would you accept? Then why would you accept a face value an approach by someone on social networking site? If you do get approached for an interview, never meet anyone in a private place, and do your homework to make sure the facts check out before you go for the interview.
One last reality check ? there are over 60 million users on MySpace alone. How will an employer find you in the crowd? MySpace and Facebook may help you in your job hunt, but don?t count on them as your sole avenue into the job market.
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 - DNS, How The Internet Keeps Track of Names The way computers communicate is, in a way, very similar to something very familiar: the postal system that delivers letters and packages. Here's how... The Internet is just what the name suggests, a large inter-connected set of networks. But those networks are pointless without the one part that forms what is called their 'end-nodes', otherwise known as computers. Those computers often need to share information because the people who use them want to share information. But, in a system where there are millions of separate computers, how can you enable them all to communicate? One very important feature of that solution is performed by something called DNS, the Domain Name System. Every part of a network that is going to send or receive information is assigned an IP address. That's a numeric identifier that uniquely specifies a particular 'node', such as a computer, a router that directs traffic or other component. They look like this: 184.108.40.206 But those numbers are more difficult for people to remember and work with. They also aren't very attractive from a marketing perspective. So, a naming system was layered on top of some of them, mostly the computers involved, though routers have names, too. But once you have a system that associates a unique IP address to a given name, you need some way of keeping track of all of them. That's carried out by several different pieces of the system: Name Registrars, DNS Servers and other components. The Name Registrars, overseen by IANA (Internet Assigned Numbers Authority) and other international bodies, provide and keep track of domain names. When you register with GoDaddy or any of a hundred other intermediate companies, ultimately that information makes its way into a number of specialized databases stored inside DNS Servers. A DNS Server is the hardware and/or software that tracks and forwards the IP Address/Domain Name pair from one place to the next. In many cases, there are a number of them between your browser and the remote computer you want to share information with. Suppose you request information from, say, Yahoo's site by clicking on a link on their site. DNS resolves (translates) the name of WHO IS making the request and OF WHOM, to addresses, then passes the request through the network to the requested IP address. The requested data is then passed back through the mesh of network components to your computer and displayed in your browser. Whether the communication is between a desktop computer and a server somewhere, or between one server and another, the process is essentially the same. DNS servers translate names into IP addresses and the requests for data are forwarded on. In some cases those DNS servers are part of a specialized network computer whose sole job is to do the translation and forwarding. In other cases the DNS software may reside on a server that also houses a database of general data, or stores email, or performs other functions. But however complicated the chain or the parts, the basic process is simple. Translate the name to an address, just as the postal system does. Whether international or local, your name is associated with an address, and the deliveries are made to the address, then forwarded to a particular name.