 As you know, KD has a very tribalistic culture, that is every KD developer who's found out to contribute to other projects is immediately pushed out of the KD community. But then, how do you explain this? Well, this is Nate Graham, and is the holder of the Pointiest Stick blog, which, of course, you all read, so you know the person, and this, this is Gnome Shell, and this is a merge request, which was actually merged, so the code you're seeing actually got, sorry about that, actually got inside of Gnome Shell, made by Nate Graham, which means that now every time Gnome users use Gnome, there is some Nate KD developer codes inside of it, which you can make fun of to like Gnome users, I guess, just kidding. But how did this happen? And first of all, what's the merge request? Well, it's a rather simple one, but nonetheless important. Let me zoom in. So what it does now, it checks for this single main window desktop information from the applications. If the app is explicitly telling us via desktop file, then we know for sure. So it's reading the desktop file and searching, sorry, for the single main window property. Now, what is the single main property? Honestly, I don't know, it's technical details, I'm not here to discuss about that, but notice the line that's very after that, which is it's immediately checking if it has the XGnome single window property. So it seems like this property is the same as this one, but Gnome, in here it's explained that Gnome specific key for backwards compatibility. Okay, so what's going on? So Gnome had this single window property, and then somebody, which is still Nate, came and made that standard, a free desktop standard. And what that means is that merge request another was created this time in XDG, XDG specs, that says, look at here, there is, sorry, there is a new property, which is called single main window, as you can see here. And if true, the application has a single main window and does not support having additional one opened. This key is used to signal to the implementation to avoid you for offering a UI to launch another window of doubt. This key is only a hint and support might be no present, depending on the implementation. Okay, so if you have an application that can't be opened more than one time, like as an example, system settings, then these properties should be set to true. And Gnome did that, but to have that, they had their own property. And now that property, which of course, could only be read from Gnome, really. I mean, technically, Katie could read for the xGnome property, sorry, but I mean, xGnome property. Now it's a standard, it's just single main window, and everybody can use it. And that's really important. So you might rightfully ask, of course, my computer was going to sleep. It's a bit too soon, sorry about that. What's free desktop? So let's go go free desktop. Is this thing here, free desktop.org hosts the development of free and open source focused on interoperability and shared technology for open source or was I for open source graphical in desktop systems. We do not ourselves produce a desktop, but we aim to help others do so. And how do they do that through software and specifications. So the idea is there are some interoperability specifications that all desktops implement or in theory should implement that helps a single application to work well in more than one desktop. And that's really useful if you think about it. Because of course, the Linux ecosystem is going to have some amount of apps. And if that amount of us up is split depending on the desktop environment you use, and it's not going to feel as a nice experience to use apps from another desktop, then the amount, the actual amount of apps that you can use in a nice way will decrease. And if we want to be the Linux ecosystem and try to compete against windows and making touch, we can't allow ourselves to do that. So interoperability specification and look at how well I pronounce interoperability are really important truly. And in this case, the spec we've just seen is under the name of XDG spec. And as is declared here, XDG stands for cross desktop group, which sounds cool. And there's a GitLab for that, which is where the merge requests were created. And in here, there's all of the specs, like to take an example, XDG specs. Inside of it, we get the system tree specs, the thumbnail specs, the trash or the MIME apps, which is, I think, like, when you open an application, know which app to open that, sorry, when you open a file, know which app to open that file of, kind of, I guess, that's how I see it, at least, notifications. And notification spec is actually one that was already edited, I think, if I remember correctly, by KD. Oh, yes. I mean, look at David Fauré. I'm pretty sure is another KD developer. I'm pretty, yeah, it's KDouble. So as I was saying, and there's lots of stuff here. And if I remember correctly, there should be some reply stuff, of course there isn't, but somewhere, something is with a reply to, actually, reply to notification. And that was initially implemented by Plasma, replying inside of the notification itself. And that was upstreamed, if I remember correctly, and hopefully I do, to be standard for other desktops to allow other desktops to also implement the feature to reply to notification without having them reimplement everything in their own property. Like, hopefully, I mean, something can always go wrong. But in theory, right now, it shouldn't be the X Plasma reply to all property, but rather the reply to all property. I'm just making an example. Of course, it's not called reply to all, but, and of course, not going to scroll with touch. But we can see that as an example, we have an entry, which is the notification icon, which contains, you know, the notification icons. And then there's another spec that talks about icons and image formats. Then there is the summary of the icon, the body of the icon, which is the one you see inside of it, the actions to actually, you know, click on. And then it goes on hints, expiration, timeout, backwards compatibility, blah, blah, blah. Oh, look at here, urgency level. So you can have like normal, low or critical urgency notification, that's cool. Okay, I was not going crazy. There was the notification add in line reply, which was a proposed change to the specifications made by Cabrolick, which is another KD developer. As you can see, KD developers are really interested in trying to make sure that standards are standards, even in other desktops. However, the merge quest was closed and there are 37 messages about this. So probably there was lots of discussion on how to do this and maybe something went wrong. I'm not going to go through 37 messages, but you get the idea. So you have a spec and a series of properties, the description of the properties. And whenever you implement something as a desktop, it is your duty really to go to the free desktop as an example specifications and make sure that they're updated to what they're doing. And if not, try to propose, at least try to propose what you're doing as a maybe better way to do things. And if you do that, other desktops can see that change of properties and try to implement their own. In this case, I think it's pretty cool that Nate Kerham himself changed, both changed the specification, but also did a patch to GNOME to actually implement that specification, which was quickly reviewed and merged. I think that's cool. So to summarize it up, you can see that a keylopper has made a patch to GNOME by making sure that it follows the free desktop specifications. And specs are important because if you, when they decide to create your own desktop, you don't have to rewrite like notification from scratch, but you can just use the specs that are there already. And I think that's pretty useful, isn't it? Now, in theory, this is the part where I outro the video and say thank you, subscribe and that kind of stuff. And usually I do have the animations, but as yesterday and as the day before yesterday, I still don't have them. And sorry about that. And I promise that this time they're coming. But look, I've been, it's been a busy week. It's been a busy week, to say the least. So don't worry to all the people who donated. I'm not showing you the names, but I really am happy. I just received a very nice donation that I'm super happy about. And this giving me the energy to go forward. So thank you to everyone and see you tomorrow as always in theory. Can I stop?