No no no I don’t mean that you did this - you used the correct URL for the tweet.
I meant that this looks like another weird Twitter UX decision. And it seems this is on Desktop (so FF, Chrome, Edge), I just looked on mobile and it was fine.
I suspect Twitter is fully aware of this and decided it didn't matter when designing it. It's a fairly common pattern to make URLs more readable. I do it intentionally on a couple of my sites as well.
2) i added it from the ipad, it does not work on the web
3) try clicking on the unprefixed link on an ipad: it redirects to /timberners_lee which then redirects to #!/timberners_lee, which then submits a form or sth. Clicking "back" after that brings you to "mobile.twitter.com/" instead of here
4) when you visit the non-mobinle link from a web browser (Chrome), it first loads your personal frontpage and then reloads with the actual tweet page.
All this for less than 140 precious characters. Where is the world heading to?
So what are they doing, technically, that makes it hard for the twitter app to display an image inline? That URL just points to an image, so I'm not sure what broke here.
It's because they're using an url shortener in a non-twitter/character limited situation. Makes the browser need to go through a couple of jumps to load something that the user will want to load fast.
Yes, I’ve seen this quite often and been annoyed with it. I thought it had to do with the embedded web view in certain apps or the user agent used by an app’s web view. Whenever this happens, I just skip going to that tweet. If Twitter wants to make things so frustrating and tough, I don’t need to patronize that platform further.
It's an odd choice to put the tweet button at the top of the dialog rather then the bottom where your eyes and mouse should be after finishing the tweet message.
I meant that this looks like another weird Twitter UX decision. And it seems this is on Desktop (so FF, Chrome, Edge), I just looked on mobile and it was fine.
reply