At Twitch, we provide an API endpoint to get the list of a user's followers. For some of our popular users, this list might have 100,000+ entries.
A subscriber can subscribe to the topic https://api.twitch.tv/helix/users/follows?first=1&to_id=1234, which will send a content distribution request whenever user 1234 receives a new follower. Since the topic includes the query parameter first=1, our subscribers know that the content distribution request will include only the most recent entry, not the entire massive list.
However, it's unclear to us how we should handle someone unfollowing. If someone from the middle of the list unfollows, what payload should we send in the content distribution request? How do we send a payload that says "the list is now missing an element"? 🤔
At Twitch, we provide an API endpoint to get the list of a user's followers. For some of our popular users, this list might have 100,000+ entries.
A subscriber can subscribe to the topic
https://api.twitch.tv/helix/users/follows?first=1&to_id=1234, which will send a content distribution request whenever user1234receives a new follower. Since the topic includes the query parameterfirst=1, our subscribers know that the content distribution request will include only the most recent entry, not the entire massive list.However, it's unclear to us how we should handle someone unfollowing. If someone from the middle of the list unfollows, what payload should we send in the content distribution request? How do we send a payload that says "the list is now missing an element"? 🤔