Welcome to the personal redirect system of Frank S. Pilone. This site is intended to provide short and easy to deal with URLs to people and the Internet in general. When this system was developped, the system used a PHP code front end which has eventually caused more problems than value. The site has then been cleaned out with all of the relevent URLs kept, and the obsolete URLs just ignored during the transfer. In turn, I will simply do things the old fashion way which is to edit and manage an .htaccess file.

So, why would something like this be useful, and why not just use a hosted option such as bit.ly or goo.gl? Well, let's address the desire to do things "inhouse". If I used a service, that service may go down, and dissolve. There may also be restrictions on modifying or changing the URLs. And even if there isn't, if there is information I would consider as private, I may not feel comfortable with a company handling those URLs. For example, a doctor that asked me to keep a log of my life to help with pain management would be considered as confidential. I would give her a URL that should be easy for her to type if she doesn't have a link that is on her computer. I want her to have an easy URL, but keep that URL destination under my complete authority. If I am relying on a company such as bit.ly to do that, they now have the URL. If there is a breach in their system, a hacker has that information, and while I will like to think I am not that special enough to be a target, it is still a disturbing thought. If I own the domain where the link is being served, then I have more responsibility, but better control.

Next is URLs themselves. If I send a hyper link via an IM service, or email - this is not much of an issue. However, if a person has to type the URL in (such as referring to a printed document), then that becomes a problem. In addition, if I needed to send a URL via SMS, there is a maximum length on how long that URL can be because of the implementation design of SMS. In example, it is harder to type http://store.hp.com/us/en/pdp/Laptops/hp-envy-x360---15-w155nr-%28energy-star%29-m1v67ua-aba than it is to type http://fsp.cc/envy360. If someone is off by one character when typing a URL, at the very least, they will get the wrong page, and at worst a file not found error.

So, learning through mistakes of the old system which used PHP, and a MySQL database to manage links, I have instead relied on good ole' fashion .htaccess. This is a simple text file, and is uploaded via FTP. I had decided to make all fsp.cc Addresses a redirect system. This will also include subdomains. Some subdomains exist now, and catered around a particular company or subject. For example, all links at http://a.fsp.cc/ are related with AMazon. Links at http://g.fsp.cc/ are related with Google. Some people may have a dedicated subdomain for which I will give links to. For example, a person with the Initials F.P. has their links at http://fp.fsp.cc/ which in this case will redirect to http://fsp.tel/.

So why did I choose fsp.cc? Simply put, fsp.to which was preferred wasn't/isn't available to me. Last I looked, the domain is for sale for $400 more than I can afford for the domain at this moment. Even if I had the resources to pay the normal registrar fee of the .TO domain, it is still $350 more than I would be able to afford.

Public Subdomains