=== Thu, 31th ===
+==== News Feed ====
+
+Today Rasky suggested that we could use an RSS feed to notify
+about new articles in the blog.
+
+I wanted to fulfill the same purpose, but with a totally
+different approach: use git-send-email to notify a mailing-list
+and tell people: "hey, just subscribe to the list!".
+
+My version is surely too complicated because it employs
+a chain of 4 different programs (pikiwiki -> git -> git-mail -> mailman).
+But I like that it can be done without even touching the wiki
+engine.
+
+A middle-ground solution could be using gitweb's own
+RSS feed:
+
+ http://bender.codewiz.org/wikigit/wiki.git?a=rss
+
+But as Rasky notes, this would send notifications
+also for minor edits: real blog apps would only
+bother you for new articles.
+
+So, maybe we should filter only changesets that
+contain a new level 3 header... Hmmm... This
+can't be done with gitweb, I'm afraid.
+
+We live in an era where we can make very cool
+things with very little effort. I could hack
+this versioned wiki engine in just 2-3 days
+because I could pick the existing PikiPiki and
+combine it with the existing Git versioning
+system.
+
+This brings me to the point: the really hard thing
+in software design is choosing the right ingredients
+for your sausage. Because there are many ways to
+bake a pizza, but only a few of them have the
+quality of being tasty, healty, dietetic, cheap
+or whatever. And usually, even a good design...
+err... receipe requires you to choose a few of
+these qualities you care more.
+
+'''Q''': What do you think is the most elegant way to
+obtain useful notification from this blog?
+
+You can choose whatever technology to deliver some
+kind of "notification". You can also use any
+sensible definition of the words "useful" and "elegant".
+
+
==== Hop hop! ====
Today I typed {{cvs up -dP}} to update Gnash from CVS.
projects / wiki.git / commitdiff