i tried that url using wget (command line tool that fetches urls) and got
> wget t.co/mAtQ0Q8cot
--2013-09-23 09:46:37-- http://t.co/mAtQ0Q8cot
Resolving t.co (t.co)... 199.16.156.75, 199.16.156.11
Connecting to t.co (t.co)|199.16.156.75|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://twitter.com/tarteenia/status/382042205231132672/photo/1 [following]
--2013-09-23 09:46:37-- http://twitter.com/tarteenia/status/382042205231132672/photo/1
Resolving twitter.com (twitter.com)... 199.16.156.102, 199.16.156.230, 199.16.156.70
Connecting to twitter.com (twitter.com)|199.16.156.102|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://twitter.com/tarteenia/status/382042205231132672/photo/1 [following]
--2013-09-23 09:46:38-- https://twitter.com/tarteenia/status/382042205231132672/photo/1
Connecting to twitter.com (twitter.com)|199.16.156.102|:443... connected.
ERROR: The certificate of `twitter.com' is not trusted.
ERROR: The certificate of `twitter.com' hasn't got a known issuer.
so i'd try adding "http://" at the very least, and cross your fingers that processing handles 301 redirects.
> wget t.co/mAtQ0Q8cot
--2013-09-23 09:46:37-- http://t.co/mAtQ0Q8cot
Resolving t.co (t.co)... 199.16.156.75, 199.16.156.11
Connecting to t.co (t.co)|199.16.156.75|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://twitter.com/tarteenia/status/382042205231132672/photo/1 [following]
--2013-09-23 09:46:37-- http://twitter.com/tarteenia/status/382042205231132672/photo/1
Resolving twitter.com (twitter.com)... 199.16.156.102, 199.16.156.230, 199.16.156.70
Connecting to twitter.com (twitter.com)|199.16.156.102|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://twitter.com/tarteenia/status/382042205231132672/photo/1 [following]
--2013-09-23 09:46:38-- https://twitter.com/tarteenia/status/382042205231132672/photo/1
Connecting to twitter.com (twitter.com)|199.16.156.102|:443... connected.
ERROR: The certificate of `twitter.com' is not trusted.
ERROR: The certificate of `twitter.com' hasn't got a known issuer.
so i'd try adding "http://" at the very least, and cross your fingers that processing handles 301 redirects.