Welcome to www.allaboutspam.com

Web Hosting - Why Backups Are Essential One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort.

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.

Copyright infringement case Learning Copyright Law through Copyright Infringement Cases Copyright infringement cases can be both costly and time consuming. Considering copyright infringement is something that isn’t as easily defined as theft or speeding, there are numerous copyright infringement cases that are changing the way copyright law is viewed in the United States of America. By reviewing a few of these copyright infringement cases, you’ll be able to get a better idea of what is, and is not, acceptable use of copyrighted works. As a forward, however, you’ll need to know a little bit about copyright law. Most copyright lawsuits are brought to the courts because a copyright owner has found their copyright is being used outside the copyright laws. This usually means that the copyright holder hadn’t been asked for permission to use the work, or if they had, that the work is not being used in an agreed-upon context or they have not been paid royalties. The copyright infringement cases, listed below, give a sampling of what goes to the Supreme Court in copyright infringement. Feist Publications v. Rural Telephone Service Co (6th Cir. 1996) This copyright infringement case was brought upon the Supreme Court in 1996 regarding the copyright of a database. The supreme court, in this instance, decided that compilations of data (such as in a database) are only protected by copyright when they are “arranged and selected in an original manner.” Although the level of originality needed to make the database copyright-able is not very high, the pages of a directory such as a phone book are not protect-able because the data contained therein is arranged geographically, then alphabetically. Because of this, the data was not original enough to warrant a copyright infringement charge, and the competing telephone company was allowed to tap into their competitors’ database and use that data in their own work without liability. Princeton University Press v. Michigan Document Services, Inc (6th Cir 1996) This case has to do with the ‘fair use’ law, which is defined in the Copyright Act of 1976, 17 U.S.C. § 107. In this case, a photocopying service was sued for copyright infringement for making ‘course packs’ for the University of Michigan. In this case, a course pack was a group of reading materials assigned by a professor – then the course pack was bound together by a professional copy shop. In the fair use system, there is a system available for payment of copyright fees to publishers whose works are used in course materials, the printing shop owner refused to pay the copyright cost. When it went to the Supreme Court, they analyzed the fair use code and found that it was NOT fair use, and the printing shop had to pay the copyright costs. As you can see, copyright infringement cases are cases in which someone violates the rights of a copyright owner, as provided by 17 USC §106, or of the author as provided in §106A. These copyright infringement cases can be taken to either criminal or civil court, and can carry with it a hefty fine. Copyright infringement cases are brought upon people who violate copyrights every day. In recent times, you’ll find many copyright cases in relation to electronic copyrights – such as those you’d find on a website or PDF file, as well as other digital media such as music and audio files. It’s probable that you’ve seen copyright cases brought against the common person – such as a child or family – for downloading digital music in the form of MP3s. In the current internet age we’re in, it’s not surprising to see so many music and video copyright cases brought to us because of peer to peer file sharing made possible by the internet. You can be certain that until people know the rules of copyright, and downloading copyrighted material from the internet that we’ll see many more copyright cases.