Welcome to esiq.org

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.

Preparing Questions to Ask in your Upcoming Job Interview When you get ready for a job interview, chances are you have spent a lot of time trying to guess the questions you will be asked and prepare your answers to them. How will you explain that gap in your work history? What will you say when they ask you why you left your last job? In the rush to make sure that you have all of your answers perfectly prepared and ready, don’t forget to prepare a few questions of your own to ask the person who is interviewing you. Asking questions is an important part of your interview. When you get asked the old “do you have any questions for us” one, it pays to actually be able to come back with a few questions instead of a, “no, I don’t think so.” Asking questions will show that you are engaged in the interview and have done some thinking about the position, plus, the questions you ask will help you elicit valuable information you need when you have to decide whether or not to actually take the job, should it be offered to you. The first thing you should want to find out is why the job is open in the first place. Is the job you are applying for a new position? That means you can expect to have a lot of transitional bumps along the way as you are integrated into the company. If the job is not new, and the person before you was fired, then you can expect things to be in a state of disarray when you take over and that you will have to spend a lot of time up front cleaning up spilled milk. If the job is open because the person who had it before you moved up in the company, then you will know that this is a job with a lot of future potential. Next, find out a little bit about the person who will actually be your boss if you get the job. Sometimes, this person will be involved in the interview, but often they will not. Finding out how high up in the company chain you will be reporting will help you gauge how important the position for which you are applying is to the company. Also, it helps to know a little bit about the personality type of the boss to be. If you like to keep your head down and do your work, and your potential new boss is one of those “wacky” types, then you may want to look elsewhere. From there, ask about the kinds of responsibilities you will need to take on board right out of the gate. When companies are hiring for a new position, they usually have a few ideas about what that person will need to start working on right away. Getting a clue about your first project will help you decide if this job is right for you. This is also a good time to ask the interviewer about their job and why they like working the company. You may find out that this really could be your dream job, or you may end up sensing from your interviewer that you should run away, fast. Last but not least, ask your interview when you should follow-up on your interview. Don’t open the door for a “don’t call us, we’ll call you” kind of interview closing. Let the interviewer know to their face that will be making the effort to contact them again. You may get the vibe from your interviewer that the job probably will be going to someone else, so you can move on quickly, or you may end up being offered the job on the spot. Either way, you will have opened the lines of communication to take the next step.

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.