Recent Posts

That's a third show booked! This means that, as I hoped, I'm going to manage at least one show a week for the Fringe!

Now, this one could be seen as a cheat, sorta, kinda. I've seen this show before. But I liked it so much last year I have to see it again! The odd thing about it was it's not something I would have gone for on my own, it's technically not really my thing, but I got talked into it and I'm so glad I was!

So a year back Mariëlle told me about this wrestling show at the Fringe and how she wanted to go but nobody else was interested and I was all "yebbut wrestling though?" and didn't think much more about it. Eventually though, after some persuasion (I mean, an hour or so at a show and some beers afterwards, how bad could it be really?), I agreed to go. I expected to find it meh.

Holy shit was it so much fun! Like, seriously so much fun. I'd never realised that wrestling was the best way to tell the tales from Norse mythology; turns out that wrestling is absolutely the best way to tell the tales from Norse mythology.

So we're off back again this year. All booked, not this weekend, the weekend after.

There might even be a beer afterwards. Perhaps not quite so many as last year though.

This evening I've spent more time working on the planned complete remake of my personal website, in this case "porting" over many of the files that made up the old "miscellaneous stuff" section of the site. If I'm honest, most if not all of the things in there are no longer relevant (like: who really needs a shell script to make gnuplot plots from files pulled off a 1990s-era Garmin handheld GPS unit?), but I thought I'd keep them kicking around "just in case".

One wee section I wasn't going to get rid of though was my scans of three pages from a UK magazine called Personal Computer News. These contain Grid Bike; a game I wrote for the VIC-20, all in BASIC, and got published. For my efforts I got a huge cheque for £40! If that doesn't seem like much to you, trust me, to 1983 me this was huge.

I bought a 16k RAM pack with the money.

Funnily enough, while trying to improve some of the links in the text, I decided to see if there was now an archive online somewhere and, sure enough, there is: in the obvious place. This means that my web site isn't the only copy of my program on the net. If you go to the December 21st 1983 edition and turn to around page 84, there I am!

At this point I'm almost tempted to try and get an emulator up and running and get the code going again. How much fun would it be to add a video to my YouTube channel, of me playing one of the very first games I wrote?

Late on last year I wrote about a bunch of new things that I'd added to PyPi, things mostly kicked off by an early dog-fooding session we had at textual HQ. Since then I've been slowly doing my best to keep the applications up to date with Textual.

As much as possible we try and not make breaking changes with the framework, but at the same time it is still 0.x software and there's still new ways of doing things being designed so there's going to be the odd break in approach now and again.

Unbored, my kind of silly self-populating TODO list application, has been sitting atop Textual 0.20.x for a while now and earlier today I checked how it was getting in with 0.32.0 and... actually surprisingly okay. Not perfect, there were a couple of things that had suffered from bitrot, but it wasn't crashing.

