Oof, my bad, posted the message without completing it. I was gonna say that PayPal is a bad payment method cause it doesn’t take into account the intricacies of local payment methods despite being used as an sort of international method to transfer money (The play store is a fantastic payment method for instance, almost makes me wish for Google to take on PayPal). Credit Cards are also bad cause you need an international one and it isn’t always easy to get it.

It’s more of a frustration thing rather than guilty, mostly because it is possible, but not convenient. KDE isn’t the only thing I’d like to donate to, but it also uses PayPal

Yes, except none of those are the most convenient payment method for online purchases in my country, even credit card requires an international one IIRC, furthermore, it is a pain to figure out a proper amount cause it uses Euro. The minimum € 3,00 isn’t a huge amount converted to my local currency, but it isn’t a small amount either.

So you end up with something that is too much of a hasle even if you had the cash and wanted to donate. Cause you can’t stop thinking along the lines of “even if I wanted to deal with all of this the amount I’m giving isn’t going to change that much”

1. I’m broke

2. PayPal is horrible and inconvenient

I think the best solution is to have a… Link? To the general setting.

Having duplicated settings across multiple settings page is something that I think is an issue. Cause it isn’t obvious to the user if the setting is actually shared between the two pages or if it has two different options with the same name. It also doubles cognitive load to the user, as if they have a Touchpad and Mouse they need to remember both pages have the same setting.

A link is more of a way for the designers to tell the user “Hey, we know what you are trying to find, but it is in another place”

I’m not even sure why Lemmy allows markdown, tags and…links(? I swear I’ve seen one like that) on a post title. We usually click the title to open the post, so it sorta of mess with that.

I mean, disabling the close button is probably on the top 10 ways to give a PC user a panic attack. And there was a time when games had an exit button on fullscreen.

Also, what the hell, if Undertale can jumpscare the player while still using Windows titlebar on display then SSDs are not an issue.

…yes, I agree with that, and that is why SSDs are superior. They allow the app developer to do whatever they want inside the app, while also making sure the window frame is consistent with the rest of the system.

It’s like a gallery wall in a home, you can mix photos and paintings with varying styles, and they would still look like they fit together if you use the same frame style on them.

…you sure the pictures aren’t an argument against CSD? The wallpaper on those pics looks the same, so I’m assuming they are on the same system, but they are inconsistent with one another. Meanwhile Blender and Gimp on my system look right at home.

…ain’t that supposed to be part of the window manager tho?

…where? No seriously, I don’t see any picture, there’s only the link to DWD. I don’t use Nextcloud, but both Blender and Gimp use SSD on my system.

And I’m quite confused by the idea of CSD looking like SSD. I know it can, however, I don’t see how that isn’t an argument for continuing to use SSD. What is the benefit of changing from SSD to CSD if the end result is to look like SSD, but have all the issues that come from using CSD?

…how do you hope to have a discussion about a design feature without discussing the visuals? The entire CSD vs SSD debate is one of UX/UI Design

You still haven’t provided an example of CSD without a Header bar. I’m familiar with the DWD proposal, the technology used might be different, but the end result is still a Header Bar in all but name.

I’m genuinely curious: What exactly do you have in mind with CSDs without the use of a Header Bar?

CSD and Header Bars are practically synonymous, and I don’t think I’ve seen, or even heard, about CSDs without the context of a header bar

It doesn’t work for CSD cause you either have a very strict guideline to prevent inconsistency, limiting the number and location of buttons. At which point it is so limiting that Developers need add another bar to hold whatever they can’t put on the header bar, rendering the CSD implementation moot.

Or you do like GTK and allow inconsistency. You can’t win with CSD.

And that is not even mentioning if CSD is even a good idea in the first place. Some users deliberately went with Plasma due to the lack of CSD in the first place, those would migrate to LXQT or XFCE.

Design follows technology and vice-versa. Once you allow devs to use CSD they can and will use that space to put buttons on it, and that inevitably leads to inconsistency between apps, because they will never share the same amount of buttons or be divided by the same amount of panels.

CSD is a Pandora’s box that is best left unopened.

Not really following what you mean.

The moment you allow CSD, apps can and will put whatever they want on there, leading to wildly inconsistency in the number of things there.

CSD will always looks weird cause it takes too much vertical space. It will never look as good as a normal Title Bar, which can be controlled by the server.

You also lose draggable space, as now buttons are taking space.

We are talking about CSD, are we not?

There are quite a number of DEs using CSD, and a couple of them even feature a more “traditional” layout with a button panel and left side app menu.

While some folks like it, at this point one of the defining features of Plasma is the fact that it stands out by not using Server Side Decorations, or GTK for that matter.

Besides, CSD is ugly

Why would you want to ruin Plasma?