Closed manuelcortez closed 1 year ago
With these changes, I think shorteners could be removed safely. Most users haven't to use them nowadays. It is also good for us: less code, less libraries, and less modules to maintain.
As a user: I would support removing them. With the changes I don't need them anymore.
It is a bit redundant. no matter what twitter shortens it, so having a second shortening service without analytics doesn't make much sense. For me I don't see a reason for keeping it in the client.
I think it could be removed without much issue or retribution from the community. If, in the rare case, you would need to shorten a link, it takes two seconds to hope over to bit.ly or your favorite shortening service, and paste it in.
Ok, so we will do the following before completely remove URL shortening services:
Hello, In the past, we were using URL shortening services to allow people to shorten their URLS, so we will save some characters in a tweet. But after seeing the last tweet changes introduced in the Twitter API, I am wondering if it's still the case. So I'd like to talk about if we should allow people to shorten their URLS or just remove that feature (only shortening, so they will be able to keep expanding shorten URLS):