You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2019. It is now read-only.
I just got the uploader to work and I can see the pictures appearing on my Flickr account, so this is great. However, I noticed that it is taking a very long time to upload each picture. Based on my ISP and the time it usually takes with other uploads, this is very unusual, and perhaps a problem with the Flickr service itself. However, it made me wonder if using multiple threads to upload could effectively improve the bandwidth utilization. Perhaps a simple change could be to allow a thread count to be specified and divide the image set among these threads. Is there something from the API side that would make this difficult or impossible?
The text was updated successfully, but these errors were encountered:
It's a good idea, I might have to see if it's possible. Some things do seem hellishly slow on Flickr's end too - creating the sets takes minutes occasionally, and there you are only uploading a smallish amount of text.
I just got the uploader to work and I can see the pictures appearing on my Flickr account, so this is great. However, I noticed that it is taking a very long time to upload each picture. Based on my ISP and the time it usually takes with other uploads, this is very unusual, and perhaps a problem with the Flickr service itself. However, it made me wonder if using multiple threads to upload could effectively improve the bandwidth utilization. Perhaps a simple change could be to allow a thread count to be specified and divide the image set among these threads. Is there something from the API side that would make this difficult or impossible?
The text was updated successfully, but these errors were encountered: