save access & refresh tokens and reuse them on next run #8

For system-wide I could see it be in AppData for Windows or equivalent on other platforms and have it scoped to the current handle, so tokens are shared while allowing multiple accounts if needed. Flow for app passwords will be easy. I'll skip talking about OAuth here. For instance-specific could be stored somewhere in node_modules, but it breaks expectation of people being able to use it without a JS project. I'm leaning to the first option.

I'd put it in the same folder in some json file, like the post mapping… Since the password that is used to log in to generate access tokens is already in the same folder, I don't feel like it would be a problem to also have the tokens there. Just a question how you organize stuff in which file. (In Minisky I have a YAML file with initially username & password and then the library adds the tokens to the same file. Or it could be saved together with the mapping.)

Definitely not in mappings, I want them to be also importable to your webapp or whatever like what I'm trying rn with getting Leaflet comments on my blog. I don't like it also just being dumped in the project root, cause it's already a lot of files, but it seems like the best option here, unless I modify .env with the token. I'm also bit worried about people accidentally just pushing their tokens somewhere, so it would be the best if it's commonly ignored place. Also for app password now I think it should be local cause you can have multiple app passwords.