Welcome to oslab.net

Software copyright statement A Software Copyright Statement Protects Current and Future Works If you have a site that is dedicated to the sharing and distribution of open source software it is a great idea to have a software copyright statement that explains the limits of use for your software as well as the limits of your responsibility for those uses. I also recommend getting an attorney to look over the statement before posting it just to be sure there are no legal issues that you may be unaware of. A software copyright statement doesn't have to be a 10 page booklet on the law or the protections that copyright offers, it should be a simple short paragraph stating the basics and hopefully covering your rear from litigation and/or responsibility should someone use the software you are allowing them to use for something insanely stupid or frighteningly criminal while establishing your ownership of the material and expectations of those you are allowing to use your creation. This for some is a no brainer because they've done it before and know the ropes. There are new software developers born and made each and every day and this type of software copyright statement may serve to save them a little grief of their own some day. If you are being kind enough to freely share the software you created with others, you'd like to think that they would at least return the favor of using it within the letter of the law or the manner in which it was intended. This, however, is rarely the case so protecting yourself, your copyright, and your future interests by posting a software copyright statement on your website is really the best way to go in a situation such as this. Trust me I'm not trying to talk anyone out of sharing his or her software with the world. I rather like open source software and admit to using it freely (no pun intended). I love saving money almost as much as I love playing around with new technology. Software allows me to do that and find likes and dislikes about all kinds of programs. Issuing a software copyright statement is one way of protecting your investment of time, effort, energy, and sheer brilliance in the making and design of your technological masterpiece. Hopefully that flattery will keep you going a bit longer at any rate. It is important to know that a software copyright statement is only part of the process required to protect your software but for the most part poses a significant deterrent to those that would abuse your copyright and/or your kindness in allowing the distribution of your software. Even if you are charging people for the use of your software (we are a nation of capitalists after all) you still need to protect the labor you have put into making not only the software but the distribution method, the website, the payment method and the thousands of other things that are part and parcel of the business model for your software distribution. Your software copyright statement is a very small protection for your software don't expect it to be the brunt of your protection. Most of the software developers, coders, and programmers (and any other name you wish to call them) that I know aren't as concerned nearly as much about associating their name with the products they create as they are with protecting future potential income from both the products they are currently designing and the future, improvements they will make to the software and the much improved finished product that comes later. By protecting all your work with a software copyright statement you are not only protecting current works but future works as well.

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.

Web Hosting - All About Domain Names "What's in a name?" Shakespeare asks in Romeo and Juliet. In the case of your web site the answer is: quite a lot. A domain name is the English (or other) language designator for your site. Because of the way the Internet functions, that name is associated with an IP address, a numeric identifier that computers and network components use to connect a browser to a web site. It's not mandatory that a site has a name. But directing visitors by IP address can quickly generate difficulties. Having an IP address IS mandatory, since it's ultimately the way a web site is located by other computers and network software. In the early days of the Internet the name was chosen carefully in order to help a person remember the URL. That made it easier to type, too. With hotspots on a page, great search engines, social networking and other contemporary tools, that's not as important now. But from a marketing perspective, it still helps to have a good name. It's still beneficial to have a site called 'CheapTVs.com' if what you sell are inexpensive TV sets. Calling your site, 'InexpensiveElectronicVisualDisplayDevices.com' may describe your business in some way, but it's a little harder to refer a new person to your site. Which name you choose can, therefore, affect how much traffic your site gets, how soon. Sooner or later, if you have information and/or products/services that people want, word will get around. But having a good name can certainly help. Love them or hate them, the Google company chose well. Of course, the fact is that there are millions of web sites around the world. That means, you don't necessarily get the name of your first choice. ICANN (Internet Corporation for Assigned Names and Numbers) is the internationally recognized authority for managing IP addresses across the worldwide Internet, along with the top-level domain name-parts (.com, .net, .org, .edu, and so forth). But registering a name is done by simply contacting any of a hundred organizations that work as intermediaries to establish and track the names. GoDaddy, Register.com, Network Solutions and a great many others provide the service for anywhere from free to a few dollars per month or year. You contact them by navigating to their web site. Then, using a feature they all provide, you can select a possible name. They use something called whois and other software to determine if the name is already claimed. Or, you can check yourself at www.whois.com. Registration is for a limited time, but typically renewable in perpetuity provided you pay the (usually annual) fee. You may have to go through several choices to find a domain name that isn't already in use. With so many millions of sites, the odds of you getting your first choice is slim, unless you have a highly unusual imagination. But, it's also true that domains tend to die or expire. As they do, the name becomes available for use by someone new. A method for getting on a 'waiting list' is available. You register the name you want and if and when the name becomes available, you are offered the chance to claim it. Naturally, there's competition even on the waiting list for 'good' names. There are many different ways of establishing priority that vary by company. At any given time there are thousands of so-called auctions going on to bid on names. Give some thought to your new domain name and research its availability, but don't stress over it. The name isn't everything. After all, if Google had built a search engine that delivered usable results only 10% of the time, their name would be mud.