If you’re not part of the problem, you’re part of the system.
Welcome xkcd fans! April Fool and all that!
Looks like Randall’s shaming me into doing an update of the long-neglected CLI2. I wish he’d have let me know, my hosting tends to tank at the drop of a hat. I’ll get to it when I get a chance (employment interferes), but it’ll be more like CLI3.
If you want the WordPress theme as-is, the link is at Google Code.
… but maybe WordPress isn’t the platform I want it to be on anymore. WP is just going too far into GUI territory. Soon — after a couple or six projects at work, maybe in a year — I’m thinking of stripping down this whole “blog” idea, making a Blog OS, running that through a 6502-assembler-to-Javascript converter, and boom.
Could be just the Jameson’s talking though. I’m not even any sort of a blogger. I just get no fame as a systems programmer for the university library. With CLI, though, I was on top of the world. It made me, like, $54. I could use some of that sweet dough again. Maybe when keycodes get standardized across browsers… bloody Safari.
But I’ve resumed hacking on CLI. I’ve decided to sample some of the jQuery Kool-Aid and so far, so good. It doesn’t solve the keyboard events insanity completely, but we’ll see how it goes. Also I intend to add a few API-ish features like Google searches/maps, last.fm feeds, that sort of thing. Are there any other features you folks want?
Post #404! Something appropriate about that.
Michael Fogus, d.b.a. Minotaur Computing has generously volunteered to take over the development and maintenance of the CLI project. I’ll still be following it, and contribute to it, but basically the theme has become a bit of a drag on me and it will be good for new (and more accomplished) leadership to take it to the next level. He has already set up a new repository on github. With new blood comes new directions: already there is talk to expand CLI beyond WordPress, so that it will become more of an alternative, pluggable interface to Web services that supply public APIs. This means you could potentially make a site that allows mixing and mashing information from e.g. Facebook, MySpace, Google, Yahoo, last.fm, Twitter, or anything else that anyone wants to write a plugin for, all through the command line. WordPress support might not happen via the theme engine, but rather through its XML-RPC interface. It will need all kinds of exciting new development: off the top of my head, some sort of writable “filesystem”, a module system better than the current “/usr/bin” setup, a standalone configuration system (i.e. not an extension to the WordPress “presentation” menu), an umbrella scheme for storing disparate information so that interoperation can take place… Here’s some things I’m fantasizing about:
twitter.login thrind && twitter.subscribedFeeds | googleMaps.locate at the prompt to get a map of where all of my tweet-friends are locatedwith wordpress; latest|email joeblow@foo.bar subject="My latest post" to set wordpress as the current application, then get the latest post and email it to a friendrss --source "http://feeds.boingboing.net/boingboing/iBag" --titleonly| grep -vi steampunk to display the Boing Boing feed with titles only and with any steampunk references removed
wget http://wherever.com/something-neat.html; googleTranslate --source=it --to=en something-neat.html | wordpress.post --title="Look what I found (translated from Italian)" --category="Fun Stuff"; rm something-neat.htmlOf course, things might not end up exactly like these examples, but it sure is fun to think of the possibilities. I’d like to hear new ideas — share them at the Google group.
Contents © 2010 Rod McFarland. It's made with WordPress.