šŸ“… Daily Note: December 12, 2024

It looks like – thanks to some heavy debugging and re-developing from Steph – the new way of creating the Daily Notes is working! I’ll write up the thinking about it and how it works shortly.

# – micropost 22785


# – micropost 22796


One issue with my new blogging workflow is its dependence on a WordPress custom post type – and my editor of choice, MarsEdit, doesn’t currently talk to such things.

So, am testing a bit of code to get around this. In effect, I send a ā€˜normal’ post to WordPress from MarsEdit, only as a draft, and in a particular category.

When WordPress receives this, it spots it, copies the content and tags to a new micropost in the custom post type.

Currently the original post is left in drafts for me to delete manually, but I’ll probably automate that once I’m confident it’s working ok.

So, a bit janky and duplicative, but it ought to work ok. Will see if there’s any unforeseen repercussions on performance or anything like that. Code is on Github, if you’d like to make use of it.

# – micropost 22812


Jeremy’s 5 reflections on his year at Homes England are interesting, wise, and definitely worth thinking over.

# – micropost 22839


šŸ“… Daily note for 1 July 2024

Pinch, punch, first of the month.#


Am trying a thing to easily(ish) create anchor links at the end of paragraphs in these daily notes. That way I can point people directly to a specific nugget within a post. There is a very limited user need here, beyond scratching an itch, which is to try and replicate one of the ways that Dave Winer’s blogging⬈ works, and Lloyd tried a similar thing a while back⬈.

I’m aided here by the fact that I write my blogs posts in MarsEdit, a desktop app on my Mac, rather than the WordPress interface itself. MarsEdit lets me create macros assigned to keyboard shortcuts, so now when I hit ctrl-cmd-p, it plonks in opening and closing paragraph tags, and prompts me for the anchor id, which it then uses to spit out the necessary tags to make a clickable # sign at the end of the paragraph.

(A slight pain is having to type in the anchor text twice – once for the anchor and then for the link. Mistyping this will obviously lead to errors, but am not sure how to get around it.)

I think it works – try it out on this paragraph and let me know how much of a waste of time this was! #


What this hopefully will mean is that, rather than waiting until the end of the day to publish these notes, I can publish it after the first item is written, and then update it during the day. Having the anchor links means if I want to point to a specific thing before the end of the day, I can.#


Not a lot to argue about in this article⬈ on building “21st century digital government” – data and interoperability are jolly important. But the click-baity headline means that it’s presented as the only answer, and we know that – as important as data etc is – it’s isn’t the only thing organisations need to be focusing on. I don’t think anyone would argue that rather obvious point, but the danger is that some less informed folk might read this as being a ‘data will solve everything’ argument, meaning that the other stuff gets missed.

Basically, everything is complicated.#


I’ve ordered a new desk chair, on the recommendation of Ann Kempster⬈. Thanks Ann! This one isn’t too big, so won’t dominate the room, and most importantly, it won’t bankrupt the shareholders of SensibleTech Ltd⬈. I asked for suggestions on Bluesky and LinkedIn – feels as if questions like that are ideally suited to social networks. #


Speaking of LinkedIn, it does seem to be continuing its march towards replacing Xwitter as the best place to get work-related engagement going. Noticed a few people writing fairly lengthy piece as ‘posts’ rather than ‘articles’ – would be interested to know what difference this makes, as both require a click to read the bulk of the text. Might try an A/B test to check it at some point.

The URLs for posts rather than articles are very ugly, and it’s a poorer reading experience for people who aren’t logged in or have an account.

Another thought: posting these daily notes in their entirety to a LinkedIn post, rather than just linking to them? šŸ¤”#


Here is one such LinkedIn post⬈, an excellent one from Adrian Lent, in which he proposes what those wishing to see radical change in public services ought to do:

I think history is clear on what works. Those who want change must come together, work out a shared vision of generalised reform and then press for it as determinedly as possible. In effect, creating a movement within the public sector for system transformation.

#


This is a lovely post from Jukesie⬈ about his love affair with libraries, and his inspiring decision to start volunteering. #


Steve recently started sharing his blogroll⬈ – a rather old school blogging concept of maintain a public list of blogs you like to read, to encourage others to find them and share theirs.

