Starter idea: it could conceivably fit in the Sort Type dropdown - respects the other settings (Subscribed/Local/All, Posts/Comments) and just throw results through a RAND() (sic) function.

tl;dr - depends not only on the device but also carrier and region. Google specifically made changes to stop devs from doing it. Full explanation to read: https://www.pcmag.com/how-to/record-calls-on-your-android-phone

This is unfortunately a choice the Nautilus (GNOME) folks have taken; in other file managers (Thunar for XFCE, Caja for MATE, etc.) the ability to use custom actions are a first class citizen. Within Nautilus, the nautilus-actions project was superseded by the filemanager-actions project which was then archived: https://gitlab.gnome.org/Archive/filemanager-actions - a custom GNOME action might be something like gio open /path/to/terminal.desktop %d (where %d is the directory from Nautilus)

There are 3rd party attempts to recreate what was stripped out of/abandoned in Nautilus such as this one: https://github.com/bassmanitram/actions-for-nautilus

Went down the rabbit hole for you while drinking some tea listening to the rain - it looks like in the future there is a new app/proposal for FreeDesktop to use xdg-terminal-exec as the new/default way and it’s hard coded into the GNOME “gio” code over here (ctrl+f search xdg-terminal-exec): https://gitlab.gnome.org/GNOME/glib/-/blob/main/gio/gdesktopappinfo.c

That said, it looks like the nautilus-open-terminal Nautilus extension is shipped as part of gnome-terminal so it’s hard coded to run that terminal not using the above code. Instead, you’d need to leverage a different extension called nautilus-open-any-terminal for now until the landscape changes: https://github.com/Stunkymonkey/nautilus-open-any-terminal

(disclaimer: not using GNOME/Nautilus or Fedora, theorycraft from me)

I would agree, and would bring awareness of ionice into the conversation for the readers - it can help control I/O priority to your block devices in the case of write-heavy workloads, possibly compiler artifacts etc.

The Linux kernel uses the CPU default scheduler, CFS, a mode that tries to be fair to all processes at the same time - both foreground and background - for high throughput. Abstractly think “they never know what you intend to do” so it’s sort of middle of the road as a default - every CPU cycle of every process gets a fair tick of work unless they’ve been intentionally nice’d or whatnot. People who need realtime work (classic use is for audio engineers who need near-zero latency in their hardware inputs like a MIDI sequencer, but also embedded hardware uses realtime a lot) reconfigure their system(s) to that to that need; for desktop-priority users there are ways to alter the CFS scheduler to help maintain desktop responsiveness.

Have a look to Github projects such as this one to learn how and what to tweak - not that you need to necessarily use this but it’s a good point to start understanding how the mojo works and what you can do even on your own with a few sysctl tweaks to get a better desktop experience while your rust code is compiling in the background. https://github.com/igo95862/cfs-zen-tweaks (in this project you’re looking at the set-cfs-zen-tweaks.sh file and what it’s tweaking in /proc so you can get hints on where you research goals should lead - most of these can be set with a sysctl)

There’s a lot to learn about this so I hope this gets you started down the right path on searches for more information to get the exact solution/recipe which works for you.