It seems that Google has a new factor to consider for web rankings: HTTPS.
I understand the allure of encryption. Heck, I use StartPage as my search site, and all of my searches go over HTTPS. The problem is that HTTPS is expensive.
The Rosenthal & Rosenthal site is undergoing a major revamp, moving from a static, all-Flash (yech) accumulation of static pages and compiled Flash objects to WordPress 3.8.1.
In addition to rebuilding on a stable platform, the redesign plan involves a number of new features, some of which I'll document here on my personal blog to try to contribute to the community 1.
- I truly dislike the phrase "give back," as I've not taken anything; I do, however, contribute, as I can. ↩
I recently had the distasteful experience of having to tell a long-time client to find someone else to handle his IT consulting. We had (I thought) become friends over the years, though recently, tensions surrounding some server trouble over here (I hosted his email) led to difficulties in our relationship.
NettiCat has graciously granted me permission to modify (slightly) his BetterPrivacy extension to allow for installation and use under SeaMonkey. The current version (1.68.m, as of the date of this post) should install under SeaMonkey 2.0a1 and above.
For those not familiar with this extension, it goes beyond the built-in sanitizing functionality of Firefox and SeaMonkey to include clearing the Flash cookies, which may be stored for an otherwise indefinite period of time. For more on the actual feature set of BetterPrivacy, I would suggest reading the information available on the official home.
Download & Installation
Ultimately, BetterPrivacy for SeaMonkey 1.68.m (and later) should be available for download from the Modified Firefox Extensions page of the xSidebar project site. You may also download it from the Rosenthal & Rosenthal FTP site via anonymous transfer.
Please feel free to post comments here for support. I can't guarantee that I'll respond quickly to such requests, but any SeaMonkey-specific issues should be directed here and not to the official support page.
Changes from the official 1.68 release, specific to SeaMonkey
- Installation is enabled for SeaMonkey 2.0a1 and above.
- Changes per NettiCat's requirements.
- Option to auto-delete Flash LSOs on exit is available on preferences panel.
- References to "Firefox" in dialogs (in the en-US locale) have been changed to "browser" for a more consistent feel.
- Some en-US language enhanced.
Localization support is welcome. There are a number of languages currently enabled, and I can't adequately translate all of them (I am passable at a handful, but native speakers are encouraged to participate).
First, my heartfelt condolences to everyone who was impacted personally or financially by yesterday's DDoS attack against GoDaddy. That includes customers and employees, and as an admin, I know firsthand what it's like when the systems grind to a halt under one of these things, when all that's left is simply to put something else on the front line to check for traffic and wait it out (or request new address blocks all the way around). This, of course, does not take place in a vacuum: when these things hit, we are always surrounded by The Suits who have no clue as to why we can't do anything more (or faster), constantly complaining of our inadequacies (we should have known better; we should have predicted; we should have been better prepared; etc.).
As a consultant, I look at computers and operating systems from a "best tool for the job" perspective. Some systems are better suited to some things than others. I wouldn't expect to play modern computer games, written for Win32 or Win64 on Linux or OS/2, no matter how far advanced Wine or Odin was/were. Likewise, I wouldn't consider running a web server on the Win32 or Win64 platform vs Linux or OS/2.
Along with other suitability considerations, I factor in my own (or the client's own) comfortability factor with a particular environment. The Mac object oriented desktop is quite nice, though it's not my environment of choice. On Linux, I prefer KDE to Gnome, but neither of those nor the Mac desktop nor Windows Explorer approaches the level of comfort, familiarity, or ease-of-use which I experience using the Workplace Shell, which is - for me, at least - the main reason I stick with eCS.
Stability concerns? These affect all platforms at one time or another. Unless the problems are inherent to the overall system design (Windows' weak security model and the dangers of the single registry paradigm), such things need to be considered in the course of business. that is to say, they happen. Cars break down, too, but I'm not quite ready to go back to a horse and cart (and carts break - ever change a wagon wheel?).