I had several drives in my PC, so I wiped a small one and just installed a few different distros and figured out what I liked. I ended up sticking with nobara with KDE.
Sounds like a weekend that you could have saved if the software was just implemented properly and accepted spaces.
Something being an industry standard does not necessarily mean it’s good. Sometimes it just means it was the cheapest, or sometimes even just because it was used for so long. How long did it take for Torx to somewhat replace philips head screws despite being better in most cases?
I think date strings are made for human and machine readability. Similar to XML or JSON. So, why not improve systems so that we can have more human readable date strings? If you don’t care about human readability and want to make sure there is no confusion with spaces, you can just use epoch timestamps.
but what does the command line matter for dates? sure every once in a while you’ll have to pass a date as an argument on the command line but I think usually that kind of data is handled by APIs without human intervention, so once these are set up properly, I don’t see the problem
I imagine that to be pretty difficult with laptop keyboards like a scissor switch. But after googling a bit there seem to be a few tutorials so maybe it’s easier than I think.
I didn’t consider that an option because whenever I searched for setcap and flatpak, most threads were pretty dismissive and told OP that flatpak is made with security in mind so doing that isn’t supported.
Regardless, I tried it just now, but the password prompt (image below) still shows up when launching the autostart .desktop file I created. The .desktop file launches a script I wrote, which in turn actually starts GSR through flatpak, in case that changes anything.
Do I assume correctly that this prompt might be gone if I set the capabilities of /usr/bin/flatpak? It’s not something I want to do, so I’ll probably keep trying to get the manually built version installed.