More about those zero-dot users

Yesterday’s article about KDE’s target users generated some interesting discussions about the zero-dot users. One of the most insightful comments I read was that nobody can really target zero-dot users because they operate based on memorization and habit, learning a series of cause-effect relationships: “I click/touch this picture/button, then something useful happens”–even with their smartphones! So even if GNOME and ElementaryOS might be simpler, that doesn’t really matter because it’s not much harder to memorize a random-seeming sequence of clicks or taps in a poor user interface than it is in a good one.

I think there’s a lot of truth to this perspective. We have all known zero-dot users who became quite proficient at specific tasks; maybe they learned how to to everything they needed in MS Office, Outlook, or even Photoshop.

The key detail is that these folks rely on the visual appearance and structure of the software remaining the same. When the software’s user interface changes–even for the better–they lose critical visual cues and reference points and they can’t find anything anymore.

On the desktop side, these people are the target audience for Long Term Support (LTS) distros, where the UI never changes for years at a time. This is exactly what they want because they prefer a bad yet unchanging UI to one that incrementally evolves to be better.

So I think if we want to reach these people, it will probably be done less by improving Plasma or KDE apps, but rather by being more attentive to our existing Plasma LTS offering and broadening it to encompass apps and frameworks as well. That way these other KDE products that are used alongside or underneath Plasma can benefit from more bugfixes without the UI changes of non-LTS upgrades. And we should increase the support period to 5 years or more. It’s 10 years for Red Hat Enterprise Linux! This is what’s needed to have a real LTS product and bring the zero-dot users into the fold.

However I’m not sure we have these resources right now. No KDE developer I know uses the Plasma LTS release. Working on old crappy code isn’t any fun. Backporting fixes is a thankless task. I think we would probably have to pay someone to be the full-time LTS developer-and-backporter if we wanted to have an LTS product worth of its name. It will most likely need to be on the back burner for a while. Hence, focusing on the one-or-more-dots users for the time being.

Who is the target user?

As a teenager, I played a lot of Vampire the Masquerade (VtM)–a tabletop role-playing game. One of the skills in which your character could become experienced was Computers, with ability measured from 0 to 5 dots:

This little table has stayed with me over time. As simple and crude as it is, I think it provides a reasonable measurement scale that can be used to guide software development: you need to decide how many dots in Computers a user must have before they can use your software, which helps you organize the user interface and prioritize features.

My sense is that currently most Linux-based software targets people with three dots in Computers or more, but is often usable for people with two dots. My wife is a solidly two-dot user who is happily using KDE Neon as her distro.

But how many zero and one dot users are out there? What fraction of the market are we abandoning by requiring two dots?

This question was answered a couple of years ago when the Organization for Economic Co-operation and Development commissioned a massive a study of adults’ computer skills, with over 200,000 participants (!!!) across 33 high-income countries. The Nielsen/Normal Group summarized the results, and here I’ll condense them even further:

25% of users cannot use computers at all. AT ALL! These people have zero dots in Computers according to the VtM scale.
14% can can perform easy and obvious button-driven tasks in single simple apps, such as sending or deleting an email. They also have zero dots in Computers, but would be on the higher end of zero. Maybe a little more than half a dot.
29% can use more advanced functionality in individual apps, such as searching for data that is not currently visible, or writing an email reply to multiple people and not just the sender. They have one dot in Computers.
26% can perform multi-step tasks involving more than one app, collate information from external sources, overcome minor errors and obstacles that occur during the process, and do some monitoring of background tasks for activity. They have two dots in Computers.
5% can perform complex tasks involving multiple data sources and apps with lots of navigation, transform imperfect data with tools to make it suitable for the required work, and succeed at ambiguous tasks with more than one correct outcome or possible approach to get it done, overcoming significant roadblocks along the way. These people would probably have three dots in Computers (even if they are not software engineers).

Let that sink in: almost 40% of adults in rich countries have practically no computer skills at all. This isn’t mentioned in the summary, but my personal experience with people in the lowest-skill group (25%) is that they can only use smartphones and tablets, while those in the next skill group (14%) still strongly prefer them over computers.

Another 30% of people have effectively one dot in Computers on the VtM scale. Taken together with the two lowest-skill groups, this means 70% of people’s computer skills are non-existent or very basic. Those with more advanced skills–two dots in Computers and up–are only about 30% of the population.

Maybe the dominance of the smartphone makes a bit more sense now…

KDE is never going to achieve world domination with software that can only be used by at most 30% of the market–those with two or more dots in Computers. To broaden our appeal, we need to make our software usable by at least the people in the next level down (one dot in Computers), which doubles the potential to 60% of the market–going from a minority to a solid majority.

BUT WAIT! Won’t this “dumb down” KDE’s software? Won’t we alienate our current audience of 2-and-3-dots-in-Computers users? After all, smartphone software optimized for zero-dot people is indeed really simple and limiting. So it’s a risk.

But I think good design and high customizability can make software elastic, suitable for users with a range of skills. Software with little or no customizability or poor design can probably only straddle two categories, so decent phone apps would be comfortably usable by people with 0-1 dots in Computers, maybe 0-2 dots with exceptional design. This pretty much matches the experience of myself and many people I know: those with more technical ability find most phone apps to be limiting and prefer using a computer for heavy lifting.

But well-designed software that’s customizable and has good default settings can accommodate a wider range of skill levels: people with 1-3 dots, or even 1-4 dots!

We can deliberately exclude the zero-dot people from our target audience, who are probably never going to be happy with KDE software. Our focus on power will bleed through in even the simplest apps, and just never appeal to them. GNOME and ElementaryOS can have those users. 🙂

This is what I think we should shoot for in KDE: software that is simple by default so it can work for 1-dot users, but powerful when needed via expansive customization, so that it can appeal all the way to the 4-dot users–which includes many KDE developers. This is currently a strength of KDE software, and it won’t be going away!

Essentially we need to fully embrace Plasma’s motto of “Simple by default, powerful when needed” all KDE software, not just Plasma.

I see a lot of this already happening via our simple-by-default Kirigami apps gaining power and customization opportunities, and our powerful-by-default QtWidgets apps gaining better default settings and a streamined appearance. So let’s keep it up!

Edit: check out this follow-up post: https://pointieststick.com/2021/11/30/more-about-those-zero-dot-users

This week in KDE: Fixing a bunch of annoying bugs

This was a major bug squashing week, with quite a lot of annoying issues fixed–some recent regressions, and many longstanding issues as well.

On the subject of bugs and recent regressions, I’m starting to think from a higher level about how we can prevent them. KDE has largely conquered our historical issues of excessive resource consumption and visual ugliness, and our next major challenge on the path towards world domination is reliability. One idea I’m toying with is starting an initiative to focus on the “15 minute bugs”–those embarrassing issues that can easily be found within just a few minutes of using the system normally. Here is a preliminary list of these issues in Plasma. I would encourage any experienced developers to try to focus on them! The impact will be very high.

Bugfixes & Performance Improvements

Creating archives using Ark’s main UI once again works (Kai Uwe Broulik, Ark 21.12)

Elisa no longer shows an error message instead of the number of tracks in the playlist footer when the playlist only has one track in it (Bharadwaj Raju, Elisa 21.12)

Okular’s zoom buttons now always enable and disable themselves at the correct times, in particular when a new document is opened (Albert Astals Cid, Okular 21.12)

Ark can now handle archives whose files internally use absolute paths, rather than relative paths (Kai Uwe Broulik, Ark 22.04)

Touch scrolling in Konsole now works properly (Henry Heino, Konsole 22.04)

Fixed a common crash in the System Tray (Fushan Wen, Plasma 5.23.4)

Fixed a common crash in Discover when using it to manage Flatpak apps (Aleix Pol Gonzalez, Plasma 5.23.4)

The logout screen once again has a blurred background and animates when appearing and disappearing (David Edmundson, Plasma 5.23.4)

In the Plasma Wayland session, dragging a file or folder from a Folder View popup into its parent folder no longer causes Plasma to crash (Marco Martin, Plasma 5.24)

In the Plasma Wayland session, when using a stylus, it’s now possible to activate other window from their titlebars and also just interact with titlebars more generally (Fushan Wen, Plasma 5.24)

Changing various settings in System Settings no longer causes a flickering effect behind Plasma panels (Vlad Zahorodnii, Plasma 5.24)

Repositioning a panel from horizontal to vertical or vice versa no longer causes the layout of the control strip to get kinda messed up (Fushan Wen, Plasma 5.24)

Activating the new Overview effect no longer causes auto-hidden panels to be shown (Vlad Zahorodnii, Plasma 5.24)

In the Plasma Wayland session, the Clipboard applet now shows entries for images added to the clipboard using the wl-copy command-line program (Méven Car, Plasma 5.24)

User Interface Improvements

Hovered and focused Breeze style scrollbars no longer blend in with their track so much (S. Christian Collins, Plasma 5.23.4)

Kate has been replaced with KWrite in the default set of favorite apps, since it’s a bit more user-friendly and less programmer-centric (me: Nate Graham, Plasma 5.24)

Discover’s somewhat confusing checkbox on the bottom of the Updates page has been transformed into a couple of buttons and a label which should be clearer, and it also doesn’t say the word “Updates” quite so many times on that page anymore (me: Nate Graham, Plasma 5.24):

When using PipeWire and streaming audio from one device to another, the audio stream now shows the name of the remote device in Plasma’s Audio Volume applet (Nicolas Fella, Plasma 5.24)

The Properties window for files now displays which app will open the file (Kai Uwe Broulik, Frameworks 5.89):

The icon selection dialog now pre-selects the folder’s currently-used icon for easier visualization and keyboard navigation (Kai Uwe Broulik, Frameworks 5.89)

Those little transient messages that sometimes appear at the bottom of the windows of Kirigami-based apps (which are nonsensically called “Toasts” in Android land) now have easier-to-read text (Felipe Kinoshita, Frameworks 5.89)

…And everything else

Keep in mind that this blog only covers the tip of the iceberg! Tons of KDE apps whose development I don’t have time to follow aren’t represented here, and I also don’t mention backend refactoring, improved test coverage, and other changes that are generally not user-facing. If you’re hungry for more, check out https://planet.kde.org/, where you can find blog posts by other KDE contributors detailing the work they’re doing.

How You Can Help

Have a look at https://community.kde.org/Get_Involved to discover ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

This week in KDE: most of GNOME shell in the Overview effect

This week the new KWin Overview effect gained the ability to shows results from KRunner when you search! This brings it fairly close to feature parity with GNOME’s central Activities Overview feature!

At this rate, we’re about halfway to implementing all of GNOME shell in the Overview effect

Thanks to Vlad Zahorodnii for this work, which lands in Plasma 5.24!

Other new Features

Gwenview now has “Print Preview” functionality, which as I’m sure you can imagine would be quite useful in an image viewer app (Alexander Volkov, Gwenview 22.04)

Discover now prevents you from doing anything that would uninstall Plasma in the process, which is probably not what you were intending to do (Aleix Pol Gonzalez, Plasma 5.24):

Bugfixes & Performance Improvements

When you print an image in Gwenview or Kolourpaint, it now automatically defaults to printing in portrait or landscape mode according to the image’s aspect ratio, rather than making you set this manually (Alexander Volkov, Gwenview 21.12)

Konsole now releases memory when you clear the text (Martin Tobias Holmedahl Sandsmark, Konsole 22.04)

Konsole now has better text display performance (Waqar Ahmed and Tomaz Canabrava, Konsole 22.04)

The Alacritty terminal once again opens with the correct window size (Vlad Zahorodnii, Plasma 5.23.4)

Toolbar buttons in GTK3 apps that don’t use CSD headerbars (such as Inkscape and FileZilla) no longer have unnecessary borders drawn around them (Yaroslav Sidlovsky, Plasma 5.23.4)

The open/save dialogs in Flatpak or Snap apps now remember their previous size when re-opened (Eugene Popov, Plasma 5.23.4)

The “Show in file manager” text in Plasma Vaults is now able to be translated (Nicolas Fella, Plasma 5.23.4)

The Task Manager’s textual list of grouped apps is now much faster and more performant (Fushan Wen, Plasma 5.24)

Discover now eventually stops searching after no further search results are found, instead of always displaying “Still looking” at the bottom (Aleix Pol Gonzalez, Plasma 5.24)

Fixed an issue with playing certain embedded videos in the Plasma Wayland session (Vlad Zahorodnii, Plasma 5.24)

Fixed a major performance issue in QtQuick-based KWin effects for NVIDIA GPU users (David Edmundson, Plasma 5.24)

The new Overview effect is now much faster to activate (Vlad Zahorodnii, Plasma 5.24)

Tons and tons of small bugs with Breeze icons have been fixed–too many to individually list! (Andreas Kainz, Frameworks 5.89)

Fixed a visual glitch with Plasma tooltips flickering when they appear or disappear (Marco Martin, Frameworks 5.89)

