Find on Blosxom.com

Grok Headline matches for Find on Blosxom.com

"with this hilarious montage [note the
French - ed.] - "'You're not going to
find us on vacation, you're going to
find us working'""

"with this hilarious montage [note the
French - ed.] - "'You're not going to
find us on vacation, you're going to
find us working'"" 07/19/2004 08:24 PM

Dust in the Light: "We led this search
to find the truth, not to find the
weapons."

Dust in the Light: "We led this search
to find the truth, not to find the
weapons." 01/27/2004 08:57 AM
"We led this search to find the truth, not to find the weapons." .. SAYS THAT EVERYONE'S MISSING THE STORY .. JUSTIN KATZ .. Quote

dustinthelight.timshelarts.com/lint/000076.html
track this site | 7 links

Blosxom 3.0+2i

Blosxom 3.0+2i 04/28/2004 06:51 PM
I've just uploaded Blosxom 3.0+2i (aka alpha 2). This is a minor update, fixing only a couple of things: permalinking (i.e. requesting a particular entry) now works and an individual entry's path is now normalized (huzzah!), so no more having to figure out whether to put $url$path$fn or $url/$path$fn or $url/$path$fn--Blosxom does that for you.

Blosxom 3.0+1i

Blosxom 3.0+1i 04/28/2004 02:59 AM
I'm thrilled to announce the future of the Blosxom personal publishing system!

(Could that have been any more dramatic? ;-)

I've bundled up the first alpha of Blosxom 3.0 for perusal, fiddling with, and discussion by mature (aka stalwart, brave, Perl-savvy) Blosxom folk with an eye to seeing what the future of Blosxom holds and just how to write plugins for the thing.

It's been massively refactored, all but rewritten, object-oriented, and usable as a CGI script, module, or indeed subclassed. Oh, and I'm afraid it's grown a bit, now weighing in at a massive 15K (slightly less, actually) ;-)

It is by no means anywhere near fully baked and should not be considered in any way, shape, or form, to be ready for deployment. Things will change. Other things will break. If you're not ready for that, you'd best watch from the sidelines. I say this not to be rude, but for your own protection.

Blosxom 3.0 should run right out of the box. Unzip, drop somewhere Web-accessible, and visit http://servername/cgi-bin/Blosxom.pm (or appropriate). You may need to change its filename to Blosxom.cgi to have it run on your server. Blosxom works from its local directory and expects to find al the bits and bobs in its package thereabouts

The current Blosxom 3.0 package consists of:

• The Blosxom module (Blosxom.pm) that may be a) run as a CGI script with about the same effect as running Blosxom 2.0 out of the box, b) subclassed, or c) used as a module, naturally enough.
• A data directory, wherein all entries, flavour components, settings and handler configuration files lie. I've prepopulated this with HTML and RSS templates, some posts (including this one) with which to test Blosxom, and basic settings and handlers files.
• A plugins directory, wherein all plugins live. I've included a couple-three plugins which do little in particular, but provide some idea (until I get to the full documentation) of how plugins work.
• A state directory, wherein to keep an state information used by your plugins.

Blosxom 3.0 will be distributed, eventually, with such a layout (subject to change), some goodly sprinkling of flavours or themes (designers, please do volunteer), a nice collection of modules that'll work well cross-platform and don't require anything more than themselves, and on-board documentation in the form of blog posts.

Please read the on-board docs (in the data subdirectory or visible as the first few posts when you run Blosxom 3.0+1i).

You'll find Blosxom 3.0+1i at http://www.blosxom.com//downloads/blosxom3/alpha/Blosxom_3_0_a 1.tar.gz. Please direct any technical feedback to the Blosxom mailing list. Feel free, also, to discuss it here, of course.

Need To Know Blosxom

Need To Know Blosxom 03/11/2003 09:43 AM
Today's episode of NTK (read: Need to Know), "*the* weekly high-tech sarcastic update for the uk", tracks Blosxom with a succinct, smashing review.

