One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with micro.blog waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.
It was trivial, but I fixed it. Here's how.
Two biggish changes this month. I switched my time recording software to Tyme and I am really liking it. I also downloaded The Archive and am trying both to make it my preferred note-taking app (not so easy) and to adopt a stricter approach to notes based on Zettelkasten methods (easier, especially with The Archive). Also started taking a proper PHP course in Coursera.
I really enjoyed reading Eli Mellen's post of a couple of days ago:
.It really struck a chord with me because I have so often felt exactly the same frustrations, but my moaning comes from a position of consi...
An update to Parsedown, one of the packages that Grav uses to process Markdown, broke the display of footnotes and image captions. The update was necessary for security reasons that I don't understand, to do with processing HTML, I believe. While the Parsedown people are working on a proper fix, it...
There's an XKCD cartoon beloved of geeky nerds and nerdy geeks looking to make things happen automatically. Actually, there are two, Automation and Is It Worth the Time?. Both have exercised me all weekend, and now, after only 13.5 hours, I might be able to save myself literally minutes every da...