Icons and text in Plasma applet tabs are once again centered as intended (Eugene Popov, Frameworks 5.89)

User Interface Improvements

Elisa’s default album icon is now prettier and more semantically appropriate (Andreas Kainz, Elisa 22.04):

The new Overview effect is now touch-friendly (Arjen Hiemstra, Plasma 5.24)

The touchpad applet has been restored after getting removed in Plasma 5.23, and is now back as a read-only status notifier that simply shows visually when the touchpad is disabled, like the caps lock and microphone notifier applets (me: Nate Graham, Plasma 5.23.4):

The weather applet’s location configuration dialog now automatically searches through all available weather sources rather than making you first select some manually (Bharadwaj Raju, Plasma 5.24):

Discover now presents a more user-friendly set of messages when there is an issue installing updates (me: Nate Graham, Plasma 5.24):

This is a simulated error message, of course. 🙂 But it’s what a normal error message seems like to regular people!

Discover’s search field no longer auto-accepts a few seconds after you stop typing; now it only initiates a search when you explicitly hit the Enter or Return key (me: Nate Graham, Plasma 5.24)

Opening a Plasma Vault and displaying its contents in your file manager now creates a new file manager window for this purpose instead of re-using any existing ones, since this didn’t work with various combinations of activities and virtual desktops and especially when using the “Limit to the selected activities” setting (Ivan Čukić, Plasma 5.24)

…And everything else

How You Can Help

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

Be flexible to win big

My goal of KDE Plasma World Domination is not a secret at this point. But what does it truly take to get there?

Let’s look at the existing market leaders in the OS space: Microsoft’s Windows and Google’s Android. Neither was the first to market, but they were the first to successfully serve the mass market. Neither is picky about what kind of software you run on them or write for them, so they are used on a wide range of devices by lots of different people. Both work with others in adjacent industries, rather than taking a “my way or the highway” approach. They are flexible.

Before KDE, I came from the Apple world, which takes a different approach. Apple identifies distinct use cases and focuses their efforts like a laser on making them as polished as possible. This works very well, but it requires ignoring, abandoning, or explicitly blocking other use cases, and sometimes inventing new things that conflict with what others are doing, in the hope that their new thing takes over. It requires saying “no” a lot and being opinionated.

Apple’s opinionated approach worked well for me with my own personal use cases in my pre-KDE days, as it did for many millions of other people. But evidently it doesn’t work for everyone, as Apple’s products routinely fail to crack 15% market share. And when they do, they often fall back down to that level after competitors emerge. But that’s okay, because Apple isn’t going for the mass market anyway; they’re happy in their profitable and opinionated boutique niche.

But that’s not KDE, and it never has been; we’ve always dreamed of a broad scope and being useful for everyone. This is what’s behind Plasma desktop’s extreme flexibility; Plasma Mobile for phones; Plasma Bigscreen for TVs; and Plasma Nano for embedded devices. It’s why the Steam Deck handheld gaming console, PinePhone smartphone, and JingPad A1 tablet are built on top of KDE technology.

To be the market leader, you must be flexible enough to accommodate everyone’s weird and random use cases. This includes grandmas, gamers, businesspeople, students, teachers, phones, tablets, shared family PCs, kiosks, and everything in between. It means you have to give up a certain amount of that laser-focus on making a particular use case bulletproof, in favor of flexibly accommodating everyone and working with partners to support their needs so that they can build their products on top of your platform. Windows and Android do this, and so does KDE.

This, fundamentally, is why I believe KDE can and will take over the world. We share the market leaders’ winning strategy and culture of flexibility, and we can supplant them by leveraging our advantages of being free and eternal, our resistance to turning evil because of our diverse stakeholders and decentralized leadership model, and our philosophy of keeping the user in control rather than exploiting them for ad or upgrade revenue.

So I think ultimately we will become the Windows or Android of the Free Open-Source Software world, with projects like GNOME and ElementaryOS competing to be the Apple of FOSS. I think there will absolutely be room for projects like theirs; in fact I think it’s highly likely that they’ll offer a better user experience than we do for people who fit within the usage paradigms they focus on–just like Apple does.

None of this means that we actually have to make our stuff look or behave like Windows or Android, of course. But it means we need to retain their philosophy of not shutting anyone out. We need to stay willing to make changes for vendors who want to ship our software and developers who want to write apps for our platform. We need to keep listening to our users and trying our best to make our software work for them. We need to remain flexible.