Rael Dornfest's blogging utility BLOSXOM is Perl code
written as when the world was young, and Perl code had
something to prove: two hundred lines of yogically back-bent
hack designed to do one thing, and do it well. You have a
directory. The text files in the directory are your blog
entries, sorted by timestamp. Pop a few HTML templates in
there, and Blosxom CGIs it all into a viewable page complete
with permalinks and other blog miscellany. Now with the
imminent arrival of BLOSXOM 2.0, the script has developed
"look at me! I can put my whole fist in my mouth!"
extensibility. The new Blosxom plugins API is just a wodge
of Perl packages that support a handful of obvious callbacks
and tootle with variables. But it works - well enough to
have spawned over fifty extensions to the basic app, from
automatic smartquotes to trackbacks to debian package tags.
The main script is still just your bog-standard CGI script
(though it can now generate static as well as dynamic blog
pages), and you're still just sticking text files in
directories (although sub-directories now work like
fancy-schmancy Moveable Type-like categories). It's blogging
if blogging was a shell command - right down to its
unpronounceable name.

The Blosxom FAQ

The Blosxom FAQ 10/28/2003 11:06 PM
The Blosxom FAQ is a repository off tips, tricks, techniques, and tidbits gathered and contributed by Blosxom users just like you. I look forward to learning from your enjoyable hacks, chance discoveries, and (yes ;-) annoyances.

Blosxom 3.0+3i

Blosxom 3.0+3i 05/02/2004 04:31 AM
I've been tinkering with Blosxom the past couple of nights and have made some good progress on the alpha. With this release come the following changes:

