Eclipse Community

Plasmafox (all versions) is incompatible with Firefox Language Packs!

Yeah I'm just not going to bother with language packs at this point. Mypal68 hasn't and it's been fine.

the_r3dacted wrote: ↑11 Jun 2026, 08:26 I'm just not going to bother with language packs at this point.

Don't bother with language packs but don't block them from being installed.
I know many people who won't use a browser if it's not in their native language.

I'm not intentionally blocking it, it's just multiple changes are not compatible with them.

Duke wrote: ↑10 Jun 2026, 16:57 Hardware acceleration is back with Plasmafox v153.0a1

Looks like it's kind of borked though, because I've tried with a quite old graphics card and about:support shows hardware acceleration decoding available for H.264 + VP9 + AV1.
VP9 I'm not sure, or maybe its very first generation. But AV1, no way, not a single chance at all!

EDIT: after more investigation not even VP9 with this 12 years old Nvidia card.

the_r3dacted wrote: ↑11 Jun 2026, 11:28 I'm not intentionally blocking it, it's just multiple changes are not compatible with them.

... Less than a year ago, when r3dfox was in the lower 140s, Firefox langpacks were fully compatible with it, leaving only the "redfox configurations" part of "about:preferences" untranslated (remaining in en-US); then, the "LibreWolf-ification" of r3dfox started gradually to take place, and that part was a conscious/intentional change; LibreWolf itself has become incompatible with upstream Firefox, to the point that LW now has to supply its own langpacks for i18n purposes...

And r3dfox now is in a state where, due to "multiple changes" (many originating from the LW fork), it has also become incompatible with Fx langpacks (and, I assume, also with LW langpacks) ; GH issues about this breakage have already been reported:

https://github.com/Eclipse-Community/r3dfox/issues/168

https://github.com/Eclipse-Community/r3dfox/issues/172

https://github.com/Eclipse-Community/r3dfox/issues/178

So, with much respect to the r3dfox author, the Fx langpacks breakage, for me, came as a consequence of certain concrete intentions, i.e. it's not a random accident ...

Another thing that kind of irks me is the frequent comparison to the MyPal68 browser; they are different projects, aren't they? With different target groups, probably (MyPal68 mainly appealing to XP-die-hards); I appreciate that their authors may share code/ideas/etc., as is the case with the e3k Chinese dev, but why should it be acceptable for a r3dfox user that MyPal68 is also broken when it comes to Fx langpacks? FWIW, the Russian community of MyPal68 users has contributed this; I don't think we'll see something like that for r3dfox and, in any case, I don't speak Russian myself ...

Regards.

A note:
If you switch the setting under Privacy & Security > Enable DNS over HTTPS using from "Default Protection" to "Increased Protection," R3dfox will no longer start.

Nobody wrote: ↑12 Jun 2026, 00:21 If you switch the setting under Privacy & Security > Enable DNS over HTTPS using from "Default Protection" to "Increased Protection," R3dfox will no longer start.

Already known and reported bug :

https://github.com/Eclipse-Community/r3dfox/issues/145

https://github.com/Eclipse-Community/r3dfox/issues/162

GoodConscience wrote: ↑11 Jun 2026, 21:15 Less than a year ago, when r3dfox was in the lower 140s, Firefox langpacks were fully compatible with it, leaving only the "redfox configurations" part of "about:preferences" untranslated (remaining in en-US); then, the "LibreWolf-ification" of r3dfox started gradually to take place

And r3dfox now is in a state where, due to "multiple changes" (many originating from the LW fork), it has also become incompatible with Fx langpacks

Yes, I totally agree and this is a real problem for many people.
LibreWolf bits when it's about security, and that doesn't mean anonymity, are ok but that shouldn't break such basic features like language packs.

Hello everyone
I'm not a native english speaker so bear with me.
First things first, many thanks for this fork

Has anybody else had problems with logging in twitch.tv ?
When I try, it says my browser is not a supported one.
This happened since some months ago, and it's still happening today,
with the latest version of r3dfox I have, ie 153.0a1 (2026-06-09) (64-bit).
I tried with a user-agent override with
- general.useragent.override.twitch.tv
- Mozilla/5.0 (%OS_SLICE%; rv:149.0) Gecko/20100101 Firefox/149.0
but it didn't work.
Any ideas?
Should I wait for future release?

Regards

Milkyway wrote: ↑12 Jun 2026, 14:27 Has anybody else had problems with logging in twitch.tv ?
When I try, it says my browser is not a supported one.
This happened since some months ago, and it's still happening today,
with the latest version of r3dfox I have, ie 153.0a1 (2026-06-09) (64-bit).
I tried with a user-agent override with
- general.useragent.override.twitch.tv
- Mozilla/5.0 (%OS_SLICE%; rv:149.0) Gecko/20100101 Firefox/149.0
but it didn't work.

Hi and welcome to the forum

No problem with Twitch.tv for me with both R3dfox v151.0.2 and Plasmafox v153.0a1.
I'm using: "general.useragent.override" = "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0"

I don't like to use the %OS_SLICE% thing because Firefox v151 is not supposed to run on Windows 7 or 8. Some sites may detect that.

But the version number has to be changed on each new version of Firefox because some sites don't like browsers which are more than one or two versions older than the current release version.
Current release of Firefox is v151 but v152 is to be released on next tuesday the 16th of June.