And I think we’re doing this. Which is why we’re going to win.

It may take a few decades, but I believe it’s going to happen. If you agree, help get there faster! This crazy thing only works because of people like you and me and all of us. There is no “they” in KDE. So c’mon, get involved and let’s take over the world together.

This week in KDE: Primarily Centered Hamburgers

This week brings several exciting and long-awaited changes, including KHamburgerMenu in Okular, Primary Monitor on Wayland, and Centered window placement by default! Read on to find out the details:

New Features

Okular has now adopted KHamburgerMenu, so you can now hide the menubar for a slim, modern look without losing access to any features! Note that in Okular this is not on by default; you have to manually hide the menubar first. (Felix Ernst, Okular 21.12):

Did you know that Okular can open and display Markdown files? Isn’t that cool!?

In the Plasma Wayland session, we have implemented the concept of the “primary monitor”, and it does the same thing on Wayland as it does in the X11 session (Aleix Pol Gonzalez, Plasma 5.24)

Bugfixes & Performance Improvements

Okular no longer crashes when opening a Markdown file containing any images with alt text that are inside links (Albert Astals Cid, Okular 21.12)

Ark now correctly handles zip files whose internal metadata uses backslashes as path separators (Albert Astals Cid, Ark 21.12)

In the Plasma Wayland session, Yakuake’s “Keep window open when it loses focus” setting now works (Firlaev-Hans Fiete, Yakuake, 21.12)

Fixed a random KWin crash (Aleix Pol Gonzalez, Plasma 5.23.3)

In the Plasma Wayland session, a few glitches in KWin’s adaptive sync support have been fixed (Xaver Hugl, Plasma 5.23.3)

You can once again activate items in Kickoff using a stylus/graphics tablet pen (Fushan Wen, Plasma 5.23.3)

The new Wayland-compatible keyboard layout System Tray applet is no longer missing the Esperanto flag (Fushan Wen, Plasma 5.23.3)

When your battery is at a critically low level and Plasma notifies you about it, the notification now goes away automatically when you plug in the power cord (Kai Uwe Broulik, Plasma 5.23.4)

The Media Frame applet now supports displaying images from folders whose names contain unusual characters such as backticks (Patrick Northon, Plasma 5.23.4)

In the Plasma Wayland session, it is now possible to run an XWayland app as a different user (Weng Xuetian, Plasma 5.23.4)

On the System Settings Display & Monitor page, text in the “revert this change” dialog no longer gets cut off when using a language with long words like German or Brazilian Portuguese (me: Nate Graham, Plasma 5.23.4)

Fixed a case where the Plasma Wayland session could crash on logout (Xaver Hugl, Plasma 5.24)

When not using the systemd startup feature, Plasma now properly cleans up after itself on logout, terminating all processes that it launched as expected (Aleix Pol Gonzalez, Plasma 5.24)

When clicking the “Check for Updates” button in Discover while only the Flatpak backend is active, it now appears to do something (Aleix Pol Gonzalez, Plasma 5.24)

Searching for cities in the Weather applet using the BBC UK Met search provider should now be more reliable (Bharadwaj Raju, Plasma 5.24)

In the Plasma Wayland session, Plasma OSDs showing things like the current volume and brightness levels no longer inappropriately respect KWin’s Maximized window placement policy, so they don’t end up huge when using that policy (Marco Martin, Frameworks 5.89)

In the Plasma Wayland session, clicking on the hamburger menu button of a QtWidgets app like Dolphin or Gwenview or Okular while its window is unfocused no longer causes the menu to appear as a standalone window (Felix Ernst, Frameworks 5.89)

In System Settings and Info Center, the title rows of QtQuick-based pages no longer oddly fade in as they load (me: Nate Graham, Frameworks 5.89)

The KCommandBar no longer shows empty space on the right side (Eugene Popov, Frameworks 5.89)

User Interface Improvements

Newly-opened windows are now placed in the center of the screen by default (me: Nate Graham, Plasma 5.24)

App list items in Discover now have a more attractive and logical layout (me: Nate Graham, Plasma 5.24):

Hopefully this should address some of the complaints about Discover in https://www.youtube.com/watch?v=XzdEHrPbYiE

In the wallpaper chooser, previews now use the same aspect ratio as the screen whose wallpaper you’re choosing, so the preview will be visually accurate (Iaroslav Sheveliuk, Plasma 5.24):

