13/12/2009 at 18h58
You have been running a Typo blog [since 2005][since], but you still can’t
quite get your Apache configuration right. In particular, you still get the
Not found: http://www.matijs.net/blog/2005/07.html/24/from-bryar-to-typo
Note the weird
23/01/2008 at 06h36
It’s a new year! Time for more resolutions. I can’t believe that’s actually two years ago.
Yes, my blog has been neglected, but not for want of anything to write about. Oh, there are so many things I have an opinion about. But always, it’s the question, is my opinion interesting, new, well informed, etc? And can I write something sizable about it? Not conductive to writing every monday (recently replaced by sunday, but I bet you hadn’t guessed). Maybe I should try less hard to be reasonable.
Oh yeah, e-mail is getting better, mainly thanks to the Inbox Zero articles.
What I really want to be doing: I still don’t really know, but let’s look at what I might blog about:
- Size is the Enemy, leading to the issue of abstractions in programming languages.
- 80/20, or the problem of getting your average Java/.NET programmer to really learn and use new things (e.g., new methods of abstraction).
- Lots of new languages are popping up, all running on some VM or other (e.g., Scala, Nemerle, Boo). Where’s the development in regular compiled languages?
This surely points in some direction, but some weighted average will have to be taken to find out what that direction is.
I did manage to quit the job that was definitely going in the wrong direction, so there’s a plus.
Oh, you wanted new resolutions? Hm, let’s do some:
- Uncluttered house
- Learn Japanese
- Finish more software so it’s releaseable
18/06/2007 at 13h13
Last week, I did some work on my website, upgrading to the latest Typo trunk and Rails 1.2, and changing from
mod_fcgid to a Mongrel cluster.
Last Friday or so, I rebooted my server. Unfortunately, I had neglected to make the Mongrel cluster start at boot. So for the past weekend, all you have seen here is a Service Temporarily Unavailable message.
25/03/2007 at 13h05
Daring Fireball talks about about an interesting post by Tantek Cilek about Human Interface Design. It’s true that there is some cognitive load in posting a blog entry as opposed to just answering What are you doing?
Partially, that resistance is good. Like forums, or blog comments, the Twitter entries are mostly like noise. A soothing background hum that lets you know other people are alive and going about their business. Unfortunately, that business is often uninteresting in the long run. So how long are we willing to store it, even for ourselves?
On the other hand, it is annoying that I have to come up with a title that covers this little post that wanders all over the place. Or that so many thoughts end up as half-finished posts in my drafts pile.
22/10/2006 at 11h23
The less said about it the better. I just blocked three IP ranges completely. I don’t really like to take these kinds of measures, for two reasons:
- I don’t want to block legitimate access to my web site.
- I don’t want to spend my days adjusting my firewall, adding rules whenever new spam seeps through the cracks.
Since I was spending my days cleaning up trackback spam, reason #2 stopped applying. There also didn’t seem to be any legitimate access from the blocks in question.
Damn Spam has more details on these particular spammers. You can see they’ve been at it for a while now.
Before, I only blocked one IP address. It was from a company called Webrescuer with a very impolite bot. Aparrently, being impolite wasn’t a very good business model, as they seem to be gone now. I removed the block.
26/03/2006 at 14h37
Why we need Atom now
by Tim Bray (via
once again brought the horrors of RSS to the front of my
working memory. I will not elaborate here, but the main problem seems to be
that there are nine versions of RSS, and even
more implementations. The result is that you can never get things right.
Atom to the rescue.
Not wanting to be the
Bitch and Moan But Never Does type,
I removed all links to RSS feeds from my web site. The remaining links are
all Atom feeds, but the word Atom will not be in the link text, to
facilitate the fading of technical details into the background.
It’ll just say feed.
I will probably add the new standard feed icon.
The RSS feeds are still there, of course, since
I want my URIs to be permanent.
27/08/2005 at 18h13
For many reasons, I like to customize the typo program code a little. Much, but not all is customizable by using themes.
I keep my version in a local repository, and I’ve just updated to typo 2.5.5. Here is the way to do these updates, partly so I can remember it myself.
[This post has been updated because the given method didn’t really work properly.]
I have set up svk to mirror typo’s svn repository, created a local copy and checked it out using, like so (this is from memory, so use caution):
svk mirror svn://leetsoft.com/typo/trunk /typo/mirror
svk sync /typo/mirror
svk copy /typo/mirror /typo/local/trunk
svk checkout /typo/local/trunk
To update, I use
svk sync -a
to sync all my mirrors (currently, that is just the typo mirror). Then I can go to my working copy and say:
svk merge -r <rev1>:<rev2> /typo/mirror
rev1 is the revision I previously updated to, and
rev2 is the revision corresponding to version 2.5.5.
There are two problems with this: One is, that you have to remember the last synced version. That’s easy if you put it in the commit messages. I didn’t know this, so I didn’t put it in.
The other problem is finding out what revision corresponds to release 2.5.5. This turns out to be impossible without mirroring the whole repository. Then,
svk info will give you the information you need. Using
svn info on the remote release directory gives this:
[matijs@pomme] svn info svn://leetsoft.com/typo/tags/release_2_5_5
Repository Root: svn://leetsoft.com/typo
Repository UUID: 820eb932-12ee-0310-9ca8-eeb645f39767
Node Kind: directory
Last Changed Author: scott
Last Changed Rev: 530
Last Changed Date: 2005-08-17 00:52:10 +0200 (Wed, 17 Aug 2005)
All this tells me is that it’s a copy of some release before 530. That’s basically useless. It’s through sheer luck that my current typo copy is actually based on release 2.5.5.
24/07/2005 at 18h26
As of yesterday, my blog runs on Typo. All in all, I have been quite
satisfied with Bryar, but it was
time for a change.
I like Bryar because it is simple (no frills, entries are stored as
files), and yet easy to customize (to change the layout there's basically
one template to update). In addition, it is written in Perl, a language
that I like, and that I'm fluent in, so getting it to
work the way I wanted was easy. So, I'm happy that I chose it a year ago.
A combination of events lead me to change over to Typo.
24/01/2005 at 19h59
People who visit this site more often than once may have noticed that I changed its layout. It took a lot longer than I expected: It's easy to just whip something up that looks nice, but it's much harder to take a thought
sketched on a piece of paper and make that happen in CSS. It's harder still if you want to make it work in
In addition to the change of layout, I did a redesign of the URLs my
A new design
The result is much as I
originally imagined it: a paper border with navigation links, floating
above a paper background with the main text. However, the paper was
supposed to be darkish, with a glow coming from underneath the border
illuminating the lower sheet.
Based on Simon Cozens' version of the rounded border layout, I
first produced a nice resizing
border layout. Unfortunately, it only works with browsers that support
:after pseudo-elements. Also, I still
had to add the paper look, and I really wanted a two-column layout.
I took a stroll around the css Zen
Garden for some inspiration, and found most designs use a fixed-width
layout to underlay their columns with an image that provides the
borders and decoration (The design
called Verdure is an example). So, I decided not to worry about
possible 300dpi display technologies of the future, and use a fixed pixel
After some initial fumbling with floats I decided I needed to actually
know how they worked instead of doing cargo-cult CSS design.
The autistic cuckoo was helpful
enough to explain both floats
and the different kinds of positioning
Possibly the last time I'll do IE hacks
Since I had given up on my Amazing Resizing Frame anyway, I
decided that I should make the design look as intended in Internet
Explorer as well. After all, about half of you, dear readers, still seem to
be using that piece
of crap. So, I had to find out:
- What my site looked like in different flavors of IE, and
- How to make it look the way I wanted it to look.
Now I don't have IE running at all, so I had to bug Thomer to send me
screen shots from IE 6, and send more screen shots whenever I changed
something (I tried using ieCapture, but it seems to be permanently overloaded). Then, I had to bug someone at work who has IE
5.5 running to see what that looked like.
To actually get things to look properly, I made great use of How to hide CSS from browsers, and Position is
Everything, a great repository of browser quirks.
Truly permanent links
While checking the validity of my HTML, I came across a tip from W3C about
choosing URIs. Now, I don't even want to understand the
difference between URIs, URNs and
URLs, but it was still very useful. So, now all (user-visible)
URIs are truly permanent, and as a bonus, they don't have file
type extensions anymore (the ones with extensions are properly redirected),
so I can safely serve up my ancient blog archives in the
file-format-du-jour when I'm 205 (I mean, it's not like the cure for aging
isn't just around the corner).
And when I do really remove stuff, I promise I'll pronounce it gone.
To create my background, I took a picture of some nice-looking paper and
processed that with the GIMP. Jeffrey Zeldman showed me that it's
possible to create a convincing floating paper effect using simple
Virtuelvis explains rounded corners too. Very nice for putting things in a box. Very much needs a
Blafoolia is a word I made up that Google doesn't know.
25/11/2004 at 23h42
All this time, it turns out, people using IE5.5 (36 so far this month),
and perhaps IE5.0 (44 so far this month), have been unable to read my
website: The left and right sides of the text were simply cut off. I knew
IE6 didn't show the vertical borders, but at least it showed the whole
Somehow, it feels similar to suddenly finding out you've been walking
around all day with mismatched socks, or a torn shirt — assuming
those things weren't part of your fashion statement. It's simply a little
embarrassing. Anyway, it should all look fine now. The vertical borders
even show up in IE6.
Oh, and I'm working on a new layout, so here are samples before and after, just in case the site
looks completely different when you read this.