I changed my primary Uniform Resource Locator, URL, to a name more fitting for the next phase of my life. Of course I am also trying to move past my Higher Education Technology focus. This change is not really worthy of a post, however, the experience surrounding the purchase and implementation of a new URL did capture my interest. I have wanted to switch for a while but I had not been struck by a name that seemed appropriate. But I have been referring to my blog in the sub title as “The Adventure Continues” and I have drifted around that theme with a number of posts. So I took the next step, checked WHOIS and voila, the name I wanted was available and affordable. I have always gravitated to the .org top level domain because I equate .org with non-commercial and I have no interest in monetizing my blog. For the most part, my blog is my archive of my adventures, so the Adventure Continues with a new blog name and URL.
Do you remember when the URL was everything. URL squatters tried to grab up all potentially lucrative names that at that time would typically precede .com or maybe .net. Of course today you can create about any top level domain but us old timers still feel a connection to the early pioneers. The other day I was in a meeting with students reviewing a proposal which had an URL printed in the documentation as a reference. I told the students that they could paste the url into their browser to review the site. One student giggled and said that she could not remember ever hearing someone refer to a web address as an URL. OK, that surprised me a bit. But really that was validation that the URL does not carry that much weight anymore. Content is king because search engines are all powerful.
I reflect upon this because of the emphasis my domain name provider tried to place on the importance of privacy for my domain name registration. They wanted to charge me $8 per year to make my whois registration private. If you have no idea what I am talking about open a terminal session and type “whois adventurecontinues.org”. I have owned URLs from the very early Internet days, back when the URL dictated whether anyone would find your site or not. Public whois registration information was important to validate the integrity of the site and of course let people know who they might need to buy the URL from in case it was highly desired. Unfortunately this is valuable identity information which today is considered an invitation to sell you something, primarily all sorts of help with monetizing your website. Since purchasing my new URL I have received 100+ emails offering me every conceivable service I might ever need to optimize my website. Luckily all of those emails end up in my Spam folder (thank you Google). I suppose I could have avoided those emails ending up in my Spam folder if I had paid GoDaddy an extra $8 per year. Maybe I should pay Google the $8 for making it easy to delete them all “Delete all spam messages now (messages that have been in Spam more than 30 days will be automatically deleted)”.
I can rationalize this decision to brave the dangerous world of public notification but then again, it will create further issues. I have always been good at protecting the distribution of my phone number and to a certain extent my home address, but this information is readily available via the WHOIS lookup. Oh well, I think I will take the risk. After all Life is just one Big Adventure.
I was outside recently watching our Research Support Student employees fly our helicopter drone over campus capturing some great autumn video.
I also had my dog, Abby, with me since I designated it to be “bring your dog to work friday”. Well Abby was generating some interest from students homesick for their pets while I got into a conversation with a couple of our IT Support Services Student employees about their programming ideas. These ideas come from our encouragement for our student employees to explore ways that we might improve our business processes. The idea was about a web app that the student workers could use to trade shifts with their coworkers. The gist of the conversation quickly focused on their perception that IT only recommended development based on Perl. Well he mentioned this to the right guy, actually the boss, but really what a ridiculous perception that obviously had roots from the past. But that type of preferential influence will not fly today.
Perl does have a significant development presence here and there is nothing wrong with Perl, but that should not dictate the requirements of future development. The student asked if he could develop in PHP but was told that PHP was not secure. Well maybe that a general statement with some merit but probably not of concern for a student employment shift sharing application. The student actually wanted to use Python and then our conversation steered toward new ideas like the possibility that WordPress might be utilized. My major point with bringing this up is that we in IT have to be cognizant of the influence we convey and that our way is not the only way. IT should remember when they were the radical adopters of new application platforms. Consider the fights they must have had with cobol and fortran proponents.