The Display Configuration applet no longer has three configure buttons (me: Nate Graham, Plasma 5.24)

The Battery & Brightness applet now shows the battery status of more devices, including more types of Bluetooth devices in particular (Nicolas Fella, Frameworks 5.89)

The KCommandBar now shows a placeholder message when your search returned no results (Eugene Popov, Frameworks 5.89)

…And everything else

How You Can Help

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

This week in KDE: more stability, more features, prettier bug tracker

New Features

Skanlite now has a “batch mode” feature for flatbed scanners without an automatic document feeder. This will automatically take a new scan after a few seconds, to speed the process of scanning a lot of things. Skanpage is getting this soon as well! (Alexander Stippich, Skanlite 21.12)

Bugfixes & Performance Improvements

Annotating screenshots with transparency in Spectacle no longer causes the transparency to get replaced with a solid white color (Julius Zint, Spectacle 21.12)

The Plasma Networks applet now lets you successfully connect to an OpenVPN server with passphrase-secured .p12 certificate (Jan Grulich, Plasma 5.23.3)

In the Plasma Wayland session, turning an external monitor off and back on again no longer makes Plasma crash (Oxalica F., Plasma 5.23.3)

Fixed a case where launching System Monitor could cause the ksgrd_network_helper process to crash (Arjen Hiemstra, Plasma 5.23.3)

In the Plasma Wayland session, hovering over the Digital Clock applet to make it show its tooltip no longer sometimes makes Plasma hang (Marco Martin, Plasma 5.23.3)

The Minimize All effect/widget/button now remembers which window was active and makes sure that window ends up on top when restoring all the minimized windows (Vlad Zahorodnii, Plasma 5.23.3)

Switching a panel widget to an alternative one using the “Alternatives…” popup no longer rearranges your widgets (Alexander Lohnau, Plasma 5.23.3)

In the Plasma Wayland session, the show/hide animation for a panel set to auto-hide mode now works (Vlad Zahorodnii, Plasma 5.23.3)

Switching between virtual desktops when there are maximized windows no longer causes the panel to flicker, especially when using a dark color scheme or Plasma theme (Niccolò Venerandi, Plasma 5.23.3)

Fixed one of the most common sources of crashes in System Settings which could be triggered when navigating rapidly between pages (Harald Sitter, Frameworks 5.88)

When using a 3rd-party icon theme, any icons that the app requests which aren’t available in the active theme are now displayed from the theme’s specified fallback icon theme, rather than just being missing (Carl Schwan, Frameworks 5.88)

In the Plasma Wayland session, pasting arbitrary clipboard content into a file now works (Méven Car, Frameworks 5.88)

Excessively long labels in System Settings’ grid-style pages now get elided rather than overflowing (me: Nate Graham, Frameworks 5.88)

User Interface Improvements

KDE’s venerable bug reporting website – https://bugs.kde.org – was given a facelift recently, and it’s now much more attractive and visually pleasant to use! Thanks to Debarpan Debnath for this work!

Spectacle’s notifications about screenshots you took using a global shortcut no longer display duplicate text (Antonio Prcela, Spectacle 21.12)

The “big focus rings” feature in Plasma 5.24 has been backported to Plasma 5.23, as it solves a number of focus-related bugs and issues and has proven stable so far (Noah Davis, Plasma 5.23.3)

Windows now remember the screens they were on when those screens are turned off or unplugged, and will snap back to them when those screens come back. This should fix a huge class of multi-monitor annoyances! (Vlad Zahorodnii, Plasma 5.24)

Critical notifications now have a little orange strip on the side to visually distinguish them from background clutter and generally help them stand out so that you will be more likely to notice them (me: Nate Graham, Plasma 5.24):

With a thin-ish panel, System Tray icons now have the same spacing in “Small” mode that they do in “Scale with Panel” mode (Fushan Wen, Plasma 5.24)

The odd behavior of middle-clicking on a panel to create a sticky note has been disabled by removing the relevant entries from the config files of people who still has them in there for some reason (me: Nate Graham, Plasma 5.24)

The Breeze icon theme has gained a bunch of folder icon with various different semi-common-ish icons and emblems on them (Andreas Kainz, Frameworks 5.88):

The standard Kirigami placeholder icon for an image that is unavailable or still loading no longer looks like the Windows logo (Aleix Pol Gonzalez, Frameworks 5.88)