All I could find is how to make a list, and reinstall flatpaks from that list, as well as backup app data, however all of that assumes I want to do updates.
Meanwhile what I want is akin to extracting APK of a stable version of some app, backing it up and using it for years to come. For example that’s how I joined these 2 screenshots, using JointPics from 2014 which isn’t even on Play Store anymore, and targets API so low that it has to be installed via ADB. (Yeah, I am too dumb for GIMP)
As for the regression, you can see. On left is older Flatpak, on right is version from Arch repo. The Flatpak I originally installed as a hotfix for update that broke it completely at one point on Arch.
You can see the older version nicely fits the screen, splitting up text into columns.
Meanwhile the new version just does smaller page in middle of screen that doesn’t even work properly with Breeze Dark theme, causing different background for text sections.
The only improvement is ability to flip pages rather than use arrows, but that’s minimum.
Well, and maybe the progress keeping got fixed, but I didn’t test that much.
Don’t pay attention to the taskbar. I wish it could flip to vertical with different screen orientation. Yeah, the icons’ clickability is a dice roll of what you tap.
Look, I get it. But I’m also burned out.
Krita’s devs specifically? No. I respect devs by default. I don’t doubt many of Krita’s devs love what they develop. I also use Krita. I don’t have it installed because I don’t need it.
The problem that I keep running into is my (Plasma) defaults being changed for (some) reason. Krita usually gets the defsult for photos. Rhythmbox for audio and MPV for video. I prefer using Pix for photos and VLC for AV.
Plasma, kind of - does.
99% of people do not want a photo editor to be their defsult app for opeing photos. Some artists? Sure. But me? No.
Again, it’s nor a Krita thing specifically - Plasma fucks with my defaults. It’s a Plasma/KDE thing. Krita is just the unfortunate app to have become Plasma’s senseless-default victm.
Oh, Krita fits my workflow quite well. Personally am in the process of switxhing to it from GIMP. I know I wrote up a huge wall of mostly garbled text in a passionate rage, but reading just the first part of my rant should’ve made that clear.
Of course you didn’t. Because who in their right mind enters “0” as the target resolution? That’s right - on one! Except for me, apparently. It’s a stupid bug. One which doesn’t mean anything. It opens no attack surface. It doesn’t cause random crashes. It doesn’t interfere with anyone’s work.
However, you clearly haven’t read my essay. Which is fine with me. It isn’t quality reading material by any sensible metric. But, were you to have read it and tried to recreate the bug, you probably would’ve succeeded.
With that out of the way, my main point was how no - devs (especially KDE, and very transparently so) don’t value your feedback as much as one might think.
Which is - understandable.
As you said, many keep FOSS software alive in their free time for nothing other than the moral gratification. Which is much more than merely commendable. And please, do not try to tell me I don’t respect that when I do.
Where would devs be if they only replied to stupid questions from new users? That’s right - in a tech support hub!
Which is obviously a waste of their time. The fact they don’t do that isn’t anything negative.
The problem, as always is - documentation. My little beef with KDE’s crash wizard is but one example of this deeply-rooted problem.
As is seen in our (both mine and your) example, reading is hard. Writing - harder still. Were I able to read and fully comprehend the ill-fated link on the KDE wizard’s “fuck you” page, you probably wouldn’t be rading this. But alas, I am a human whose reading comprehension skills aren’t top-notch.
Another, equally deeply rooted problem in FOSS is lack of general design thinking and logic. Am I calling KDE devs stupid? Of course not! But any UI (including the KDE crash wizard) should have a few eyes to assess it first. Then research on a batch of test users should be done. And then feedback from the general user population should be listened to. Is that a hard ask? Yes. Step 2 is expensive and as such out of reach of most FOSS projects, and not even Big Tech bothers with step 3.
But am I wrong in calling the KDE modal annoying and badly designed (“stupid”) even, when it has already wasted my time in the same way on 15 occasions? Maybe not. I am angry and it may have been irrational. But I feel my perspective is at least understandable even if the wording isn’t.
In the end, users can’t live without developers and developing user-facing applications makes little sense without users. I’m not in the Linux community because I don’t like FOSS, Linux or KDE. I’m percisely here to support them. However, sometimes issues arrise, and having a good community to help with fixing issues (because the devs can’t (obviously) handle all that load themselves) is good.
Having a community where the answer to a simple, begginer question is basically “bother the devs, they have a Matrix”, “it’s probably your fault” isn’t an answer. It’s a fuck you. And once they find out they’ve been mislead (not even intentionally perhaps), they might go back to Big tech.
Saying to me that I don’t support FOSS, that I don’t like it and that I can go back to Big Tech (when I haven’t been there for over 4 years now), is an even bigger one.
I like FOSS. Saying I don’t respect them wben I truly do is an insult. I merely don’t understand some of their decisions. Probably due to a lack of context and knowledge, which is on me.
But does giving a rant about, what are tiny problems in the running of a huge machine known as My Computer, spurred on by someone’s unhelpful advice, given in hopes of starting a discussion and the wholly implausible odds of the issue at hand given as an example being fixed due to it call flr the reply “Go to Big Tech, there’s clearly no room for you here”?
I’d hope not.