It'd be good to describe what this is for and when I would run it. I think the target audience is, if you suddenly retired and became a hermit, how would someone new pick this all up, both to use it and develop it?

Usage-wise, Based on #1 it seems like it's useful for associating a personal Twitter account with @whattweetbot? I'm guessing maybe I should be logged in to my personal Twitter account in the web browser I use to follow the instructions?

Maintenance-wise, what should go in private-config.json?

Not sure what the latest thinking is on software projects. whatwg/participate.whatwg.org#114 is relevant.

In addition to adding the file, any work here should update the "license" entry in package.json. Currently it says "ISC".

@domenic can you review this code? It seems to work for its purpose. E.g., I could associate annevk with whattweetbot quite easily and get the relevant access tokens. The app showed up in https://twitter.com/settings/connected_apps. I did not try to tweet, but I assume that will work.

I would prefer a slightly different name for this repository and the app as Twitter holds the whattweetbot and this is really just a means for it to acquire individual account keys. Maybe whattweetbot-keys? (If you have instructions for how to rename this locally and make my environment forget about the old name that would be great too!)

Should probably also add a license and such and then we can make this public.

Reading https://www.npmjs.com/package/twitter-lite as well as Twitter's developer documentation I could not find a use for this, which seems a little weird?