Hello world, and welcome to my corner of the web. This is where I write words about what I'm working on, and post photographs of things I've seen.
I'm a software engineer at the Wikimedia Foundation,
and so of course my personal website is a wiki (running on MediaWiki).
In my spare time I volunteer with WikiClubWest to work on Wikimedia projects, mostly around my family's genealogy and local Western Australian history (especially to do with Fremantle).
I try to keep up with issues on all the things I maintain (but usually fail), as well as listing the software that I use.
I try to find time to work in my workshop on various woodworking projects. Recently, that's been focused on building a metalworking bench, and will soon be about a set campaign-style drawers that's in the works. I've a good-sized workshop because I don't have a car.
Travel features in my life, not because I really hugely want to go elsewhere but because I just do — and also because then I can do some interesting mapping on OpenStreetMap, and take photos for Wikimedia Commons. Sometimes I ride my bike to get there, or walk, but more often it's planes, trains and ferries.
And if you prefer to install and run your own content management software or create your one yourself, you can do that too: https://indieweb.org/CMS
If you do create one, watch out for spending more time coding than writing.
Or code away! It’s your site, code, write, mix it up as you wish.
It's an old clique I guess, that programmers spend more time tinkering with their blog than actually writing anything on it. That's certainly true for me. But then, I think I spend more time writing on other places these days, mostly non-chronological ones (they feel a bit more useful). But picking a CMS and getting a site online used to be great fun! I'm not sure that it is as exciting, on the modern corporate internet. The indie internet still exists though! Everyone should come and do whatever they want on it.
W.A. Greens leader Dr Brad Pettitt put a reel on Facebook, pointing out the danger of vehicles intruding into the shared cyclist/pedestrian path, that runs along the railway line at Victoria Quay.
I pointed this out years ago, and a couple of times since, and Fremantle Ports promised to put stoppers on the road, but then changed their minds, claiming it would become difficult for motorists to park. What utter nonsense!
The shared paths is very popular and can be extremely busy with passengers of cruise ships, so vehicles sticking out onto the path are creating a serious safety hazard, that Fremantle Ports really needs to address.
But then that same day, Fremantle Ports said they'll do something!
It took years, and about four blog posts here on Freoview, to finally get Fremantle Ports to commit to safer parking at Victoria Quay, so that the shared pedestrian and cyclist path along the railway line, will no longer be blocked by the backs or fronts of vehicles.
Fremantle Ports just contacted me to say that a contractor has been engaged to install wheel stops. That work will commence in October.
I have various wikis, into which I dump stuff as I think of it, or digitise it, or find it, or whatever.
It's mostly a good feeling of eventual organisation,
like things can be safe for now and at some point put in their right places.
By date, or media type, or geographic location.
Then, all the wikis get backed up (to three different storage systems in three different places, one of which is not managed by me),
and the process of backing up helps to remind me of things that need organising.
It's nice watching the rclone progress.
I'm slightly worried sometimes about what'll happen to them in the end,
that some poor sod will be left with some gigabytes of files and a few large XML files,
and may well just give up and throw it all away.
Possibly a Git repo full of Markdown would be better (certainly would be more fashionable),
but that doesn't deal with the images and PDFs and whatnot.
I've written before about websites as collecting endeavours. That there's some good aspects to features like MediaWiki's insistence on not being able to embed foreign images. Keeping things together within one place, and pulling in things that we find elsewhere, can build a more coherent and resilient website. Having copies/duplicates/multiples of things, spread out and maintained by completely separate people or organisations, increases the chances that things will survive. The web is an ephemeral place.
Some sites, such as many of those on the fediverse, don't like archiving. They have very clever systems of interchange that does result in multiple copies being hosted in different places, but they also have good systems of those copies being strongly linked — so they can all be deleted if the original is. In the more disperse indieweb world that's not really how it's done: some RSS feed readers, for example, will keep all copies (following some retention policy perhaps, but that might be "keep forever" — that's certainly how I do it for a bunch of sites I follow).
This is an image loaded via InstantCommons (a thing I uploaded recently to Commons).
MediaWiki does allow embedding foreign images in one specific way: if they come from Wikimedia Commons. This is called InstantCommons, and it's a very cool feature. It pulls in the image and its metadata, and links to the thumbnail hosted on Wikimedia's servers. This has a few issues, such as the image being able to be changed at any point without the local wiki knowing, and the fact that it makes the local wiki's collection dependent on an external service. It also puts quite a lot of load on the Wikimedia servers, which is probably fine if it's for a purpose that's aligned with that of Commons (that's a tricky thing to figure out of course).
A better system would download the thumbnail to the wiki's own storage, and serve it from there. But I also have been wondering about a system of copying the image (and its metadata) into the local wiki, to remove any dependency on the external service. That uses even fewer of Wikimedia's resources, and makes the wiki self-contained. The trick to it I think would be to make it quick and easy to pull the image in (and perhaps it could work with any website), and also maybe to view any changes that had been made since it'd been pulled in.
Then the site would be more of a standalone collection — perhaps annoyingly indivisible.
The (nerd) world seems to be much more interested in ActivityPub than RSS these days,
but RSS feels so much simpler and also in a way more powerful.
It's sad that even podcasts are abandoning it.
It's slightly ironic that I came across the post in via my RSS feed reader (via the IndieNews feed), where it didn't have any body and just looked like this:
I still hope to implement Webmentions on my own blog one of these days.
Interesting that Miraheze are looking to disable the DisplayTitle extension
because of performance concerns.
I've recently been removing it from some wikis, mainly because people have gotten confused about what a page's title actually is.
There are also a bunch of places that used to make use of DisplayTitle that now have templates
that basically follow redirects to figure out titles, and it's more obvious what's going on when those are used.
This policy reaffirms the British Library’s commitment to making metadata as open as possible, and confirms the terms of licence, limitations and exceptions for sharing the British Library's open metadata.
contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
A good thread about what LLMs are doing to software development. It definitely does feel like people are caring less these days.
It's becoming more and more common for people to leave AI-generated comments during code reviews. This is to be expected I guess, as more and more people are using AI to write the code, it makes sense that they also use it for the discussion part. It's sometimes incredibly obvious when they do, and sometimes less so. I'm also starting to wonder if people are intentionally using AI-style language though, even when they write things themselves! Like always re-phrasing what they're replying to, being overly grateful, and using the name of the person they're replying to.
I wish people would just go back to being themselves.
The Wikimedia OCR tool is now at version 1.10.2. Nothing big in this change, I mainly made it because there were a bunch of localisation updates that had not yet been released, and lately there's been some TranslateWiki.net comments about how important it is to keep on top of these updates.
Building a website feels old-fashioned these days. How many more websites do I have left in me before the old fire flickers and dies? Is snuffed out. Before making websites is no longer a viable way to earn a living? The web will change drastically within my lifetime, maybe someday soon, indeed it already has. Maybe it really will fizzle out, a graveyard haunted only by bots and crawlers. But I have a hunch that there will be a long tail. Amid the dying embers, a resilient cohort of indie web bloggers, artists and creators will keep going, keep on talking to each other through their blogs, without tracking, pop-ups or invasive ads.
I dropped in to the maritime museum this morning to get a photo of Shakespeare Hall's diving trunk that's on display on the deck of Trixen, and also noticed that there's a document of his on display in the same location.
The Swandocks' crane is half re-built now.
Shakespeare's trunk.
Shame about the heavy tinting, otherwise it'd be a good place to take photos from.
The Swandocks' crane is half re-built now.
Shakespeare's trunk.
Shame about the heavy tinting, otherwise it'd be a good place to take photos from.
