Posts Tagged ‘frabjous’

Welcome to my humble abode

Hello. If you’ve been here before you’ll have noticed that I’ve changed things a bit; moved the furniture around, repainted the skirting boards, stripped the old wallpaper and removed the artex from the ceiling. Hope you like it. I’ve gone for a much simpler, more stripped-back look-and-feel this time around. I’m not interested in having [...]


Wailly wailly

Well, it looks like I jumped the gun with my last post. Turns out that the shiny media features that WordPress 2.9 has, and which I got so glum about not having in Frabjous have actually been in Frabjous for about a year. And I wrote them. Yes, I fail. True, they’re a bit more [...]


Migrating to WordPress

Looks that way, anyway. It just happens to need to do what I need and I don’t have the time to hack those features into Frabjous, since they’re major work. Yes, I hate myself. Yes, running PHP on my server is like allowing a busload of hackers into the Bytemark datacentre (with apologies to Chris [...]


A period of transition

This site is now running primarily on Frabjous, with only the bits than need my gbc-specific cusomisations still running out of my old gbc tree. Please forgive any instability that this causes. I haven’t spotted any yet, but you never know… [Edit] Reverted because of some crazy looping problems; please ignore this post.


Tumbling

I’ve always loved the functionality of Tumblr. In fact, I have an account there, though I’ve never used it. I wonder if I should add its functionality to Frabjous. Or, perhaps better still, I could use the Frabjous RemoteFeeds architecture to allow Tumblr accounts to be aggregated into a Frabjous blog. Hmm. This is now [...]


Blog engines stuff and things

A few months back, when I was on a Launchpad Bugs sprint in Vilnius, Tom and Gavin asked me whether I’d thought about open-sourcing the engine that runs grahambinns.com. My answer then was that I’d thought about it but never done it because: It wasn’t very good The code had a lot of grahambinns.com-specific code [...]