Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Soundcloud Issues on Firefox Nightly 134 #2050

Open
VinylNerd opened this issue Nov 13, 2024 · 3 comments
Open

Soundcloud Issues on Firefox Nightly 134 #2050

VinylNerd opened this issue Nov 13, 2024 · 3 comments
Assignees
Labels
Anti-Tracking Issues related to Anti Tracking Bug Something isn't working Firefox

Comments

@VinylNerd
Copy link

VinylNerd commented Nov 13, 2024

For about 2 weeks now soundcloud can't play with Ghostery enabled on Firefox 134. 133, Chromium and Safari based browswers all work fine

@philipp-classen philipp-classen self-assigned this Nov 13, 2024
@philipp-classen philipp-classen added Firefox Anti-Tracking Issues related to Anti Tracking Bug Something isn't working labels Nov 13, 2024
@philipp-classen
Copy link
Member

philipp-classen commented Nov 13, 2024

Thanks for reporting!

We keep a thread here: ghostery/broken-page-reports#873

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 was hoping that anti-tracking system learned that the value is safe (ghostery/broken-page-reports#873 (comment)), but looks like the problem is still present.

@VinylNerd
Copy link
Author

Actually, its working on firefox 133 for me, only 134 nightly has the issue, would be great if this is fixed before 134 goes into beta

@philipp-classen
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Anti-Tracking Issues related to Anti Tracking Bug Something isn't working Firefox
Projects
None yet
Development

No branches or pull requests

2 participants