Proposal: Hide quantization labels (e.g., Q8_0) for a cleaner UI in model selector

[MikaKrul]

Right now, the model download cards display the specific quantization format next to the file size (e.g., Q8_0). While Handy does a fantastic job of keeping the interface accessible with intuitive "accuracy" and "speed" progress bars, the raw quantization string feels like unnecessary technical jargon for the average user. Most non-technical users won't know what it means, nor do they need to care, as the download size and performance bars already give them all the practical context they need.

I propose hiding the quantization label by default to declutter the UI. It could still be shown in "Debug Mode" if it is explicitly enabled in the application.

[cjpais]

I would accept a PR to clean this up

[MikaKrul]

I opend a PR: #1685

[Marutselu]

I do not agree with the reasoning behind this change. Quantization information is well known, and it doesn't clutter the UI at all. It is very useful information. Removing it is a change for the worse and debug mode is not easy to turn on.
How do you even turn debug mode on and what other drawbacks does debug mode have, like extra CPU and IO operations for logging?
At least make an option in the settings to turn advanced mode on to see the model information.

[MikaKrul]

A simple way to toggle debug mode is to press Ctrl + Shift + D.

The idea of hiding the quantization labels by default is to keep the user interface clean so non-technical users don't get overwhelmed by terms like Q8_0. Downloading models isn't a daily task, so the accuracy and speed bars usually give enough context for practical purposes.

However, you make a great point about advanced users wanting direct access to this information without the potential obscurity of a hidden debug mode shortcut. A solid compromise would be adding a toggle for this under Advanced Settings (e.g., "Show advanced model details"). This keeps the main UI clean by default but gives power users an easy, documented way to view the exact formats.

Should @cjpais agree with this approach, I will be more than happy to update the PR to move the toggle there.

[cjpais]

Right now, I'm going to hold off on further changes just due to code churn. We definitely need better modes for advanced users in this kind of thing, but that requires rethinking the app a bit more end-to-end, including onboarding, not just like adding a toggle somewhere. So it needs a more holistic thinking about the user experience and how that fits within the application itself