@ryan
"app is ready" notifications are due to the window manager's focus-stealing prevention system. I do find it useful when clicking multiple links one after another so that Firefox doesn't raise/interrupt everytime.
If you have apps that trigger this in #GNOME when emitting notifications, then they're likely using the APIs incorrectly; see https://github.com/electron/electron/issues/18445#issuecomment-1963256166 for a technical explanation. AFAIK Electron still does it wrong to this day?
@wwarner
Believing the shop managers blaming delivery truck drivers, the supermarket's customers order chips delivered by a "Large Lorry Model" 
Meanwhile, a group of anarcho-syndicalist farmers are building entire farmers' markets to replace the established supermarkets' management by Very Small Shell Scripts™ just to prove a point, filling immutable shelves with flat-packed goods and a JIT fast-moving inventory.
#GNOMEOS #KDELinux #Linux #distros #Flatpak #automation #FreeDesktop
The social experience of upstream #FLOSS desktop software maintainers:
You're a potato farmer calling out the shop managers who keep moldy potato bags on shelves years past the expiry date, with your farm's brand prominently on the potato bag, and you get yelled at by the janitor for sternly asking the supermarket's management to comply with food safety regulations.
Wait… I just ruined #FreeDesktop devs' fantasy of becoming farmers, did I? 🤔
And with the bst caching setup it is more beneficial to do those together for maximum efficiency.
You need the setup for the #freedesktop sdk anyway.
Ahmed made a COSMIC image, tulip's had Zirconium with niri.
The nice thing about this is the #freedesktop sdk neutral. It's just the desktop base image to choose.
Then instead of "why are you inventing a distro" it's like who cares, your user experience is in your config. You get all the benefits of having a distro but you share the maintenance upstream. Every "Joe's own distro" would be part of the testing pool.
Think of the diversity of setups!
What we need is a "Sovereign #Linux Tool" that bundles forgejo/buildstream and the entire tooling for building a #freedesktop sdk OS.
100% local and can always push to a public registry.
I'm thinking the university use case where it's handy to have the built in bug tracker and stuff, but leave the heavy lifting to the fsdk.
Now I know you may have me on mute, @BrodieOnLinux ...
But let me repeat again: #Snap packages rely on a centralized repository. Let me repeat:
#Cannonical is trying to do a #VendorLockin situation with snaps, whereby they become the gatekeeper to your software.
Juxtapose that with #flatpak, which is designed from the get go to be repo agnostic. Sure, you need the #FreeDesktop runtimes for most flatpak repos, but it isn't actually a hard dependency.
Another episode of playing with #Freedesktop XDG portals in Emacs. I tried the Dynamic Launcher portal, which lets apps to add .desktop files (like #GNOME Web PWAs). Here’s an example in #Flatpak Emacs.
Launchers can even be set as URL handler, useful since Emacs Flatpak ships only one desktop entry.
--name sets WMClass and must match StartupWMClass to get the correct dock icon. Emacs can’t create frames with different WMClass, so multiple icons require separate Emacs instances.
Days since last "The #Linux kernel let an app* allocate infinite RAM, OoM'ed and locked up into a I/O death grind for no good reason whatsoever" incident:
0️⃣
How many more decades will we endure this BS on the #FreeDesktop?
*: the app in this case: #LibreOffice Calc, which encountered an autocompletion infinite loop when double-clicking the corner of a cell. And since LibreOffice's autosave is a roulette game, I lost at least 30 to 60 minutes of work even with its automatic document recovery.
Bodo Hinueber
Jeff Fortin T. (風の庭園のNekohayo)
Jorge Castro
Thor A. Hopland
Antonio Romano