Many of my traditional blog post live on this site, but a great majority of my social-style posts can be found on my much-busier microbloging site at updates.passthejoe.net. It's busier because my BlogPoster "microblogging" script generates short, Twitter-style posts from the Linux or Windows (or anywhere you can run Ruby with too many Gems) command line, uploads them to the web server and send them out on my Twitter and Mastodon feeds.
I used to post to this blog via scripts and Unix/Linux utilities (curl and Unison) that helped me mirror the files locally and on the server. Since this site recently moved hosts, none of that is set up. I'm just using SFTP and SSH to write posts and manage the site.
Disqus comments are not live just yet because I'm not sure about what I'm going to do for the domain on this site. I'll probably restore the old domain at first just to have some continuity, but for now I like using the "free" domain from this site's new host, NearlyFreeSpeech.net.
The recent BoingBoing post about the busy/huge web site's changes focuses on the move to Disqus comments, but the bigger news is that it's dumping Movable Type for WordPress. Even Matt Mullenweg of Auttomatic fame mentioned it.
A few years ago, BoingBoing, which does something like 1 million views per day, made the move to Movable Type from whatever it is they used until that point. The reason behind the move to MT, as I remember it, anyway, was the high availability of a statically built Movable Type site and its ability to handle the kind of traffic BoingBoing was drawing.
Well fast-forward to now, and BoingBoing's Movable Type days are over. It's still plenty popular but is now running on WordPress. I guess this means that WP is more than able to function in extremely high-traffic environments like that of BoingBoing.
Mozilla is already casting the enterprise market adrift with its stated wish to stop maintaining the Firefox 3.6.x series of the popular web browser in favor of charging through Firefox 4 right into version 5 and coming up on 6 and then who knows what.
Enterprises hate this. They need to build shoddy web-based applications against a browser, and if that browser changes, their apps will likely break.
Hence they need Firefox 3.6.x, if that's what they're building against, to stick around as long as possible.
No, no, NO, says Mozilla. We're in a development frenzy to catch Google Chrome, and we're upsetting the apple cart now for more goodness later.
The enterprise cares nothing for "goodness." It wants sameness, predictability and as little work as possible.
Can't say I blame them.
From a PR standpoint Mozilla is thumbing its nose at any enterprise users who decided to throw in with a browser that isn't Internet Explorer (and for large bases of users, switching browser allegiance isn't something that happens very often — and yes, they are where you, as an individual, were 10 years ago).
Despite all this, I still have updates coming to my remaining Firefox 3.6-running machines (of which there are more than a few, especially because there's not Firefox 4 or 5 for Macintosh PowerPC unless you count TenFourFox).
Yes, they all recently climbed to 3.6.19.
But if you can find the Mozilla Firefox 3.6 page, there is supposedly an end in sight for 3.6.x:
Firefox 3.6.x will be maintained with security and stability updates for a short amount of time. All users are strongly encouraged to upgrade to the latest version of Firefox.
If Mozilla wises up (and I hope they do), they'll continue patching Firefox 3.6.x for security issues for at least the next year if not two.
They don't seem ready or willing to do this, but I bet they're plenty able. Especially if they want to cement (and not rend) its relationship with enterprise users.