Just wondering if there are any rate limits when it comes to uploading images to Twitpic with the API. I find that on the odd occasion the image doesn't upload. Does anyone have any experience with a similar problem or how I might go about fixing it.
Should also have mentioned the images are around 200KB or less.
There is a 10MB image upload limit:
We take GIF, JPG, & PNG images up to 10MB in size, and videos up to 1:30 in length in most formats.
Source: http://twitpic.com/upload
It could also be that their API is having issues, which if that's the case you need to pass the error to the user so they know what happened.
Related
I am writing a Swift iOS app that uses Blockfrost.io to download assets from the Cardano blockchain. The asset's images come in the format ipfs://QmSJPFVN..., which can be retrieved by using the URI in a CloudFlare URL, like this https://cloudflare-ipfs.com/ipfs/QmSJPFVN....
My issue is that most of the images I'm trying to fetch and display are enormous, and it's seriously slowing down my UI. Are there parameters that can be added to the URL to specify a smaller image size to be fetched? I've looked around for a solution but haven't been able to find any.
You have two options for this -
Use a 'proxy' to fetch the image server-side and convert before downloading. Could make use of a Cloudflare worker for instance - https://developers.cloudflare.com/images/image-resizing/resize-with-workers
Download the full size image, but convert it within your app before displaying it in the UI. You'll still use full amount of bandwidth in this approach, but may reduce complexity.
I'm writing a fairly involved application for working with Sony cameras.
I can list the contents of the camera and copy image files no problem at all, but I can't seem to figure out the size of the files before I start to download them.
I'm receiving the file list using the standard getContentList API, and finding the files using the originals array in the response. That response seems to have no file size information in it.
Is this possible? Knowing the file size before downloading is important for a good user experience, and all the other camera APIs support it.
I do get the size when I start to download in the HTTP Content-Length header, but performing HEAD requests to hundreds of URLs in a row seems very inefficient!
Unfortunately the API does not support getting the file size.
Progressive JPG is a image format, that contains low quality snapshots. These snapshots can be displayed during the transmission of the higher quality snapshot, which gives better end-user experience.
Progressive JPG is a image format, that can be progressively displayed in the web browser during its transmission.
Can end-user benefit form the progressive JPG, if the file is transferred over HTTPS? If the image is encrypted, snapshots would have to be separated...
Progressive JPG is a image format, that contains low quality snapshots
No, that’s not true¹. It is only one image – but saved in a way, that some ”broad”, lower-detail information is encoded first, and then more detailed data is coming later on, so that rendering can start early in lower quality, and as more details become available, the rendering can become more refined.
And serving such an image via HTTPS does not change that.
¹ Images can contain additional thumbnail version(s) inside the EXIF meta data – but that is not what the “progressive” format is about. And that feature is seldom used on the web, because it would increase the overall amount of data to be transferred (and I am not even sure if common browsers support this, in that they would display such a thumbnail first and then the full image once it is done loading.)
When uploading certain PNG files the size is incorrectly reported on the OneDrive website and in the Photo object returned by the REST API. This can be reproduced using the following PNG file:
http://www2.zippyshare.com/v/11270772/file.html
The file size is 20.3 KB, OneDrive displays it as 38.4 KB
It seems this only happens with PNG files that would be downsized/converted when the downsize_photo_uploads query param is absent or set to true. But the problem is not just limited to uploads using the REST API.
The problem has been already been reported here.
Ryan from OneDrive here. We looked into this and have a good understanding of what's going wrong with the size. OneDrive computes the "space" a file takes up in our system by using the size of the largest data stream associated with a file. When an image is uploaded to OneDrive, we also create thumbnails for images so that we can quickly show various views in our clients and website.
In the case of this particular file, one of the JPG thumbnails we create for the PNG file is actually larger than the original file (due to the JPG compression not being as effective as PNG for this image). As a result, the thumbnail is actually the largest stream on the file. As you can imagine, that doesn't happen very often, but for this image (and others like it) we have this bug.
We have a bug tracking the issue and are investigating how we can fix the API to return the size of the "default" stream -- the stream that represents the actual contents of the file. I don't have an ETA for the fix, but we're working on it.
FWIW, I appreciate your post, I discovered that is seems to be the same issue with the Android Onedrive SDK post I made a couple weeks ago
Does OneDrive change/re-encode jpg files?
It doesn't seem like anyone from MS is actually monitoring these SO tags very closely, so I'm creating a Github issue on the Android SDK, maybe that will produce an answer.
https://github.com/liveservices/LiveSDK-for-Android/issues/37
I have got a little file sharing webpage. It's free to use it. I would like to upload files between 0mb and 1GB. I'm searching in Google since two days, but I can't find anything what I needed...
My webpage: http://boxy.tigyisolutions.hu However I can upload only 20-30mb now. I would like upload only 1 file at once. But it may be bigger than 500-600mb ... Can anyone help me?
I tried jquery fileupload, but it's uploading nothing for me.
The Blob.slice method will allow you to split up a file client-side into chunks. You must then send each chunk individually. This will only work on browsers that support the File API.
If you don't want to write this code yourself, Fine Uploader is a javascript uploader library that has the ability to chunk files for you and send them to your server.