• A Tag plugin allows arbitrary tags to be assigned to entries, either instead of or alongside Blosxom's native path-based categorization. You can think of it as a personal, family, or workgroup del.icio.us The plugin then allows searching for these tags on the URL-line by feeding a comma-separated list of optional (e.g. cookies,oatmeal), must-have (e.g. +raisin), and must-not-have (e.g. -sausages) tags.
• A Meta plugin populates a $self->{state}->{current_entry}->{Plugin}->{Meta} hash with variables corresponding to meta tags found in the "header" (anything before a blank line) of a weblog post, removing these meta tags from the rendered post along the way. These variables are available to plug-ins and flavour templates as $Plugin::Meta::variablename.
• An EntryType plugin is in answer to Jason Kottke's need for differential post types and correspondingly different renderings thereof. Individual entries may be styled as particular flavours. Specify the flavour of a particular post as a meta-entrytype: tag and the entry will be rendered using that particular flavour's entry.flavourname template component.
• Interpolation of variables at depth (e.g. $Plugin::Meta::via as $self->{state}->{current_entry}->{Plugin}->{Meta}->{via}), thanks to brian d foy for his _interpolate() help.
• In answer to requests for cleaning up the data directory and not having it littered with settings and templates alongside entries, subdirectories (configurable; set to '' to remove) for settings (.settings for settings*, handlers*) and template (.templates for flavour components, themes, etc) at each step in the hierarchy to keep them separate from entries. They're there, useful, yet all but invisible (you most likely have to type ls -la on your system to even see them). They're also then capable of being .htaccess-protected.
• Symbolic link support (via inode - not necessarily best for cross-platform, but we'll see) means never having to put your entry in only one part of your category tree. Of course only one version of each is displayed at render time.
• I moved get_plugins--at the suggestion of a couple of folk on the Blosxom mailing list--to the top of the flow handler list.

Download Blosxom 3.0+3i (aka alpha 3) and give it a whirl yourself.

Blosxom excerpts

Blosxom excerpts 03/08/2004 11:23 PM
My weblog software's design is based on blosxom's, with entries stored in the familiar title followed by body format.  On my longer entries, such as this one, the first element in the body is a div tag with a class of excerpt, something that I parse out with a set of regular expressions.  This approach can be implemented in blosxom as a plugin ...

Blosxom.PHP 1.0RC1

Blosxom.PHP 1.0RC1 08/01/2004 03:20 PM
A port of Blosxom to PHP.

Pagination for Blosxom

Pagination for Blosxom 03/19/2003 10:27 PM
Here's a little something I whipped up last week: BlosxomPaginate...

"Blosxom: Think of it as cat(1) with
stylesheets"

"Blosxom: Think of it as cat(1) with
stylesheets" 03/11/2003 09:43 AM
A simply fab review of Blosxom appears as a sidebar (read: 1/2-pagebar) to an article titled "Building with Blogs" in the March issue of Linux Journal.

In "Blosxom: Think of it as cat(1) with stylesheets," Don Marti writes:

Time to look at Rael Dornfest's Blosxom, which might be described as blogging UNIX-style.
...
The fun part about Blosxom isn't what it does in that first 15 minutes--it's what you'll end up doing to yours in the first 15 days. A bas les cookie-cutter blogs! Vive le Blosxom!

I just love hearing peoples' take-away from their experiences with Blosxom. To some, it's the simplicity of writing, as nature intended, in your favourite text editor. Others can't wait to get their hands on those perl-ish innards. Ever my favourite is "It's like a weblog haiku on my iBook."

Blosxom AdWord

Blosxom AdWord 10/28/2003 11:06 PM
Blosxom has its very own Google AdWord--and it's not mine.

Sponsored Links

we know blosxom rocks
does your webhost even know what it
is? try us, cgi runs as your user
www.phpwebhosting.com

Blosxom 2.0 beta 1

Blosxom 2.0 beta 1 03/11/2003 09:43 AM
I suspect there's really no need for preamble. If you've been reading my blog over the past few weeks, you've more than seen it coming.

Here's Blosxom 2.0 beta 1, replete with sample plugins for:

RSS 1.0, Weblogs.com Ping, Foreshortened, Tiki, Readme, Buy from Amazon, Lucene-Powered Search, and TrackBack count.

:-p

Blosxom 2.0 beta *3*

Blosxom 2.0 beta *3* 03/11/2003 09:43 AM
Blosxom 2.0 beta 3 is out . For a list of changes, see my Blosxom mailing list posting.

Blosxom 2.0 beta *2*

Blosxom 2.0 beta *2* 03/11/2003 09:43 AM
As promised, I've wrapped up another bundle of Blosxom joy this weekend... Blo sxom 2.0 beta *2*. For a complete list of changes since beta 1, read my posting to blosxom@yahoogroups.

The biggest improvement by far is the ability to swap in a replacement for the default routine that finds all of your Blosxom stories. Exemplifying the sort of thing you can do with this added functionality, I've bundled a new entries_index plugin which preserves creation times on stories, no matter how many times you edit them.

Current size of blosxom.cgi: < 13k ;-)

Blosxom and Bricolage

Blosxom and Bricolage 05/19/2004 01:24 PM
I just love stumbling across stories of integrating Blosxom with other applications or bits and bobs of software. My good friend David Wheeler of Bricolage fame just pointed me at discussion of using Bricolage as a front-end/sidekick to Blosxom:

I created a new output channel (Blog), which simply outputs documents with .blog extension; I then created a BlogStories element type (story type) and a BlogStory element of BlogStories type, with primary OC Blog and four allowed subelements . . . The main site is accessible through http://www.example.com while the Blosxom scripts answers requests for http://blog.example.com.

Blosxom 2.0 beta *4*

Blosxom 2.0 beta *4* 03/11/2003 09:43 AM
Blosxom 2.0 beta 4 is out . For a list of changes, see my Blosxom mailing list posting.

The biggest change is a sort() hook, allowing you to override the default sort routine when it comes to rendering items on a page. I used this in the Blosxom Plug-in Registry, sorting by category (aka path) and plug-in name.

Hello Kitty says, "Hello Blosxom"

Hello Kitty says, "Hello Blosxom" 12/17/2004 06:28 PM
Hello Kitty has a blog. Ms. Kitty blogs (in Japanese, of course), moblogs, links to her friends, writes of her latest jewelry likes and dislikes, and so on--just like any other blogger worth their salt ;-).

As if that weren't enough, Jo i Ito pinged me when he noticed that the blog, a joint Sanrio/NTT Data project, is running on Blosxom. Take a gander at the RSS output at http://diary.hello kitty.ne.jp/blog/index.rss:

<xml version="1.0"?>
<!-- name="generator" content="blosxom/2.0" -->
<DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" 
"http://my.netscape.com/publish/formats/rss-0.91.dtd">

Blosxom.PHP 1.0 pre2

Blosxom.PHP 1.0 pre2 06/03/2004 06:39 AM
A port of Blosxom to PHP.

Announcing Blosxom 2.0

Announcing Blosxom 2.0 10/28/2003 11:06 PM
I'm thrilled to announce that Blosxom 2.0 has been released today. For those not in the know, blosxom (pronounced "blossom") is a lightweight yet feature-packed weblog application designed from the ground up with simplicity, usability, and interoperability in mind.

The biggest change in this latest incarnation of Blosxom is a plugin architecture, allowing the core of Blosxom to remain small, sleek, and simpler-than-pie while providing room for extension and integration. The Blosxom Plugin Registry is already home to some 140 plugins ranging from authentication to Google search, click-through tracking to writebacks (read: combination talkbacks and TrackBacks).

There's also a brand new Blosxom for Mac OS X Installer, the simplest way to get Blosxom on your laptop, desktop, or closet Mac without any of the muss or fuss of installing it by hand. A couple-three clicks of the mouse and it'll skip lightly through the nitty-gritties, installing Blosxom itself, some sample flavours, documentation, and some useful plug-ins.

Also launching today is the new and improved blosxom.com. The site features updated, augmented, and just plain new documentation and an easier path download, installation, configuration, and blogging -- not to mention the snazzy layout. And the whole kit and kaboodle is built on and powered by Blosxom using nothing but what comes on board and the power of a selection of user-contributed plugins; for the niggly-naggly details, take a gander at the colophon.

Karma++, Brownie++, and gold stars to the Blosxom users and abusers on the blosxom mailing list for their patience, bug-fixes, suggestions, and plugins. You truly are a fabulous community within which to hack and learn.

At the Forge: Blosxom

At the Forge: Blosxom 05/17/2004 03:16 PM
Linux Journal ran a second piece on Blosxom in its May issue (the first was a nice sidebar, "Blosxom: Think of it as cat(1) with stylesheets", back in February of 2003). In "At the Forge", Reuven M. Lerner describes Blosxom as "No modules, no SQL, no hassle"--precisely!

I initially wrote off Blosxom as an unrealistic tool for blogging, assuming that its small size was indicative of its abilities. But Blosxom's power is not only in its strong feature set but in the way it allows us to mix and match functionalities.
...
Blosxom is a powerful tool for creating a Weblog; it's more than it might appear at first glance. Blosxom consists of an easy-to-install, easy-to-configure CGI program written in Perl, but its true power lies in the fact that it lets you change every part of the display through a combination of flavours (display templates) and plugin routines.

The one complaint Mr. Lerner had is addressed in the latest alpha of Blosxom 3 (3.0+4i, due out shortly): "The fact that Blosxom keeps all entries and flavours in a single directory is a bit disturbing to me and makes me wonder about the program's scalability. Even if my filesystem and Perl can handle that many files without too much trouble, do I really want to wade through them all?"

The new architecture keeps settings (settings, flow hanlders, etc) and templates (flavours, themes, etc) in their own subdirectories at both the base level (e.g. blosxom/data/{.settings,.templates}) and (optionally) anywhere in your hierarchy you wish to mix things up a bit (e.g. blosxom/software/{.settings}). By prepending these directory names with a ., they're all but invisible unless you're looking for them. Of course this is all completely configurable.

Blosxom Plugin: atomfeed

Blosxom Plugin: atomfeed 12/11/2003 04:48 PM
I've been meaning to get to this for some time now and finally had a few moments to rub together and get it done. Atomfeed is a Blosxom plugin that provides an Atom feed of your site. The plugin has all you need right on-board, including the appropriate flavour template components and a couple-three optional configuration directives. You simply drop it into place in your plugins directory and point your browser at /index.atom (or append it to any path in your blog hierarchy, of course). Check it out live at http://www.raelity.org/index. atom.

