You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That it is only reproducible with Firefox, but works on the other browsers is in line with the observations so far. It comes from the anti-tracking, which removes ids in requests that it considers fingerprints. Here it is a false-positive and thus removing it, breaks the soundcloud API. On the other browsers, removing it is not possible, since the API has been removed with Manifest V3.
I have not tried, but I would assume is not related to the Firefox version; but rather that the difference comes from using a different profile. This comment gives some background: ghostery/broken-page-reports#873 (comment)
In a nutshell, there are some preconditions what websites are visited and when the last anti-tracking bloomfilter update was fetched. I would expect that steps that reproduce it on a fresh profile would work the same on Firefox 133 and Firefox 134.
But thanks for sharing. I will keep it in mind to see if it makes a difference.
For about 2 weeks now soundcloud can't play with Ghostery enabled on Firefox 134. 133, Chromium and Safari based browswers all work fine
The text was updated successfully, but these errors were encountered: