Some thumbnail images do not resolve for dugg items
ryanT
{user name}/dugg" method, sometimes the result set contains items for
which the thumbnail does not resolve to a file.
For example, in the following query "http://digg.com/tools/services/?
endPoint=/user/flocktest/dugg&appkey=http%3A%2F
%2Fflock.com&type=json&count=50&offset=0" an item is returned with a
thumbnail of "http://digg.com/tech_news/
Cisco_Predicts_Big_Growth_for_the_Internet_to_Continue/t.jpg" which
does not resolve to an image.
Is there an explanation for this?
Cheers
Steve Williams
>... sometimes ... the thumbnail does not resolve to a file.
>
>For example ...
>digg.com/tech_news/Cisco_Predicts_Big_Growth_for_the_Internet_to_Continue/t.jpg
Yep. I requested that URI and Digg responded with a 500 Internal
Server Error status.
An internal error can occur for a number of reasons. The details of
each internal error is logged. We continuously monitor the logs for
the most frequent kinds of errors, hunt down the root cause, and
apply a fix. That's a time-consuming task, and even the most
frequent errors represent rare, exceptional conditions, so I'm not in
a position to explain this one or say when it might be fixed.
Digg.com itself can be affected by this sort of error. Digg.com is
likely to serve a page that includes that image, and the image won't
show up. Interestingly, the image does show up on the permalink page
for that story:
http://digg.com/tech_news/Cisco_Predicts_Big_Growth_for_the_Internet_to_Continue
That's because it uses a different size that's not affected by the error:
http://digg.com/tech_news/Cisco_Predicts_Big_Growth_for_the_Internet_to_Continue/p.jpg
("p.jpg" stands for "permalink" size, which is 160 pixels on the
longest side, aspect ration preserved. The one that responds 500,
"t.jpg," stands for "thumbnail" size, which is 80x80 with a cropping
heuristic.)
A really careful API application might pre-fetch the thumbnail to
ensure Digg responds with a 200 OK status before using it. But
because it's an exceptional condition, an API application might
reasonably do what Digg does: Request the image and tolerate occasional errors.
ryanT
On Jul 6, 8:24 am, Steve Williams <s...@digg.com> wrote:
> At 11:14 AM 7/4/2008, ryanT wrote:
>
> >... sometimes ... the thumbnail does not resolve to a file.
>
> >For example ...
> >digg.com/tech_news/Cisco_Predicts_Big_Growth_for_the_Internet_to_Continue/t.jpg
>
> Yep. I requested that URI and Digg responded with a 500 Internal
> Server Error status.
>
> An internal error can occur for a number of reasons. The details of
> each internal error is logged. We continuously monitor the logs for
> the most frequent kinds of errors, hunt down the root cause, and
> apply a fix. That's a time-consuming task, and even the most
> frequent errors represent rare, exceptional conditions, so I'm not in
> a position to explain this one or say when it might be fixed.
>
> Digg.com itself can be affected by this sort of error. Digg.com is
> likely to serve a page that includes that image, and the image won't
> show up. Interestingly, the image does show up on the permalink page
> for that story:
>
> That's because it uses a different size that's not affected by the error:
>