The problem with all these Firefox forks is most of them are dead ends, development wise. They don’t contribute upstream. Maybe Tor excluded.

Hopefully this one is different, it does seem to have some actual code behind it rather than just disabling features.

Mostly that it doesn’t work on Steam Deck. Hits memory limits IIRC.

It would allow them to do HDMI FRL also, which is probably what you mean when you say HDMI 2.1. AMD cards also do HDMI FRL I thought. FRL is what allows things like 4k120Hz (higher bandwidth modes). The VRR that the Dock does is the VRR standardized with 2.1, which is why it works on TVs and devices that do not support freesync (see: LG TVs).

Anyway, the Dock doesn’t have a fast enough HDMI converter to do that. It’s not a licensing issue. Next gen Deck/Dock will probably do it.

Actually it works fine on Steam Deck. It uses VRR over DP to the dock, which then translates it to HDMI with VRR. The dock has proprietary firmware to do this.

Intel and Nvidia hardware with open source kernel drivers also do a similar trick where the HDMI part is in a firmware blob. Only AMD does not work with HDMI VRR.

Hah! I wish it was email, so I could ignore it. Instead it’s either a Slack DM, which escalates to a phone call.

Yes it is. It’s not in mainline wine, it’s been in kernel for a long time now.

It’s annoying all the articles are focusing on performance versus stock wine here when basically everyone uses Proton or a fork of it anyway, which has had fsync for years now that does similar performance uplift.

The story here should be that we’re getting fsync level performance with fewer bug and it can be upstreamed to wine. There is no relevant performance uplift for Proton users, but I guess performance gets clicks so that’s the story all the press are going with.

It’s not merged, but the benchmarks are against upstream wine. Proton has hacks (fsync) that have almost identical performance uplift but were not suited to upstreaming.

So basically this will improve “correctness” versus current Proton, not performance. Should fix some bugs and improve compatibility.

Versus stock wine, it’s a huge perf uplift though.

What’s wrong with the Flatpak permissions system on Linux?

Knowing Mozilla it’s probably done client side (meaning it sends weather data for all major regions or something and the client filters what is needed)

*Ik ben

Good read. Makes sense and not even that complex, good that they did this experiment anyway just to prove it out to those less technical and try to get prevention steps out there.

Technically AMD also offers an open Vulkan driver (AMDVLK), it’s just dog shit, and an open compute driver (Rocm), its just also bad, and an open OpenGL driver (Radeonsi), which is solid.

Those three are all primarily developed by AMD engineers and are fully open. Nvidia has no such open equivalents.

Uhh nvidia has had native Linux drivers since the 1990’s…

That also doesn’t resolve the carrier seeing which IPs you’re connecting to, which can often be traced back to services or sites.

The addresses themselves that you’re connecting to as one example. Also often DNS.

The web UI was also vastly superior to Hotmail or Yahoo

It’s pretty drastically harder to register 100 phone numbers, especially in your target region, than 100 email addresses. Major spammers and such work with automation across many accounts, this isn’t designed around someone with 10 accounts.

Ok… That’s too long. Weird decision.

I suspect the small delay is just to prevent them from going crazy if you swing your mouse over the tab bar, it’s not going to be like a second or something. Sounds useful for the case of multiple tabs on the same site with similar titles, especially at higher resolutions.