I started seeing today some users on our DB whose URL profile was NOT a t.co URL.
Up until now the API have always returned the t.co URL and the expanded URL on the entities field but we are seeing inconsistency on different users.
Here are some of the users whose profile URLs come on the expanded way from the API:
- @realref
- @tamberoweb
- @eatads_ooh
It isn’t a big problem but it shows an inconsistency that we need to deal with. Is this going to be the expected behaviour from now on? Will we have to deal with both formats of URL?
