My favorites | Sign in
Project Logo
       
New issue | Search
for
| Advanced search | Search tips
Issue 1182: Timeline thumbnails are too large
18 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  raffi.krikorian
Type-Defect
Priority-Medium


Sign in to add a comment
 
Reported by jordan...@gmail.com, Nov 07, 2009
Requests for thumbnail images returns images not appropriately sized. Many
are beyond 500 KB (and much larger than the expected pixel size), there are
reports that some are even as large as 2MB in size causing mobile clients
to crash from higher than expected memory consumption on timeline views.

This bug is related to  issue #1158 
http://code.google.com/p/twitter-api/issues/detail?id=1158

Twitter had addressed the root cause of the issue but did not correct the
images that were uploaded since  issue #1158  went live.

The result is that some mobile applications are still exhibiting unexpected
behaviors even though the root cause was corrected.

Will you please create a process to correct these images on accounts?
Perhaps you can use the original process over these images (which failed
because of #1158) that runs upon upload to generate the correct 48x48
image? Just a thought.
Comment 1 by josuhr, Nov 07, 2009
I'd also urge Twitter to fix all oversized Avatars including those from the  issue
#601 . It's a real pain for all mobile clients.

Can you imagine what downloading a couple of megabytes means for people without a
flatrate plan?

Please consider rescaling all oversized avatars. Please.
Comment 2 by jordan...@gmail.com, Nov 07, 2009
3rd party developers are really at the mercy of Twitter with this one. I hope they
will see the reasoning and the good that they will be doing to help the 3rd party
developers (and for themselves) by properly addressing this issue.
Comment 3 by jordan...@gmail.com, Nov 07, 2009
Attached is a screen shot showing just 3 comments (of many) that I compiled from
Tweetie 2's comments on the App Store.

Note that I am not associated to the developer, but I thought it might be helpful for
you to see what users opinions are on the most popular of the clients.

Note how each user unfairly blames the developer (atebits), but how should users
really know? I don't blame users for seeing it this way.

This issue seems simple enough to correct. But it's devastating to developers. I feel
that the responsible thing to do is correct these images and do to do your best not
to let the issue happen again. Although, as developers we're all understanding how
regression can occur.

I don't want to be thought of as ranting so I hope this to be my last word on the
subject.

@TwitterAPI Please just have a look at the screen shot, and look at this issue from a
developers perspective. As you are likely aware developers are unable to respond to
user comments on the app store.
user_comments.png
29.2 KB   View   Download
Comment 4 by ticoconideas, Nov 07, 2009
I also believe this should be fixed, please realize that even the twitter.com page 
takes a loong time to load. If it will be up to users to reupload their images then 
at least post something to urge them to do so or something... Inaction is not a 
proper solution.
Comment 5 by terence.eden, Nov 09, 2009
This is a dupe of 601 http://code.google.com/p/twitter-api/issues/detail?id=601
The official response seems to be "It's fixed for new images, email us any which are
too large."

You can use http://tweetimag.es/ until the problem is fixed.  I'm not affiliated with
the site - but like that they can size the avatars correctly.
Comment 6 by jordan...@gmail.com, Nov 09, 2009
@terence.eden

Unfortunately this doesn't appear to work with the larger sized images, at least in
the test I just did.

See http://twitter.com/Jahia where the users avatar "thumbnail" is 3000px × 3000px
(scaled to 48px × 48px).

The request from tweetimag.es should be the following but notice how only Jahia_o
works (it is the original 3000px × 3000px image).

http://img.tweetimag.es/i/Jahia_m (returns no image) 
http://img.tweetimag.es/i/Jahia_n (returns no image supposed to be 48x48)
http://img.tweetimag.es/i/Jahia_b (returns no image)
http://img.tweetimag.es/i/Jahia_o (original size - works)
Comment 7 by raffigeo, Nov 15, 2009
this problem has been addressed for newly updated avatars.  we are planning a fix that will handle avatars that 
have already bee updated, but we do not yet have a timeline for when that fix will be deployed.
Status: Accepted
Owner: ra...@twitter.com
Comment 8 by jordan...@gmail.com, Nov 15, 2009
@Raffi I'm glad that Twitter is doing the right thing here. I hope that the fix will
be deployed in the near future but it's at least better to know now that Twitter is
committed to addressing the issue of the affected avatars.

Thanks.
Comment 9 by raffigeo, Nov 15, 2009
yeah - definitely - as you can imagine, this is not an easy fix, and its subtle to get it completely correct.  i'll keep 
people updated.
Comment 10 by jordan...@gmail.com, Nov 17, 2009
Thanks @Raffi on behalf of all of the 3rd party developers we're glad you guys are
addressing this issue.

I do I understand it's not an easy fix as I imagine there are a lot of images to
process. Hopefully (presumably) you will implement some automation to fix the images,
but I'm sure it will be resource hungry and still need to be executed very thoughtfully.

I'm crossing my fingers that the planned maintenance window at 11PM PST might be in
order to address this as well as other issues.

Cheers.
Comment 11 by raffigeo, Nov 17, 2009
unfortunately no - the maintenance window has nothing to do with the fix for this issue.  the good news, 
however, is that this fix will probably not require a maintenance window.  i'll keep you all updated.
Comment 12 by raffi.krikorian, Dec 10, 2009
(No comment was entered for this change.)
Owner: raffi.krikorian
Sign in to add a comment

Hosted by Google Code