3 ms·
Many of Twitter’s defining features, such as “@“ replies and retweets, originally began as conventions that were standardized by third-party clients before Twit
by segphault 5y ago
Many of Twitter’s defining features, such as “@“ replies and retweets, originally began as conventions that were standardized by third-party clients before Twitter natively incorporated them into the platform.
When they restricted access to their APIs and began tightening the screws to discourage third-party client development, Twitter began to stagnate because they no longer had a steady flow of new ideas to exploit. It also prevented third parties from providing the kind of user experience improvements and specializations that heavy users with large audiences relied on to make Twitter manageable. Without these things, the platform has deteriorated badly.
It isn’t surprising that they have circled back around to where they started and realized that they need third-party developers, but given how poorly they have treated the very people who drove Twitter’s initial success, I can’t imagine anybody is foolish enough to give them a second chance.
- p4bl0 5y agoAs someone who has been using Twitter daily for almost 14 years now, I have witnessed what you are saying and can totally confirm it.
- AutumnCurtain 5y agoHaving been farmed for ideas and then kicked out once, I can't imagine who would sign up for round two.
- runako 5y agoTwitter started trashing its API 9 years ago. That's eons in developer time. This was before the first public release of React, for example. I think if they make a meaningful effort to engage, there will be plenty of developers ready to meet them there.
- pookeh 5y agoAlso given that there are now a whole new generation of developers who weren't around when the whole trashing began years ago.
- renewiltord 5y agoPerhaps folks who never participated in Round One and therefore carry no scars.