mshroyer

Or alternately, there's no such thing as ghosts, and this isn't a problem that anyone based in reality needs to deal with.

I'd recommend the author use the OAuth 2.0 scope https://www.googleapis.com/auth/drive.file ("View and manage Google Drive files and folders that you have opened or created with this app") instead of https://www.googleapis.com/auth/drive ("See, edit, create, and delete all of your Google Drive files"), if/when they get a chance to work on this.

Anyway, this is really cool and totally fills a niche for me (90% of the time I want to edit org files in Emacs on my computer, but sometimes I need remote access). So I'm really happy to see this exists.

(Not a Rustacean yet.)

Are there any circumstances in which this approach can have undesirable behavior, for example if the dependency has to deal with some global state?

This seems like the kind of thing that could create difficult-to-understand problems if Cargo gives you two copies of a dependency only under specific and rare circumstances. (But I'm happy to be proven wrong, and I'm sure the Rust folks have thought this through more carefully than I have.)