People have written some interesting things following on from the pop-up IndieWebCamp that Chris Aldrich organised a couple of weeks ago. The Garden and the Stream set out to compare and contrast wikis and weblogs and how the two might be used. It was a terrific success, and I’m sorry I wasn’t able to be there. The topic interests me and is something I’ve thought about on and off for a long time. This morning, I treated myself to thinking about it some more.

It has been three weeks now since I first ran Bise on my logfiles to see who and what had been popping in here to take a look. It’s a bit of a faff, for a whole variety of reasons, which start with my host keeping only a couple of days worth of logs. That means I have to download the logs daily. And my host’s naming convention is different from the one Bise expects. Rather than play with Bise, it is easier to rename the files. And then there's a whole lot of to-ing and fro-ing.

Very strange, but for two days straight my log files have not shown anyone coming here for a post that couldn't be found. Is this a sign of success, or of increasing irrelevance?

Anyway, I did eventually find something that couldn't be found, and brought it in. And it triggered all sorts of nost...

It is 160 days since I first noted that I would like to make use of Bise, Jason McIntosh's blog-readership reporter, 118 since I automated downloading the access logs. With half an eye on the project day at IndieWebCamp Austin, time to make good on my promise.

Bise expects its log files to be named a certain way, which is not the way mine were named, but that proved relatively easy to overcome with the wonderfully powerful A Better Finder Rename. The latest version has filters that make it possible to rename 1-9 and 10-... , which require slightly different handling, in the same batch, and that makes life super easy.

One of the reasons I love RSS (and other) feeds is that they effortlessly alert me when someone I follow posts something. So it was this morning, when James Morley published Collecting and displaying contextual tweets for cultural heritage records. I've known James a long time, and admired his approach to gathering and visualising data, and this was his first post in almost two years.

It's about automatically harvesting Tweets using a tool called TAGS – Twitter Archiving Google Sheet, and he shows in detail how useful it can be. I might even find a use for it myself. But here's the thing. James recognises some "potential issues," among them this: