If anyone else was wondering why some websites and the "Alternate Player for Twitch.tv" extension stopped working in the latest Librewolf update, it's because they changed the userAgent string from Firefox to LibreWolf and way too much shitty code is confused by it looking like firefox but then not being firefox.

top 9 comments

sorted by: hot top controversial new old

[–] Lucien@mander.xyz 14 points 1 week ago

I spoof mine to say chrome; got tired of lying ass websites saying their page doesn't work in Firefox. First, fix your shit if that's the case. Second, yeah, it probably does.

[–] roguelazer@lemmy.world 6 points 1 week ago

Be careful what you wish for, that's how you end up with Chrome's weird semi-proprietary Sec-CH-UA headers

[–] kbal@fedia.io 5 points 1 week ago (1 children)

... and they've changed it back.

[–] Yingwu@lemmy.dbzer0.com 1 points 1 week ago (2 children)

Really? If so they haven't pushed it to the main Debian repository

[–] kbal@fedia.io 1 points 1 week ago

Changed in 138.0-2, reverted in 138.0.1-1 which I got from repo.librewolf.net.

[–] kbal@fedia.io 1 points 1 week ago

According to @librewolf@chaos.social it's still a problem in the current build if you have resist fingerprinting turned off.

[–] gencha@lemm.ee 3 points 1 week ago

You can't stop sending it. That triggers bot detection. If you send a fake header, that doesn't match existing fingerprints of that browser, bot detection.

[–] Yingwu@lemmy.dbzer0.com 1 points 1 week ago

Yep, just got this problem too.

[–] dirtycrow@programming.dev 1 points 1 week ago

Browsers have gotten too complicated.