zlacker

>>xslowz+(OP)
you could maybe show some testing? if that's true, then it should be measurable

>>c0t300+d
Test yourself, they link to their site from their profile and it's definitely delayed.

https://twitter.com/nytimes

>>stilwe+F
Just tried this - loaded almost instantly. But that's only the link in the profile. Not shared links in tweets.

Leaning towards there's something else going on deep in the DNS/ad servers/cdn/who knows. Not the first I've seen/heard of resolving delays with t.co... maybe it's even just something with legacy non-SSL links being redirected etc

>>ChrisA+89
You’re really twisting yourself into a buzzword cloud there aren’t you?

The link you clicked in the NYT bio is not a t.co link - I assume you noticed that but still are using it as counter-proof?

>>yunohn+Ej
On mobile, a quick test didn't even look at where the link pointed..... Because all links on twitter are t.co aren't they? Weird you think any links aren't t.co. It's how they track analytics on everything

No buzzwords there, just suspicion there's something else underlying with various technologies that are in play even on a 'simple' link click