Following someone on Twitch is usually a simple click of a button. But what happens when you can’t? Recent changes to Twitch’s API, specifically the removal of the Create User Follows endpoint, have impacted how some third-party applications manage follows. This change, while aimed at combating bot activity and fake followers, has raised questions and concerns among developers and users alike. Let’s explore why you might be experiencing issues following someone on Twitch and what the API endpoint removal means.
Twitch API Changes: The End of Automated Following
Twitch recently removed the Create User Follows endpoint from its API. This endpoint allowed developers to programmatically create follows for users, a functionality often used by chatbots and other automated tools. The removal stems from concerns about abuse, as this endpoint was susceptible to exploitation for creating fake followers and manipulating follower counts. While aimed at improving platform integrity, this change has inadvertently affected legitimate use cases.
Legitimate Use Cases Affected by the API Change
While the removal targets malicious bot activity, it also impacts legitimate applications. For example, certain bots relied on this endpoint to follow channels with “followers-only mode” enabled for clips, allowing them to create clips for users. Other developers used this endpoint for features like automatically following a channel after subscribing. The removal necessitates finding alternative solutions for these functionalities, potentially impacting user experience and workflow.
The Debate Over the Delete Followers Endpoint
The decision to remove the Create User Follows endpoint also sparked discussion regarding the Delete Followers endpoint. While the former was clearly linked to potential abuse, the latter’s removal seemed less justified to some developers. The Delete Followers endpoint primarily reversed the create action, enabling users to unfollow channels programmatically. Its removal raises questions about potential unintended consequences for managing follower lists and cleaning up unwanted follows.
Lack of Transparency and Community Feedback
A significant point of contention surrounding this API change is the perceived lack of open communication and community feedback. The decision seemingly occurred without a formal Request for Comments (RFC) or public forum discussion, leaving many developers unaware of the impending change. This lack of transparency frustrated developers who relied on these endpoints and wished to contribute to finding solutions that addressed abuse without hindering legitimate functionalities.
Balancing Abuse Prevention and Developer Needs
Twitch’s efforts to combat abuse are understandable and necessary for maintaining a healthy platform. However, the removal of the Create User Follows endpoint highlights the challenge of balancing abuse prevention with the needs of developers who rely on the API for legitimate purposes. The situation underscores the importance of open communication, community feedback, and collaborative problem-solving to mitigate unintended consequences of such changes. Finding a solution that addresses both concerns remains a crucial task for Twitch moving forward. This may involve exploring alternative API functionalities or implementing stricter verification processes for bot activity.