Blosxom Plug-In: Rating

Blosxom Plug-In: Rating 10/28/2003 11:06 PM
I've been meaning to whip this up for some time now and finally got around to it. The rating Blosxom plug-in generates numerical, textual, star, and graphical representations of a rating (specified in your weblog post as meta-rating: n using the meta plug-in).

Use it for rating movies, books, sites, toys, devices, articles--whatever you're pointing at or talking about in your weblog post. You can even change the rating scale on a post-by-post basis.

A meta-rating: 4 generates a numerical 4, textual <===O=>, star ****, and graphical representation you can see in action here and here.

Blosxom 2.0 Release Candidate 1

Blosxom 2.0 Release Candidate 1 03/19/2003 10:24 PM
As I head toward a 2.0 release of Blosxom, I've dropped the "Beta" moniker in favour of "Release Candidate." Take a gander at the release notes and download RC1. Also, be sure to check out my latest plug-ins, sporting hooks into the new functionality in RC1.

Blosxom Plugin: Theme

Blosxom Plugin: Theme 10/28/2003 11:06 PM
From a Blosxom mailing list conversation with the thematically-talented Bryan Bell about his interest in creating themes for (and porting themes to) Blosxom comes the theme plugin.

The idea is to make it dirt-simple to create entire themes (template, images, stylesheets, javascript source, etc) for Blosxom-powered blogs, installable by simply unzipping the theme archive to the appropriate directory. The plugin further pulls all the usual flavour templates into a single file, making it easier to edit Blosxom flavours in WYSIWYG HTML editors.

I'll soon be building a Blosxom theme registry a la the plugin registry and faq. Judging from the bounty of Blosxom plugins (161 at the time of this writing), I expect we'll see a veritable cornucopia of creative Blosxom themes.

Blosxom-Branded Knicknacks

Blosxom-Branded Knicknacks 12/11/2003 04:56 PM
Ever wish you could have Blosxom with you wherever you go? Over your morning coffee, at the gym, break room at work, changing your baby's onesie. The Blosxom CafePress store has you covered (literally) with more Blosxom-branded knicknacks than you can shake a stick at.

Thanks to the spyrograph-like talents of Matt Barger and incomparable artistic flair of Bryan Bell, that very special Blosxom logo is now available in vivid colour for you to sport with glee. You'll also notice the nifty new Blosxom slogan, "blog for the zen of it," a Bryan Bell adaptation of my original slogan--and much, much better.

I pulled this together after the second request for Blosxom-branded brickabrack, the latest by Dave Walker on the Blosxom mailing list:

As I sat at my desk drinking my morning coffee from a styrofoam cup, I thought to myself, "gee, it sure would be nice to have a Blosxom coffee mug, maybe with the pretty, subtle Blosxom greyscale blossom logo." It's 8 hours later, and I still think it's a good idea.

I've marked each item up only a buck or two, all of which will be donated to my local schools to promote math and science education in memory of those brave souls who died w hen Columbia fell from the sky.

Blosxom Plug-In: interpolate_fancy

Blosxom Plug-In: interpolate_fancy 10/28/2003 11:06 PM
interpolate_fancy is a powerful little Blosxom plug-in I whipped up last night. It overrides Blosxom's far simpler to use, but more limited, default default interpolation routine--that's the bit that pulls in values for variables you specify in your Blosxom templates.

The plugin builds on its predecessor, interpolate _conditional, conditionally including bits of text and template variable values in pages. But the syntax is cleaner and conditions now include: defined, undefined, equal to, not equal to, less than, greater than, like and unlike (regex). Here's a taste:

<a href="<$url /><$path />"><$path
/></a>
<?$path><a href="<$url /><$path />"><$path
/></a></?>
<?!$path><a href="<$url />">home</a></?>
<$writeback::count /> 
   <?$writeback::count eq="1">writeback</?>
   <?$writeback::count ne="1">writebacks</?>