Was reminded of this when I came across this post from Dave Winer⬈, sharing an automated way of finding blogs from blogrolls, and then finding more blogs from those blogrolls, and so on – all thanks to a defined standard. Nice.

(I just noticed that one of Steve’s posts mentions Winer’s standard too – I must have missed that at the time!) #


šŸ“… Daily note for 28 June 2024

I’m back! First daily note in a while. Hope you are as pleased with me as I am 😁

The blog has been rehosted, meaning I can save a bit of money shutting down an old hosting account. Have also changed the theme, going from the venerable Twenty-Fifteen⬈ which has served me well for a long old while.

I’ve gone for GeneratePress⬈, which is a very bare-bones (the idea being that you can customise it to do whatever you like). I’m just tweaking it here and there to keep things light and simple. I’ve avoided blog-tinkering for a while, but it’s quite nice to change things up.


I’ve tried to trim down the number of RSS feeds I am checking on the regular in NetNewsWire⬈. Am subscribed to over 400 but huge numbers of those are inactive these days, and others I rarely check. So, have split them into two folders, Must reads and Nice to reads. The latter stays shut unless I’m desperate for something to look at!


Eddie Copeland posted an interesting aside⬈ on language and how he isn’t using the word digital much, and it seems to be working for him. Fair enough! I’m a bit horses-for-courses on this one really, sometimes it can be a helpful word, sometimes not. Depends on the organisation’s context I guess.

When I do say ‘digital’ these days though, I invariably follow it up by saying that it is a simple shorthand for technology, data, and online experience.


I love this quote from Matt King in his post the future of digital is already here⬈:

Working in public sector digital environments can often involve an almost disorientating sense of deja-vu, where a chance phrase drops you deep into a flashback to the previous times you had a similar conversation. When this first happens, it’s tempting to think that you’re getting old, and that either that the organisation you’re working with has ignored the last 15 years, or that the case for digital change is doomed. The reality is usually that none of these things apart from the getting old bit is true, and that the organisation you’re dealing with is both ahead of the curve in a few places and has missed some stuff in other places. The future of digital is not very evenly distributed at the moment – it’s pretty bumpy – but what we’ll see in the next 15 years is that distribution improving.


Going down to London and speaking at the Town Hall 2030 launch on Tuesday was pretty exhausting but also inspiring. I love the fact that the lens for quite a few big beast policy types is now on local public service delivery.

With the likely new government on its way, it feels like a very optimistic time, which is a very nice feeling to have. I came away with many thoughts that I will try and wrangle into posts in the near future.

Does this actually work? #

šŸ§‘ā€šŸ’» Movements

I have rehosted this blog, which seems to have worked ok. Well, if you’re reading this, it must have!

One side effect is that anyone subscribed to the RSS feed may well have suddenly received a bunch of old posts popping up as a result. Just mark ’em as read and move on, there’s nothing new to see there!

I’ve switched the theme as well, for the first time in many years. Not sure what direction I’m going in with it all yet though – plenty of tinkering ahead!

WordPress and email

I’ve been moving a few of the sites that I manage away from a simple shared hosting arrangement onto something a bit more proper, with Steph’s advice (this blog, being incredibly simple albeit with a fairly hefty archive going back to 2004 or something, remains on the shared hosting for now). The new ‘platform’ is made up of using SpinupWP to manage the setup of the servers and WordPress itself, which is all hosted on DigitalOcean, with all the benefits that come from having this kind of control over the environment.

One area that has been causing me some worry is around sending emails out of these sites. The emails that WordPress sends, like password resets etc, can be a bit flakey in getting delivered at the best of times, but to make it more complicated, SpinupWP doesn’t install a means of sending emails itself, you have to configure your own, using an email sending provider like Amazon SES or Mailgun. It sounds complicated – and it is, in a way – but there are plugins and things to make it easier.

I’ve played with a few ways of doing it, but think I have settled on one, that I will now move all the sites onto over time. I’m going to be using the WP Mail SMTP plugin to get everything set up and working, and linking it up with SendLayer to do the actual emailing. When setting these things up, you need a domain to use, and each one needs configuring in SendLayer. To make life easier for myself, I have registered a specific domain to use for this, and so emails will come from sitename@davesemaildomain.notreal, which hopefully will keep things simple.