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.
A peek at the Planet Python blog aggregator (I'm a big Planet blog fan, in case you didn't know) clued me in to a project I'd never heard of before: Nikola, a static website/blog generator.
Click, the blog I write under the auspices of my employer, has moved from Movable Type to WordPress.
The move was prompted by the company's decision to phase out Movable Type, which they've been using since the MT 3 days.
I can't say I'm surprised. While there's a certain flexibility in what you can do in Movable Type (like setting up any number of feeds and kinds of HTML output without regard to themes), the multiblog capability is integrated in a way that WordPress isn't anywhere near, and every damn thing is a static HTML file (if you want it that way), the platform is getting creaky, there's not much of a community, especially compared to WordPress, and the whole WP ecosystem of plugins and themes is pretty much nonexistent.
That said, I got to know Movable Type pretty well, I will miss it, I have to figure out how to build a whole lot of stuff that is easy (and already built in MT).
But there are so many things that WordPress brings to the proverbial table, things I'm learning about as I go, that it's going to be an equally proverbial adventure.
The PyBlosxom blogging software isn't dead, but it's not terribly alive either, plus why I use Ode as my flat-file blogging system of choice
PyBlosxom, a very worthy project that took the Perl-based Blosxom and re-did it in Python, has been slow, development-wise, for a long time now.
In recent months the project was near death, but a new maintainer is at least watching over what's left.
Not that Blosxom is an active, living project, because it isn't.
OK, here's the deal. In Ode I can get any kind of output I want through the project's infinitely flexible theming. In Movable Type I can create any number of custom Javascript output files that draw on the blogging system's database.
So how do I do this in WordPress? I'm looking into child themes (I confess that I've -- horror of horrors -- modified the main theme in a WordPress blog), but I need EXTRA theming. What I need is the ability to tap the blog database for custom HTML output that includes only the elements I want with accompanying HTML so I can display that output on other sites.
It's so easy to do this in Ode and Movable Type. Why is it so hard (or seemingly so) in WordPress?
I don't know what it means (and it could very well mean nothing), but Blosxom is now in GitHub.
Crawl through these files to find out more.
This file in particular says:
Welcome
Welcome to Blosxom 3.0, the future of the Blosxom self-publishing system, coming soon to a computer near you.
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.
I just found out that the search function built into FlatPress does not look at the text of the entries but only at the titles (and possibly the tags; I’ll have to check on that one).
I know this because I was searching for an entry, and it wouldn’t come up when searching for a word I knew was in the body of the entry but not necessarily the title.
It’s not a FlatPress deal-breaker, but bloggers might want to explore the alternatives. I’ve been using the Google Custom Search box on some of my other blogs, and that works very well.