Yeah, if manually typing in the individual ID for each files shareable link sounds like your kind of fun.
Each files ID (from the shareable link) has to be type in to TinWoo.. like this:
1r5fpIioPkP-ePNtemcubgKtj-OTAFGCEWD
It can't list directory contents, so shared folders aren't possible.
AND in every attempt I made to feed TinWoo files from several different
personal drives, it properly identified the filename after I gave it the file ID (so it was seeing the file) but 403'ing after attempting to download the file. This happened on two different internet connections, so it ain't that either.
Broken implementation. Waste of time.
Haven't tried it but if you are locally hosting the files from an http server on your LAN, then that option in TinWoo may be feasible, but don't enable https because it can't handle that dilemma either. Maybe if you are using something that can mount google drives and cache all filenames/details locally (mountain duck for example) then share that volume via http on your local network? Then again I would expect TinWoo to totally lock up or crash if you give it an http link to a directory filled with a hundred (much less thousands of) files.
The only thing I have come across that seems to be able to look at a google drive is Tinfoil itself.. but as is officially documented
here and vaguely noted in tinfoil itself, you have to set up OAuth from NUT and have it all configured from there.. so NUT is handling the directory listing and all that, and NUT in itself is a dumpster-fire if you've had a look at the code and pre-reqs. Kinda pointless to go through all the effort of setting up an overly complicated middle-man service that your switch has to be physically tethered to or have a direct network connection to just to see the files on a google drive.
Fingers crossed someone can figure out how implement a better solution in the future.