<?$writeback::count lt="5">few writebacks</?>
<?$writeback::count gt="50">oodles of writebacks</?>
Howdy, 
   <?$user::courtesy like="^(Mr\.?|Sir)$">Sir</?>
   <?$user::courtesy like="^(Mr?s\.?|Miss)$">M'am</?>
<?$path unlike="/(Film|Literature)">no review</?>

The plugin also sports actions (read: subroutines or methods). At any point in any of your Blosxom templates, you can call a particular plugin's method, optionally passing arguments as key/value pairs stated as XML-style attributes. Like so:

<@plugin.subroutine arg1="a" arg2="bee" /> produces no output
<@plugin.subroutine arg1="a" arg2="bee" output="yes" /> produces
output
<@encoder.encode encoding="Latin1" output="yes">pass this content

I'm still working on the recursion/chaining, allowing for things like "some content">plaintext>foreshorten(50)>babelfish::translate. The first plugin I'll be writing using interpolate_fancy is for atom (or whatever it's called a few minutes from now).

Blosxom Plug-in Docs

Blosxom Plug-in Docs 03/11/2003 09:43 AM
After much ado and not a small amount of fiddling and honing over the past couple of evenings, I've a version of Blosxom 2.0b and sample plugins I'm ready to start seeding.

Despite expecting it to be in flux for a while, I wanted the first version of the Blosxom Plugins API to be good enough to provide a nice starting point for discussion and further development.

I've some mild cleanup to do on the beta release and anticipate finishing up and putting out a package Thursday evening.

I spent this evening massaging the zen of Blosxom plug-ins into some decent documentation rather than simply leaving interested parties to muddle through the source. I believe I've done a rather decent job on them, but if you notice anything confusing, missing, or just plain odd, please do let me know. You'll find the docs here.

Blosxom Plug-in Registry

Blosxom Plug-in Registry 03/11/2003 09:43 AM
Blosxom now has its own Plug-in Registry, sporting a growing number of Blosxom plug-ins. The registry itself is built of Blosxom with just a few tweaks which will make it into bet a 4, due out shortly.

There currently exists no front-end to the registry, but it is on its way. In the meantime, please do let me know of new Blosxom plug-ins either directly or by posting to the Blosxom mailing list.

And, of course, you're invited to keep abreast of the latest Blosxom plug-ins thanks to the wonders of RSS.

Two more Blosxom Plug-ins: config and
isp

Two more Blosxom Plug-ins: config and
isp 03/11/2003 09:43 AM
A couple more Blosxom plug-ins I whipped up... co nfig overrides Blosxom's inline configuration settings on a per-directory, per-flavour, and per-directory-per-flavour basis (more detail) and isp, designed for the ISP looking to provide Blosxom weblogs to all of its users, traps URLs of the form /~username/weblog, setting an appropriate user-specific data directory.

Be sure to check out the growing collection of contributed plug-ins in the plug- in registry.

Add preview functionality to Blosxom

Add preview functionality to Blosxom 05/28/2004 11:14 AM
A fair number of people use Blosxom, Rael Dornfest's weblog software, for its simplicity and power, and given Movable Type's recent change to its pricing structure, even more people may do so soon. The major drawback, IMHO, ...

Inline::Python Blosxom Plug-in

Inline::Python Blosxom Plug-in 03/19/2003 10:24 PM
Here's an utterly naughty little something not for the faint-of-heart... inline_python is a stub plug-in for anyone wishing to try their hand at writing Blosxom plug-ins in Python. A hearty "yeehaw!" to the creator of the first Python Blosxom plug-in. ;-]

Blosxom WriteBack Plug-In Out of the
Oven

Blosxom WriteBack Plug-In Out of the
Oven 03/11/2003 09:43 AM
My WriteBack plug-in -- a Comments/TrackBack combo -- is available for your plugging pleasure.

I've also WriteBack-powered the Blosxom Plug-in Registry so as to allow running commentary on and TrackBack pinging of plug-ins themselves.

Karma++ to Ben and Mena of Movable Type for their inspiring work on TrackBacks!

Blosxom Writeback Plug-In 4/5 Baked

Blosxom Writeback Plug-In 4/5 Baked 03/11/2003 09:43 AM
My comment plug-in has blosxomed, if you will, into a combination of comments and trackbacks... writebacks.

As ultra-simple as its predecessor, its about as Blosxom zen as you can get. I'll be releasing it after a day or so of trial pings and comments. To give it a whirl, click the blue 'writebacks' link associated with this, or any, weblog entry. Or, if your weblog tool is TrackBack-aware, the usual TrackBack auto-discovery sugar is embedded into the HTML of this page.

Major new Blosxom version in alpha

Major new Blosxom version in alpha 04/28/2004 04:45 AM
Rael Dornfest has come up from air after a prodigious bout of writing and editing, and promptly produced an alpha of the next major rev of his brilliant blogging tool, Blosxom:

It's been massively refactored, all but rewritten, object-oriented, and usable as a CGI script, module, or indeed subclassed. Oh, and I'm afraid it's grown a bit, now weighing in at a massive 15K (slightly less, actually) ;-)

Link

Some nice /.-posted comments about
Blosxom

Some nice /.-posted comments about
Blosxom 05/17/2004 03:16 PM
While unfortunately associated with a /. post on the fracas around MT's new pricing scheme, I came across some nice comments on Blosxom I thought worth pointing at.

Blosxom Comment Plug-In 3/4 Baked

Blosxom Comment Plug-In 3/4 Baked 03/11/2003 09:43 AM
I whipped up 3/4 of a comment plug-in for Blosxom last night. I say 3/4 only because I'm putting the final touches on the associated flavour templates (including commentsinRSS).

It's ultra-simple, uses existing flavour methodology to style the comments themselves, has room to expand to support TrackBacks, is about as RESTfu l as can be (for those of us that care about this sort of thing), and requires nothing but the plug-in itself and a little flavouring fun.

Give it a whirl here.

Blosxom WriteBack Plug-in Updated and
ZIPped

Blosxom WriteBack Plug-in Updated and
ZIPped 03/12/2003 02:49 PM
There's a shiny new version of my Blosxom writeback plug-in sporting a ZIP file replete with the plug-in itself, full complement of sample flavours, and Quick Start instructions. Also, the plug-in now creates your writeback directory for you, setting appropriate permissions along the way -- making installation a snap!

Wikilike Blosxom Plugins: textile 2 and
kwiki

Wikilike Blosxom Plugins: textile 2 and
kwiki 10/28/2003 11:06 PM
Todd Larason has released a textile 2 Blosxom plugin, a wrapper around Brad Choate's mttextile, in turn an implementation of Dean Allen's textile 2 powerful text formatting engine.

I finally had a couple-three minutes to rub together and used them to create a quickie kwiki plugin which uses Brian Ingerson's CGI::Kwiki as a formatting tool for Blosxom weblog entries.

Between the text-formatting options offered by the textile 2, kwiki, or tiki plugins, wikiword functionality of the wikiwordish plugin, and in-page editing of the wikieditish plugin, we've a nice set of tools for building Blosxom-based a fully-categorizable WikiWeblog.

In fact, paranoidfish< /a> did a little outside the script thinking, combining CGI::Kwiki and Blosxom in a way that let's you publish a Kwiki page to your Blosxom blog.

The similarities between CGI::Kwiki and Bloxsom are obvious - both are brilliantly simple, and both use plain text files in a directory as a file system. So, I was wondering if it was possible to use CGI::Kwiki as a backend for Blosxom in some way. Unsurprisingly, the answer is yes.

I did some similar fiddling a while back, sharing a data directory between Blosxom and moinmoin. Every wiki page was a blog post; every blog post a wiki page.
Grok Description matches for Find on Blosxom.com
GrokA matches for Find on Blosxom.com

Find on Blosxom.com

The following phrases have been identified by the grok system as matching this entry: