Let’s say I could have my dream blog engine. How would that be?
– it would let me easily copy the whole blog to a new server when I decide to change hosting providers.
– I wouldn’t have to worry for database or other updates if I decide to abandon it
– I would be able to keep a copy of my posts localy
– I should actually have a local copy of *all* my content, including photos of videos posted there.
– It would use a version control system for my content, like git.
– It would allow me to create a folder (a real, file system folder) drop in it a bunch of photos, and it would create a gallery and a post from it.
– It would poll twitter and friendfeed for my activity and pull it back to my blog
– I should be able to send it an email with attachments (ex. a couple of photos and mp3 files), that would be automatically extracted to a folder, and all of them would be bundled in a single post, using the title of my email and its body text.
- I would just have to copy my latest podcast episode MP3 file to it, and it would read the id3 tags and automatically create a new blog entry, with enclosures and all.
- I should be able to easily script crazy things for it, in any language, from python to C -even bash.
That’s why I’m building bucket3.
It will only do very few of the above mentioned. But it will also give developers and sysadmins the tools, the environment, where they will be able to easily add functionality “the UNIX way”: by scripting and gluing together old and new tools.