Welcome to www.tetheredmommy.com

Events of copyright infringement The Events of Copyright Infringement: Innocent People Infringing Accidentally Copyright infringement is in the news a lot lately – it’s hard to miss stories about kids being carted off to jail or seriously fined for downloading music or movies off the internet. I’ve even heard about a lady was fined for tens of thousands of dollars because of the events of copyright infringement – her grandson downloading music, and she couldn’t prove it wasn’t her. The events of copyright infringement are complicated – and not easy to define. Surfing the internet has its advantages and disadvantages, that’s for sure. We’re able to find useful information quickly, but how close are we pertaining to copyright laws? Do we even know what is and is not acceptable? A couple of the more pertinent questions have been asked below: If you hear a great new band, and then download a song from MySpace, is that legal or not? The events of copyright infringement are not only limited by Kazaa, Morpheus, or some other file sharing peer to peer (P2P) service. If you download a song - no matter if you’re on a website or a MySpace page - and it isn’t coming from the artist themselves, you may want to think about downloading it. Chances are, if it’s not coming from them, you can’t have it – unless it is under a Creative Commons License. Creative Commons gives the exact ways in which you can use the license – and many times those are completely free and legal to download – so make sure you check if it’s under a CC License. If I’m writing a paper, or article, and I want to quote another website, can I? First of all, did you know the minute you write or create something, you hold the copyright to it? ESPECIALLY if you’re writing it online – it’s very easy to track things in the internet page. So, if you’re writing a blog, all the things you’ve written (no matter good or bad) are there permanently, thanks to archive.org, and you can review last versions of your web pages. Sometimes, people we can use – rather heavily – someone else’s work in our own, and think we’re small and anonymous. That no one will notice by the time you get it down – you’re just ‘borrowing’ it. Before you begin quoting anyone’s website – from CNN to your local neighborhood hardware store – you need to ask the person who holds the copyright if you can. Usually, they’ll let you if you attribute to them. Depending who you talk to, you’ll either have to pay royalties or license rights to republish. If you don’t ask before you quote, you’re beginning the events of copyright infringement and you are opening yourself up for a lawsuit. As you can see, the events of copyright infringement can begin at any time, beginning with normal ‘everyday’ activities. It’s just as easy to infringe on as it is to be infringed upon. Make sure you check your copyright using CopyScape or some other service, and you can check your work against other works on the internet, and make sure that you’re not infringing someone or vice versa. In this day it’s easy to protect yourself from getting infringed upon, and the events of copyright infringement are easy to track. It’s easy for innocent people to get caught in copyright infringement, like children they didn’t know what they could and couldn’t do. Make sure, in all you do, that you’re striving to do the best you can, and you’ll be certain not to fall victim to your own infringing demons.

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Conducting a Self-Evaluation After Getting Fired Sometimes life is hard and when you get fired, it gets even harder. In a country where employee turnover is high and there are no laws to protect you at your work place, potentially anybody is at risk to be fired. In general, that is true, but companies usually only fire a person that has done his or her job improperly, or is not qualified for his or her job any more. Therefore after you get fired, it is time that you conduct a self-evaluation. First of all, you need to make sure you know the reason why you have been fired. Do not just assume, you know why you have been fired. Make sure that your employer tells you the exact reasons why he has fired you. A self-evaluation as to whether the employer is right and whether you might have to work on yourself can only be done after you know why the company has told you to leave. If it was tardiness and absence of work that has gotten you fired, you need to be self critical enough to see that you need to be on time and be at work every day that you are not taking a vacation day. Keeping a job means playing by the rules and these rules do include times that you have to be a t work if you want to keep the job. When your boss told you, that you are not accomplishing your work or you are not qualified for the position, think back and try to find out why he might have said that. Did you deliver your work on time? Was it correct, mostly without any problems and errors? If that is not the case, then perhaps your boss was right and maybe you were not qualified enough to do the job. It might be that you need some more training or some more classes at the university to be able to do your job right. Or maybe you have just chosen a job that is not for you. When you are conducting that self-evaluation, make sure you are not too hypercritical. If it clearly was your fault that you got fired, you need to improve yourself and the personality traits that have led to the firing. Sometimes even though your boss gave you an explanation why you have been fired, you might not agree with the reason you have gotten fired from your company. Yes, sometimes these reasons might not be right. Since this is a society where anybody can get fired, maybe you have been fired because your boss did not like you and he made up some dubious reason for firing you. This is why you have to conduct a self-evaluation to make sure if what you were told is the truth. A self-evaluation might also lead you to the conclusion that you need to choose a different profession than the one you have been in. Maybe it took to get you fired to ser you in the right direction and at some point in your future you might actually thank that boss of yours that he had fired you. Otherwise you might have never found the job that you were destined for and would have been miserable doing the job you were doing. Unhappy employees are not good for a company and some bosses are good enough to realize that. Whatever the reason is that you got fired, make sure you find the reason and check with yourself how much truth lies within that reason and do you have to change to be a better employee and be able to keep your next job.