Is URL Shortener service(s) support scheduled ?

Thanks for your answer and thanks for your work, hoping you'll consider adding personal URL shortening services support in the future.

Sincerely yours,

Jikan

Small change of plans. Twitter is about to impose t.co shortening without opt-out.

Since two layers of shortening does not make much sense and wastes bandwidth, I might stop using third-party shorteners.

[1] https://dev.twitter.com/docs/tco-link-wrapper-faq

Hum, bad news :/

But I read:
"""
My application or users already use URL shorteners. Will this break URL shortening and can my users opt-out?

URL shorteners will continue working with Twitter as they always have. [...]
"""

So, just one layer, and the one _you_ choose...
My opinion: you shouldn't stop to use third-party shorteners and you should add YOURLS :D
But it's just _my_ opinion ^^

Jikan

I think what the Twitter devs meant is that they won't *reject* the usage of other shorteners. But I highly doubt they are going to implement on-the-fly resolution and re-wrapping. That means they will wrap t.co *over* other shorteners, meaning users will have to go through two layers. This is bad for users with low bandwidth.

After giving some thought, I will keep the current system, as people might have other reasons to prefer a certain shortener. But Twitter will wrap t.co anyway, so to avoid giving two layers by default, shortening will ship disabled by default.

Twitter will only wrap URL to t.co only when the URLS are greater than 20 characters.

https://dev.twitter.com/docs/tco-link-wrapper/faq

Mariusz, there are plans to extend the wrapping to all URLs eventually, and applications can opt-in to have this already. Polly does.