The graphene community in the past has pointed out Firefox’s incomplete content sandboxing implementation and suggested that other aspects of security are not up to chromiums standard. They pointed out other technical shortcomings as well, though I can’t recall them, I’m not sure how urgent they’d be.

This was several years ago, and I’m not sure if any of this has been addressed, but I wouldn’t like to rely on manifest v3 compliant ad blocking.

I get the impression that Firefox may continue to lag in this regard, and I don’t feel that people like us are made vulnerable by this, though I do worry about people like my parents.

yeah, they do that 😅

where do they find the time?!

joined 38 minutes ago.

this was the wildest thing to me

I managed to resolve this by slightly loosening the top screw, they work fairly reliabily now. I need to look into perhaps increasing the friction of the scroll wheel, as I’m finding that sudden movement causes it to rock and scroll accidentally. I’m wondering if I could grease the ends of the scroll bar or something to that effect.

stumbled upon this really cool mod leveraging megnets to introduce some tactility to the mousewheel, I might need to pick up an FDM printer to experiment 😊

e: seems the revised model leverages magnets to increase friction only, but I think that would also work

where’s the bats angels comic 🥺

One of the comments on the phoronix post mention display stream compression (DSC) and fixed rate link (FRL - specific to HDMI 2.1), both assist with high bandwidth throughput.

Mine arrived today, have you ever had issues where holding down RMB also holds down LMB with it? I’ve experimented with loosening the top screw slightly, and it’s greatly improved this behaviour but I don’t believe it’s been eliminated.

No but I do get about three or four challenges. I can paste the article for you if it helps?

archive link

https://archive.is/N4thi

Thanks for these, I’ll discuss with the DAL team when I get the chance

Oh sorry, I misunderstood, so you actually get locked into a low mclk under specific display configurations? I’ve genuinely never heard of or personally experienced that across a breadth of hw and sw configs.

I’m wondering if it could be worth probing the power play sysfs interface or hwmon the next time this happens to try and understand what’s happening there.

Do you use client apps to interact with tuning settings like LACT? Can you link me to an existing bug report so I can follow up with engineering?

Can you elaborate on your display config?

You kind of alluded to part of it there; it’s not so much a bug in sw/fw as it is a hardware limitation at both the adapter and display side. The variables for displays are vertical blanking intervals (and differences between panels), as well as total display bandwidth.

with RDNA2, a feature was implemented in DAL to leverage VRR in order to allow a single connected display system to achieve a lower mclk, and thus lower idle power draw. With RDNA3, hardware changes (MALL specifically) broadened this capability two concurrent displays. Even then, it’s not bulletproof.

The display eng team has more or less exhaustively worked towards this over the course of RDNA3’s lifespan; their work is applicable to both Windows and Linux.

Do you have an OSD for active refresh rate built into your displays? FreeSync / VRR can be managed directly by your DE settings

I think you went from a 25.10 branch at a point where the KMD split had already occurred. This means that support for kmd3 devices (RDNA3+4) was not present, which lead to the abject chaos you saw on windows

I’m curious about the network remark though. Was this on windows 10 or 11? Can you tell me which platform (motherboard chipset) this is with?

how is it a sub par GPU given it targets a specific segment (looking at it’s price point, die area, memory & power envelope) with its configuration?

You’re upset that they didn’t aim for a halo GPU and I can understand that, but how does this completely rule out a mid to high end offering from them?

the 9000 series is reminiscent of nv10 versus vega10 GPUs like the 56, 64, even the Radeon 7; achieving equivalent performance for less power and hardware.

no it’s fine, I thought you had the inside scoop there for a sec 😅 I’m sure we’ll see an android build eventually.

either way, I think we’re pretty well served for Firefox forks across desktop and mobile

nah just the OP was asking for android specifically

Is there a mobile version for this yet?

Fennec on fdroid perhaps?