> I think I found the issue. I just spoofed the User-Agent with the
> Safari one and it now works okay. Is there a reason for the block of
> the custom User-Agent?
We don't that I'm aware of. Services_Digg sends a User-Agent of
'Services_Digg x.y.z' where x.y.z is the version number without any