Programming things: Giving up… (or at least getting bitten by semver and Golang’s unforgiving nature, and wanting to!)
There are good days, and there are bad days when coding, and you never stop learning. Today was not a…
![]()
ross spencer :: exponentialdecay.digipres :: blog
Digital preservation analyst, researcher, and software developer

![]()
Following the previous posts, bringing this all together meant three different applications.
paintergoblin.py – creates the images, can be run standalonewikigoblin.py – retrieves data to tweet from the Wikidata SPARQL servicestwittergoblin.py – tweets for us! Either a random Wikidata image or from am existing Wikidata linkWe create Tweetable information using the wikigoblin. We perform the Tweet using twittergoblin. In between the paintergoblin has to create his art!
We’ve seen examples of the images from the original zine.
How do we turn this concept into something real, and automated?
![]()
Continuing the story of the Painter Goblin and following part one, the idea of a Twitter bot started to form earlier this year.
In part 2 I take a very brief look at what is needed to write a bot and get it publishing.
Learn more below.
![]()