tonyflames
Member
It's back!
Remote Upload doesn't work!!!
Remote upload isn't something that we can maintain 24/7, sometimes the other side, quite naturally, updates their services to prevent remote uploads and URL resolvers, while we offer an API for our CDN, others might not be that open.
Ok so what if "the other side" is Streamango itself? I'm using your remote upload exclusively to "clone" files (remote uploading streamango links to streamango). I understand that it's hard to support 3rd party services who may or may not provide proper API's. But file cloning shouldn't be affected by that. I've never understood why you and Openload hide the cloning functionality under the remote upload API. After all as we can see here if the actual remote upload future breaks it takes down cloning with it which shouldn't be affected (remote uploading streamango links only results in some db queries). So is this getting looked into?
It doesn't; cloning sounds like you are copying something you already have. To me.Thank you for responding. I wasn't aware that the file manager "copy files" thingy worked with file ID's from other accounts.
Revealing any of the above information is a risk for your files and the account.Still, that introduces the problem of needing the accounts login creds as opposed to the API login+key which is a bit of a security risk. It would be really great if this could just get added to the API. Since all the functionality for this is obviously already implemented in the backend it shouldn't take more than 30 minutes to expose it through the API.
It doesn't; cloning sounds like you are copying something you already have. To me.
The recent issue, however, shouldn't hinder you from using the remote upload to clone mango files, they do not count as items in the remote upload queue, which is currently the issue and we are dealing with it.