Which is why I was asking for some specific examples, and why that functionality can’t be possible with the current APIs for followers. Specific use cases can go a long way to help prove the usefulness of a feature and why it should be implemented, simply saying there’s lots of various reasons isn’t helpful.
Some may like a follower badge in chat, but that’s an end user thing and probably more an appropriate suggestion for https://twitch.uservoice.com rather than 3rd party dev forums.
Also implementing a system to request specific tags would result in either defaulting to no tags (a major breaking change), defaulting to all tags (so not solving the bloat issue until all devs both update their libraries for it, and devs using those libraries request not to receive tags they don’t need), or defaulting to current tags, with only new tags requiring them to be requested to receive them (which isn’t very consistent, and going forwards into Helix one of Twitch’s goals is to be more consistent).