I started to comment on Alan’s recent post but realized I needed to document this a bit better than a comment.
Every so often I kick over the #ds106 Markov generator and see what comes out. Sometimes I push it on to Twitter to share with the world.
en
You know what I understood characters (included. You to in inner pages
@IamTalkyTina is Back? Where is YOUR photo? #ds106 #markov
— Tom Woodward (@twoodwar) December 4, 2013
This one amused me so I did.
@twoodwar
en
But I don't really understand what you just said. Like what #markov means? #ds106 #contextfelldownthestairs
— Talky Tina (@IamTalkyTina) December 4, 2013
Talking Tina replied, justifiably confused. I explain. (There’s some additional side chatter you can see here but the more interesting stuff is below.)
@IamTalkyTina random text assembler w #ds106 tweets as source material http://t.co/GPAK1njFkh It's fairly fun (to me) although context free
— Tom Woodward (@twoodwar) December 4, 2013
It could have died there but instead it went into a realm I could not have predicted- probabilistic programming in quantitative finance.
@twoodwar Am I here ?? Probabilistic Programming in Quantitative Finance | Quantopian Blog – http://t.co/suhLmUKjab #ds106
— Talky Tina (@IamTalkyTina) December 4, 2013
Bill Smith chimes in with n-dimensional Hilbert space.
@IamTalkyTina @twoodwar You R probably not here, but likely to be there. Yes, you exist in n-dimensional Hilbert space, but which n?
— Bill Smith (@byzantiumbooks) December 4, 2013
All this from the random ramblings of a robot algorithm.
An Aside
Because asides are what this post is about after all), you may recall some attempts I was making to use an IFTTT recipe to pull my Tweets into a Google spreadsheet to mess with them a bit more.
I decided to see how often I’d get close to the full 140 characters. In playing around with the chart types I decided to visualize it with the radar chart. I was just curious what it would look like. No real reason. Strangely it has completely frozen the chart. I can’t remove it or interact with it in any way. It looks like the first image on my end and gives the second humorous (to me) error message on the published view.
It’s always interesting when you break something. Usually it’s best if it’s fixable but I don’t mind too much in this case. there’s something fairly attractive about breaking a web service in this way.
