It only checks mirror latency every transaction if you enable “fastestmirror”. Repositories are only synced if the local cache is out of date or the metadata timestamp has changed. There might be a way to prevent dnf from refreshing repository metadata at all, but I really don’t think that’s a good idea.

In my experience, dnf has pretty good mirror selection by default. Setting “fastestmirror=true” replaces the more complex mirrormanager2 heuristic, which tries to select an appropriate mirror by available bandwidth, with a simple latency check that runs before transactions. In most cases this has no effect or worsens dnfs performance. They changed the description in dnf5 to better reflect the behaviour.

Having said that, it’s worth giving a try in a case like this. I just want to make sure that people realize that there is a reason this was never enabled by default, since this is a popular configuration tweak suggested all over the internet, whose actual function very few seem to know.

Good marketing or influencers perhaps? I’m not sure but I’ve been wondering myself.

If you use omarchy, you have bad taste.

The default paste action is pretty much the only thing preventing anyone from picking a different function for the button. That’s the the biggest reason for reversing the default behaviour.

There are programs that use the middle mouse button but also support pasting from clipboard. I’ve been annoyed at work plenty of times when I’m trying to translate across a canvas but accidentally paste a random node of text. Bonus points if it contains some kind of password that was still in your clipboard. I don’t think it’s a good default.