just remove the locked: true bits on pdfalttext and translations then. i don't really care as i leave them off anyway
btw, i set locked: true on the others, matching ff (yes, ff port does not set locked on translation/alttextpdf)
tbh i just sync ff, but disabled by default is fine. i mean, lw already sets these same off-by-default, but doesn't add locked: anywhere. perhaps i could just not patch policy at all?
then without that, the only change is removing perplexityhonestly, removing the policy patch entirely would be the most puffy thing to do. that's what i'd recommend. but it's up to you lot. do as you please. my patches are largely advisory, for reference purpose but the ports team is in charge of what they merge.
so... choose :) Am 19.10.26 um 14:00 schrieb Stuart Henderson:
On 2026/10/19 13:50, Stuart Henderson wrote:On 2026/10/19 13:28, Leah Rowe wrote:i don't think translations/pdfalttext are disabled outright, i think it's just the AI bits.translations *are* in the "AI" group.my port turns off AI entirely, in librewolf. the firefox port also disabled AI, based on config provided by the justthebrowser project.grmbl, so *that's* why I couldn't find it any more, I thought they had just messed about with where it was in the UI and I hadn't found it yet.i do the same in librewolf. i don't think we should be putting strain on electricity and water needlessly in the browser.what you have is different than in firefox; the version in fx allows reenabling from prefs, the version you have doesn't (locked: true)
-- Company director, Minifree Ltd Registered in England, No. 9361826 | VAT No. GB202190462 Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK
OpenPGP_0x5C654067D383B1FF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
