i don't like that i cant definitely say "they are not doing this" because there are half a dozen ways they could obfuscate it, but the only things going out after initial load are
1) beacons to scorecardresearch
2) gql queries refreshing presence, stream id, stream tags, stream access token
3) pings (and chat) on the chat websocket
4) pings on the pubsub websocket
5) HLS requests
none of them have anything that changes when muting or unmuting
youd think the scorecardresearch beacons would be the most obvious culprit but if they were then twitch wouldn't count any viewers using some form of tracker blocker. also i doubt they'd get near real time numbers like they do
anyway the only thing in there that seems to change ever after the page is done loading, regardless of muting status, are a bunch of monotonically increasing timers, i assume counting time on page
in the end i think the worry is that they *can* do this. i am fairly confident that they're not doing this, to me and my browser at least, but nothing stops them from flipping a switch one day to make a muted player add a new flag in hls traffic (which i suspect is where they are doing their beancounting) so that it is ignored in counting
@codl Things might look dramatically different when using the app, where they have full control over the state of every UI control, and probably tons of telemetry to report on those?
@galaxis possible! although if they really are interested in that information, i don't know why they wouldn't collect it on the web as well
Chitter is a social network fostering a friendly, inclusive, and incredibly soft community.