Hi guys,
This is my tweet:
Senior .Net Developer/Microsoft Developer - .Net, C#.net, ASP.net. , London, £50k-55k, IT http://job.ad/ress #jobs #example #example2
134 bytes.
Taking into account that urls will go through your shortener service we add here another 2 bytes (because http://job.ad/ress is 18 bytes long but you replace it with 20 bytes long url).. Ok. Now our tweet is 136 bytes long. It should go to user feed without issues.
Posting.
Error: The text of your tweet is too long.
Whyyyy?
Lots of checks and in the end..
ASP.net is an URL, didnt you know? There is even no http(s) prefix, no www.. nothing. just (\w+).(\w+)
Why do you count it as an url?
Not all users are smart and not all put spaces after dots. So, will you count everything with dot in the middle as an url?
You know guys, its bringing a lot of mess and creates big issues for those who does posting tweets automatically (blogs, sites, services) on behalf of users.
Its ok that you limit posting to just 140 characters long.
But it is TOTALLY NOT OK that you expand our tweets to the bigger sizes. It makes tweets shorter when we dont want to.
How can we create tweets when we are not sure which size in the end it will have? Will it fail or not, which parts are expanded?
If you create API - then make strict and with expected behaviour, please.
Updates
- Thanks for your feature request. t.co is here to stay though. See How Twitter wraps URLs with t.co to better anticipate how your URLs and URL-like constructs will be wrapped with t.co. Consider using a twitter-text library to aid in you preparing text before sending.
