Keep topic type names below 64 bytes/characters
Summary:
While bandwidth across networks are usually a concern, internal bandwidth and memory footprints are also a concern. When using "channel.cheer" this is fine, but topics such as "channel.channel_points_custom_reward_redemption.update" approach an unnecessary level of verbosity and is roughly the largest topic name as of this moment. This can be left (though I'd prefer it to be shortened), but future events should be kept on a low byte footprint. Below 64 is my recommendation.
Reasoning:
Non-development basis: There is no real reason to provide a name of a topic that is over 64 characters, if this is the case, the name is likely in need a refactor.
Developmental outlook: In many languages you can just merely look for a string and go on from there, but when dealing with low level api layers, multithreaded, and non-blittable types, this is not necessarily possible.
Related Events:
- All
Some of note are the point redemption events which have a double encoding of "channel" which feels like a remnant of PubSub.
-
Appreciate the feedback for naming topics! Current names will not change, but we'll certainly consider this for new names as they are released.
-
Adminecressey (Admin, Twitch) commented
Hi Soaryn! Thank you for the feedback. We will keep this in mind as we name new subscription types.