After writing Staccato I thought I should play a little more with the Twitter API. Not that I had anything to particularly say about the API, or that I wanted to broadcast, but I wanted a framework that I could push into service at a moments notice in case I had an amusing idea.
I am currently about to write my third bot...
A simple (nay, stupid!) Twitter bot to post random suggests for names of projects. With its origins in the Boaty McBoatface saga (https://en.wikipedia.org/wiki/Royal_Research_Ship) this bot was created in July 2016 and ran for a year.
To be honest, there was never a very large dictionary, and the logic to compute the sentances was never smart enough, so its contents repeated itself too often. But it was handy to have since I ran it on my home server, so it was an ambient information source that told me there hadn't been a powercut or network outtage at home. (Although, I have other monitoring systems in place for that!)
The full source to Botty McBotface is available on github under the GPL!
The 22nd July is represented, in right-thinking countries, as 22/7. This is, approxmiately, pi. So, I decided to publish 140 characters of pi every day. Well, it's not exactly 140 since I wanted to include the #pi and #pitbot hashtags. Writing it was a simple case of finding a million digits of pi, and computing the number of days since launch.
While of no practical value, it's always amusing to see the numbers it tweets. Sometimes you (as a human) spot nice or interesting patterns. Sometimes these patterns raise questions. Like, when is the first occurance of "31415926" in the number, after the start? When the first "0123456789" patterns, and so on.
When Twitter upped their limit to 280 characters I had the option of updating it. But didn't. Just because you have 280, doesn't mean you have to use them. And I didn't see the point.
I'll release the source soon.
I know what it's going to be. I know how to write it. I just need the time...