From the menu, select the Settings option. To do this, select the three-dots menu icon in the top-right.To get around this problem (and if a few browser refreshes doesn’t fix the problem), you’ll need to clear your browser data and force Chrome to load a completely fresh version of the Twitch website. The outdated page that Chrome loads might not work as a result. For instance, a change in the Twitch backend could mean that your browser cache for the Twitch website is out of date.
Unfortunately, caching can cause issues on certain sites, especially if the site changes after your last visit.
This helps to load assets (like images and browser CSS files) more quickly, since these are unlikely to change often. Google Chrome, like most modern browsers, uses caching to quickly load pages you visit often. The stream should start to load, assuming ad-blocking was the cause of the issue in the first place. I can see how seeing your User ID is scary, but rest assured we are not storing it or passing it along in our proxied request.Once disabled, refresh the Twitch stream (and allow the ads to run). I personally don't have time to refactor the server and plugin currently, but I can put that on our roadmap as a feature. We pass your non-identifying arguments as part of the proxied request ie: fast_bread, supported_codecs, etc.easier to just pull all query parameters.It was implemented this way for a couple of reasons: Once again this data is not stored and is not sent as part of the proxied request. Once the handler call is complete your request falls out of scope and in turn, any identifying information in memory is gone. Depending on where you are located you will be hitting a server in new york or Germany where your request is parsed and then proxied. The endpoint you are hitting is also not some random proxy in Russia.
As per our privacy policy, we are not storing your twitch user ids or IP from the request. I just want to clear up any confusion on this topic. Posted this comment on the issue on our repo, but will paste it here as this is literally the same issue. Tested this myself and it does leak that information. This does not apply to Purple Ad-Block, which only sends the channel name." Not trying to scare people away as I'm sure it was just easier for them to implement it this way but still, it is a security risk. Hopefully the devs will remove this information from it's extension, as it shouldn't be needed. For obvious reasons this could be a problem. The extension currently leaks your Twitch user ID and personal IP to their Russian proxy. "Just a warning to those using TTV LOL, especially if you are a streamer.
0 kommentar(er)
