Cheers, Greg, and thanks for taking it to the developers.
I will say that I've perused a few topics on this, and they've all been at least a year old, so I'm wondering if there's ever actually going to be any real movement with the (Public) Shared Folders/Links. (i'm not saying that in a tone that would indicate an attack on your person, mate ... just ... it seems like it's something that isn't desired for the public to have)
I guess, then, my final question would be what API command would you see as the best use case with regards to a cloud based implementation that may have size limits (let's take the Google API with limits size to 50MB per upload/download).
I would imagine that a "download then upload" won't be the ideal solution for that, would it? Would something like " get_temporary_link " work better. So it would:
- Locate a file ID.
- Generate a temporary link.
Allow that link to be used to directly access the file in question?
To be clear, I'm not stating that in a literal fashion, just using the get_temporary_link as an example, I'm sure there's a more appropriate function to achieve this.
Essentially, once I have identified a file that I would like to copy to another (let's assume an external API to work this out better) then I need to essentially be given a direct link to the file, somehow, to present to the other API. How would I get that link?
Would it perhaps be " get_shared_link_file " ?
If so, how would that work with the previously mentioned subfolder issues in that path?
(I'm about to attempt it, but will try to play it out here, too)