The main thing I needed to change was the ability to focus a couple of containers (they didn't used to receive focus by default, now they do so I had to tell them not to again), and that was about it.

While I was in there I also updated the application so that I dropped the nifty little slide-in error dialog I'd made, and instead embraced the new Textual notification system.

While the application itself is a bit silly, and likely of no real use to anyone, I feel it's a pretty good barometer application, helping me check what the experience is like when it comes to maintaining a Textual application and the needs to keep on top of changes to Textual.

It goes without saying, I hope, that really you should pin the Textual dependency for your applications, and upgrade in a controlled and tested way; for this though it's less crucial and is a good test of the state of the ecosystem, and on the remote chance that anyone is using it, it'll be helpful to me if it does break and they yell.

This morning I've spent a wee bit of time tinkering with the configuration of the planned complete remake of my personal website. As part of this I made an effort to "port" over a section of the site. The choice for the first section to move was easy enough: Norton Guides.

Of all the parts of my old site, this is probably the most useful in terms of "contains information that isn't generally available out there on the web elsewhere and some folk might find it useful". I mean, at some point in the past, someone edited the Wikipedia page for Norton Guides and linked to mine as a source.

So getting that one back up and running as soon as possible made sense.

I've not added every bit of Norton Guide code to the main page, instead just pulling over and tidying up what was there before. On the other hand, just hacking on Markdown makes it all so much easier so I may expand on it a bit.

The really important part was moving over the file format details. This, I feel, is the information that people will be looking for, if anyone is ever looking.

So, proper start made; there's content beyond the landing page. There's still a lot to weed out and move over, and I think there's a lot of tweaking and the like with the configuration to do too. But the ball is rolling now. Ever time I get a spare hour and the desire to sit at my desk I can pick a section, look it over, decide if it deserves to come over, and act on that.

Heck, at this rate I might even end up with an actively-maintained website again!

As mentioned about a week back, my first show booked for this year's Edinburgh Fringe was to see Nick Harper. It's been a long time since I've seen him; far too long. As best as I can tell the last gig I made it to was in 2009.

Fourteen years. Shit's changed in that time, for me, for the world. O_o

On first getting into town it was warm and crowded, with that fun "town is doing festival shit" vibe that I like, so I went and grabbed an ice cream to kill some time until the venue opened. I knew I was in the right spot when, as I stood on Chambers Street, enjoying the cooldown, the man himself dashed passed, guitar case in hand!

When I got into the venue I grabbed a drink and tried to find a seat; most were taken; except for one right at the front and off to the side. So I grabbed it. Moments later Nick himself came over to say hello to the folk sat in this spot. We had a wee chat about how long it was since I'd last seen him, nattered about general stuff, and he said very nice things about my hat.

The gig itself was fantastic. While I love his recorded work anyway, Nick's always been one of those artists who I enjoy most live. He's got this way of singing and playing guitar that fills whatever time he's got to play; never once have I ever found myself looking at my watch, wondering if it's near the end; or if I have it's because I'm worried it'll be over soon.

A good number of the tracks he played I didn't recognise; at least two of them I know are from a new album that's coming, and I have to admit that when I do listen to his stuff it's the earlier works that tend to go into heavy rotation (I think the last album of his I bought was The Last Guitar). But I loved everything I got to hear. I'll be diving back into his catalogue and also keeping an eye out for the new release.

While there was only an hour for his slot, he did manage to get a couple of old favourites of mine in; I was delighted when he launched into By My Rocket Comes Fire, did a wonderful She Rules My World, and even squeezed in a quick Galaxy Song.

All too quickly though, the hour was up. It was kind of fitting that many of the songs he did have on the set list were all about time (on purpose, I'm sure). I'm happy to say I got to say a quick thank you and goodbye and then it was time for me to head out of town again.

Seeing Nick brought back a lot of good memories, and reminded me that I need to catch up on his more recent works. While most of his stuff doesn't seem to be on Apple Music (what can I say, I'm very online these days when it comes to music), I'm glad to see he's got a full Bandcamp, so I'll be paying that a visit!

I hope he swings back this way some time soon, not during the Fringe, and with a proper long set. It's been too long since I got to enjoy him really going for it and having a ton of fun.

A couple of weeks back I mentioned home my main HomePod had got stuck installing 16.6 of the software that runs it. This situation persisted for days after writing that post and I kept promising myself that I was going to see if I could unstick it by removing it from the Home, doing a factory reset and adding it back again.

Of course, during the week that followed, I never got round to that. You can imagine what it's like: no time in the morning, and by the time I get home in the evening I want to watch TV and use the HomePod as the speaker for the Apple TV, I don't want to be doing tech support shit.

The following weekend... yeah, I kinda forgot.

So, here I am, a couple of Saturdays on, it's early morning, I've had breakfast and I'm having coffee and I think it's the perfect time to do this. I hope the Home app my on iPad and... it's sorted!

So, yeah, it looks like it somehow managed to unstick itself in the end. A quick test of some of the issues I was seeing suggested there was still an issue, for example asking for the temperature in the bedroom would still result in a "working on it" reply followed by it telling me it wasn't responding. A quick reset seems to have fixed that.

I guess it's good to know: if it happens again, it'll keep on working as the speaker for my Apple TV, and it'll eventually sort itself out even if I don't muck about with a hard reset.

And I'm off! This morning I spent a good amount of time going through the sources for the old version of davep.org and removing everything that won't be needed any more, and also building up a rough TODO list of things I may want to recreate as content.

With that done, as mentioned earlier today, I started work on building the site around Pelican. Pretty quickly though I started to feel that that was going to be a bad choice. While Pelican felt like a perfect fit for this blog -- mainly because it seems to be very blog-oriented -- it was feeling a bit clunky for a general website that would have a handful of static pages at best; likely something I wouldn't be updating too often.

So I put it aside and went on with my morning, doing normal Friday domestic stuff like the weekly supermarket shop. It was while I was out doing that that I realised the obvious answer: use what we use for the Textual docs and what's been used for label.dev: Material for MkDocs!

I've just spent about 40 minutes after lunch kicking that off and it was really straightforward. Of course the result is horrifically cookie-cutter in terms of its look -- such is the way that mkdocs-material sites end up looking out of the box -- but I don't much care about that; what's important is that I've got a placeholder page in place, and I've quickly built a framework for writing and publishing the content.

So that's the plan: now that the welcome page is in place and there's something on my domain that looks like a working website again I can start to slowly drag in old content in a new format. Heck, if I'm careful I might even be able to retain some of the old URLs!

Longer-term plans might involve finally sorting out https support (yes, even today, my site is http-only), and perhaps adding some sort of RSS feed so there's a record of when changes are made.

After that... hopefully that'll be about it and perhaps the website will last another 22 years running on top of the same engine (actually that part should be easier because the "engine" is now local and it generates a static site).

The question then becomes who'll last longer, the site or me?

I've had davep.org since very late 1999. Initially it started as a domain used just for email; while I did have a website, around that time it was still hosted on my then-ISPs hosting service, with a mirror on a friend's web server.

A year or so later I finally did a proper revamp of my website and finally settled on www.davep.org as the place to point people to. I think, when I made that move, that's when I decided to write my own website engine in php. It was fun. It worked. I didn't want to code backend stuff (I don't think the backend vs frontend distinction was even a thing we were talking about then) so hacking it together in an unholy mix of ruby to generate various static files that live in the filesystem and then php to turn them into actual HTML made sense.

And it worked.

I heavily maintained the site for many years; keeping the same engine, tweaking the styles, adding features and content. I figure some time around 2013 or 2014 I probably stopped being quite so active in messing with it, and then in the last 5 or 6 years I've pretty much neglected it.

The neglect shows.

Meanwhile... php has changed. Quite a lot. It's one of those languages I used back in the day and pay no attention to. Then earlier this week I noticed that there must have been an update on the host and huge parts of my site broke, lots of content missing, pretty much useless and dead in the water.

I did briefly think about breaking out the latest and greatest php locally, setting things up to investigate what's going on, and seeing if I could breathe some more life into it; but really what's the point?

So after all these years I'm finally admitting defeat.

Right now, on the home page, I've just got a placeholder saying that bitrot finally ate my website and that I'm going to start again from scratch. That's my plan: given that I had a good experience moving this blog over to Pelican I think I'm going to build a new www.davep.org with Pelican. Where possible I'll try and drag some of the old content over, but I'm also going to use this opportunity to have a proper digital spring clean.

There's no planned timescale for this, but this morning I've spent an hour or so over coffee, branching the repo for the site and pruning out all the stuff I know I won't need and don't want.

I'll try and drop the odd update in here as things progress.

I almost feel bad admitting this. For someone my age it feels like a thing you should not really admit, but here goes... I only saw Little Shop of Horrors for the first time back in 2020. Don't ask me why. I just... never got round to it. I've known plenty of people who have seen it and loved it. I had a girlfriend for a while in the late 80s who was obsessed with it. She, like plenty of people I know, would quote all the quotes from it.

And yet... yeah, I never got round to seeing it.

Until 2020. On first viewing it became really bloody obvious why so many people seem to love it.

So you can imagine my delight when, earlier this week, I was fighting through the Edinburgh crowds to get to my bus home and I saw this:

Oh yes please! Oh so yes please! Given my desire to try and take in a few more Fringe shows that I normally would, this year, this seemed like a perfect fit. It also solved the choice paralysis problem for at least one week (really, have you seen how much there is on offer?).

So today I booked some tickets for myself and a couple of friends. Next week's "try and see at least one Fringe show" problem is solved: I'm going to go and see a performance of Little Shop of Horrors.

Following on from the previous entry, where I outlined a weird problem I'd started having with syncing Obsidian via iCloud, I finally decided to sit down and try and work out the exact flow of the problem. Today, for example, I'd created an entry in two different vaults on my phone while on the bus into work, and when I got to my desk the vault I use on my work machine had updated.

However, when I got home this evening, the vault for my personal stuff hadn't updated on my home Mac Mini. I tried a few edits, in both vaults, on the iPhone, and nothing came through to the Mac.

So... before I started really diving into things I decided to "turn it off and on again" -- the iPhone that is -- and when it came back I ran up Obsidian, which told me it wasn't allowed to access my iCloud drive!

I took a moment to go into the settings to try and figure it out, didn't find what I wanted right away, then got to thinking that perhaps some of the phone's services were still spinning up, so I ran Obsidian up again (after killing it).

Sure enough, this time, it saw my vaults. With both vaults open on my Mac I made edits to open entries and the edits started to flow.

So, yup, looks like it was a simple case of "turn it off and on again".

Apple: #ItJustWorks.