SHOUTcast sending un-requested meta-data to Roku

[belltown]

This thread also relates to these issues:

Artifacts on TuneIn Roku app
Artifacts on Roku boxes
Is metadata in the stream by default

Audio streaming issue
Shoutcast v2
Sound Artifacts From Wavestreaming To Roku

The issue here is that SHOUTcast servers are sending meta-data (StreamTitle, for example) embedded in the audio streams to Roku devices even if the request contains no Icy-MetaData:1 HTTP request header. This only occurs when the Roku (or any other client such as curl) sends an HTTP request with a User-Agent header containing "Roku/DVP".

This has been confirmed by myself, an independent Roku developer, and Roku Co. engineering staff, and has caused problems for multiple Roku channel developers and provders of SHOUTcast audio streams who use various Roku channels to deliver their content (the Roku TuneIn and SHOUTcast channels, for example).

I believe this is a bug in the SHOUTcast servers in that the meta-data embedded in the audio stream should only be included if the server receives an HTTP request containing the Icy-MetaData:1 header. In fact, in the general case that is how it works; the meta-data is not sent from the SHOUTcast server to the client unless the request headers contain Icy-MetaData:1. The EXCEPTION to this rule is when the client's HTTP request has a User-Agent header containing the string "Roku/DVP", regardless of whether the request is sent from an actual Roku device or another client such as curl.

Is there any way to get in touch with the SHOUTcast server developers to pass along this information and have them research where in their code this Roku-specifc check is being performed, and disable the sending of meta-data if it has not been requested?