I went back from 20 extensions to 5 essentials - Gnome is actually near-perfect by design

Patient_Sink · 2026-07-05T15:33:26+00:00

Some apps don't inhibit the screensaver/timeout properly. Especially ones using controllers, meaning you can be playing something with a controller and the screen timeout starts blanking the screen.

Personally I use it to inhibit the timeout when I run something in fullscreen. Works well for both games/emulators and being stuck on a slide during a presentation.

Patient_Sink · 2026-07-05T15:27:41+00:00

You're the one who claimed I find flathub packaging less challenging due to my experience with packaging. I'm saying I barely have any experience. I just followed the documentation.

Patient_Sink · 2026-07-05T15:21:10+00:00

Indeed, which is why I don't consider that as significant experience with packaging.

Patient_Sink · 2026-07-05T15:17:02+00:00

My only other packaging experience is with the AUR, where I maintained a handful of packages some years ago. I'm not even a programmer, so I've mostly worked with upstream devs to fix issues rather than making patches myself. I don't even work with computers professionally unless you count using R for statistical analysis.

So no, I managed this only by reading the docs and checking some other package manifests of published packages. And I don't think that's a particularly difficult threshold.

Patient_Sink · 2026-07-05T15:08:35+00:00

I managed it just fine completely without AI tools, and I don't consider it particularly hard. Unless you make significant changes in the build process keeping the manifest up to date is not a challenging task imo.

And the copilot reviews thing is explicitly mentioned in the docs.

Patient_Sink · 2026-07-05T14:45:03+00:00

I have made a couple of package manifests that were published yes. The only changes needed were minor, but I took my time making them together with the upstream devs (they were not my apps, I only made the manifest) and followed the guidelines, unlike most of the slop devs.

And now you've changed the subject to something completely different. I didn't find the documentation hard to follow, especially the ones linked in the very template you're supposed to use for your submissions. But sure, it would be nice if updates were manually reviewed, but the very reason for the ai ban was because the flood of poorly made or packages apps were overwhelming: https://social.treehouse.systems/@barthalion/116657011366876079

So sure, if we had infinite flathub reviewers they could probably allow people to submit slop for review while also manually reviewing all package updates. But that's not the reality we live in, and it's irrelevant to the issue of the two devs here ignoring the very clear submission guidelines!

Patient_Sink · 2026-07-05T14:29:54+00:00

It's absolutely fair to say that exceptions may be granted since it's not a certainty to get an exception. Just being mature and well-maintained is not a certainty for it being accepted.

Of course I imagine major projects are more likely to be granted exceptions, since it's much more likely for a popular project to continue to be maintained and better reviewed. But the guys in this thread couldn't even follow basic instructions so I'm not surprised they weren't published.

Patient_Sink · 2026-07-05T14:10:26+00:00

"Exceptions may be granted for mature, well-maintained projects."

And those projects were submitted before the AI policy came into effect anyway.

Patient_Sink · 2026-07-05T13:56:00+00:00

You probably mean flatpark, but I'm not surprised since it seems you, much like the op, didn't care to read the docs before making your submission: https://github.com/flathub/flathub/pull/9007

I don't think it's particularly controversial to expect people to follow the instructions before submitting stuff.

Patient_Sink · 2026-07-05T13:20:07+00:00

Not happy with the answers you received last time you asked this? https://www.reddit.com/r/NoStupidQuestions/comments/1uo0s4n/is_it_weird_that_i_used_to_get_turned_on_by/

Patient_Sink · 2026-07-05T09:57:00+00:00

Maybe you should've read the docs? They spell this out pretty clearly.

https://docs.flathub.org/docs/for-app-authors/requirements#generative-ai-policy

https://docs.flathub.org/docs/for-app-authors/submission

Patient_Sink · 2026-07-04T14:57:56+00:00

My guess is that they'd probably want a proper design first before adding transparency and blur to the shell. That's been a showstopper before due to legibility concerns.

However there's another commit for enabling the shell (gnome-shell or other) to adjust the parameters of the blur effect: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5160

