ianpaul
commented
7 years ago Well, life got in the way but I'm settled in now and back to work on the Twitter issue. I've got a rough version of a Twitter plugin that works. You can check it out in the newTwitter branch on my fork.
It uses the tweepy library to deal with all the Twitter stuff. That admittedly adds an extra pain for users since you need PIP before you can install tweepy (at least that's the easiest way to do it).
But I've discovered few people try to roll their own code for dealing with the Twitter API since there are so many libraries out there that take care of the nasty bits for you.
The other problem is you need to get consumer keys and access tokens from Twitter. That's par for the course for CLI apps, but it means users will have to be warned about keeping those access keys secure on their machine (i.e. don't make your .flashbake file public on Github). I can spell all of this out on the wiki with clear instructions on how to set everything up once this plugin is ready.
Anyway, the plugin needs a little bit of cleaning up before I make a pull request. Right now it prints some parameters in the commit message when it shouldn't. I'll figure that problem out over the next few days.
After this first version is up and running I'd also like to add some user friendly error messages when keys, tokens, etc. haven't been added to .flashbake, but that's for later on.
Twitter doesn't work. As of March 17, 2017 I'm working on a new script, but as I'm new to Python this is going to take me at least a few weekends. If anyone with better Python chops can whip up a solution faster than that please do.