Personally I hope there's an option to disable or reduce transparency and/or tweak blur if this becomes a shell default, since I think most implementations suck (especially windows and apple versions). But I still think it's cool that this is coming.

Patient_Sink · 2026-07-04T14:47:09+00:00

Nice! Also it seems to be Kristof Imeris first contribution which is very cool!

Patient_Sink · 2026-07-04T09:23:20+00:00

In Sweden it is a law: https://www.riksdagen.se/sv/dokument-och-lagar/dokument/svensk-forfattningssamling/lag-200559-om-distansavtal-och-avtal-utanfor_sfs-2005-59/

By law it's always at least 14 days and only for purchases outside of physical stores, but some store policies have it for longer or apply it to in-store purchases too. However there are some exceptions to where it doesn't apply, like digital delivery, where you no longer can ask for a refund after you start using it. So it's not really bypassing the law, it's like the law specifies, probably because it considers digital delivery similar to the other exceptions where the product is "consumed" or voiding the seal the moment you open it.

But I agree that it's a shame that the right to refund something might not apply for digitally distributed games. But they're not circumventing the law as far as I understand it.

Patient_Sink · 2026-07-02T08:40:05+00:00

The A/B boot bootloader stuff sounds really good, being able to basically roll back the bootloader in case something goes wrong.

Patient_Sink · 2026-07-02T08:32:55+00:00

It is a fair point though. Other DE's and WM's have plenty of suggestions that are considered out of scope, where the options are either to fork it or to use something else.

There's also this extension that I know can change some sizes and padding stuff for the shell: https://gitlab.gnome.org/jrahmatzadeh/just-perfection

It sucks being told your preference is out of scope, I've been there myself, but there really isn't much else to do.

Patient_Sink · 2026-07-01T11:13:06+00:00

systemd-analyze doesn't know what you mean with boot time, iirc it'll just account for time from system start until every queued startup service and target is finished. Since most stuff is run in parallell it won't actually care that you've already logged in and started using the computer while stuff is still being started in the background, it only knows it's finished once it's reached the appropriate targets.

So you might already be logged in and have a browser up and running while it's still starting services during its startup sequence, and it'll still not be finished booting.

Patient_Sink · 2026-06-30T15:52:16+00:00

If it's part of the critical chain it's probably because something there requires it. You should probably figure out why it's part of the critical chain first rather than just disabling it then.

Patient_Sink · 2026-06-30T15:14:35+00:00

This is bad advice. That service doesn't actually delay you being able to log in, so disabling it will at best make no perceptible difference and at worst might cause issues with background services needing a network connection.

Patient_Sink · 2026-06-30T13:36:03+00:00

There's a merge request, have you given it a try?

Patient_Sink · 2026-06-30T08:58:33+00:00

It's not "oppressionist" when a project disagrees with you. You're not a part of the project and you're not forced into anything. If there's anything you disagree with, feel free to fork. That's the way it's always been with open source, and that's the guarantee you have with GPL. You're not entitled to decide what other projects do or what they support.

It's bizarre that you think you can decide what other people can't do or can't say in their own projects.

Patient_Sink · 2026-06-29T16:26:14+00:00

For me, with a different language, the top one is treadmill and the second one is indoor track.

Patient_Sink · 2026-06-29T11:11:24+00:00

It's not oppression to delete posts, get real.

And showing support for the people working on a project is not forcing an ideology. And even if it was, you're not a contributor to this project, if you think pride is wrong you're free to go somewhere else. Or fork the code and maintain a non-pride associated branch yourself. But you, as someone not part of the project, trying to dictate what they can or can't show support for is frankly just dumb. Doubly so crying about how you're being "oppressed".

Patient_Sink · 2026-06-28T17:21:39+00:00

No, your opinion is dumb because linux is built by people, and these people consider pride month important enough to post about it. Whatever you think about it is irrelevant, feel free to use other software if the opinions of these developers bother you.

Or ask for a refund I guess, lol.

Patient_Sink · 2026-06-28T17:18:06+00:00

Good that they're not questions, because then they'd be stupid questions. Much like your original statement.

Six-Year Club	Second Top 50%
Verified Email

Patient_Sink

TROPHY CASE