Audacious and Audacity are different applications, despite their similar names. Audacious is a lightweight and versatile audio player designed for POSIX-compatible Unix-like operating systems, with limited support for Microsoft Windows, and it is known for its support of Winamp skins and a media library. It began as a fork of Beep Media Player, which itself is a fork of XMMS.
On the other hand, Audacity is an audio editor used for recording, editing, and producing audio files, supporting a wide range of audio formats and offering features like noise reduction and time-stretching.
While both are free and open-source software with similar licensing (GNU General Public License v3.0 or later), they serve distinct purposes: Audacious for playback and Audacity for audio editing.
The confusion between the two is common, but they are separate projects with different development histories and functionalities.

You can compile Audacious (and plugins) with meson and ninja

1. Setup the build system

arch-meson audacious build 

2. Compile

meson compile -C build

3. Install to debdir

meson install -C build --destdir "$(dirname $(pwd))"/debdir

The Last Cargo Cult Interviews
_https://www.youtube.com/watch?v=YB-26XqDZj8
_https://youtu.be/YB-26XqDZj8

Dec 3, 2009
In THE LAST CARGO CULT, groundbreaking monologist Mike Daisey (If You See Something Say Something) returns to The Public with the story of his journey to a remote South Pacific island whose people worship America and its cargo. This narrative is woven against a searing examination of the international financial crisis that gripped the globe at the same moment. Confronting the financial system that dominates our world, Daisey wrestles with the largest questions of what the collapse means, and what it can tell us about our deepest values. Part adventure story and part memoir, he explores each culture to unearth a human truth between the seemingly primitive and achingly modern.

Native cargo cultists could easily imagine cargo planes because they had witnessed the arrival of real military aircraft during World War II, which delivered supplies and goods seemingly from the sky.

Native cargo cultists typically obtain their knowledge of "the true secret of cargo" through dreams or visions, which are considered revelations from ancestral spirits or deities. These prophetic experiences are central to the formation of cargo cults, as a charismatic leader often claims to have received a vision or "myth-dream" that foretells the return of ancestors or a messianic figure who will bring abundant goods... The dream or vision legitimizes the leader's authority and serves as the foundation for the movement's rituals and expectations.

Add mate-sensors-applet to panel, and watch processor temperature
_https://help.ubuntu.com/community/SensorInstallHowto#sensors-applet

EDIT:
A manual for Ubuntu newbies is available here:
Building Firefox On Linux
_https://firefox-source-docs.mozilla.org/setup/linux_build.html

To fix problems, you can simply re-bootstrap

cd firefox        # cd sourcedir
./mach bootstrap

It will open a dialogue:

Please choose the version of Firefox you want to build (see note above):
  1. Firefox for Desktop Artifact Mode [default]
  2. Firefox for Desktop
  3. GeckoView/Firefox for Android Artifact Mode
  4. GeckoView/Firefox for Android
  5. SpiderMonkey JavaScript engine
Your choice: 2 

and you can choose 2. Firefox for Desktop

Create .mozconfig

➤ cat firefox/.mozconfig
# The default mozconfig is located here: sourcedir/browser/config/mozconfig
# It specifies the build flags for Firefox. 
# You can use it by adding:
#  . $topsrcdir/browser/config/mozconfig
# to the top of your own  sourcedir/.mozconfig file.

  . $topsrcdir/browser/config/mozconfig

# Restrict the number of parallel jobs to reduce the chance of build failure 
# For old computers -j2 of j3, for new ones -j10
mk_add_options MOZ_MAKE_FLAGS=-j4

mk_add_options MOZ_OBJDIR="$(dirname $topsrcdir)"/build_dir
mk_add_options MOZ_APP_DISPLAYNAME="Firefox Nightly"
mk_add_options MOZ_SIMPLE_PACKAGE_NAME=firefox-nightly

ac_add_options --with-app-basename="Firefox Nightly"
ac_add_options --with-app-name=firefox-nightly
ac_add_options --prefix=/usr
ac_add_options --enable-audio-backends=alsa

Then, you may try to build

cd firefox     # cd sourcedir
git pull           # update source code
export LDFLAGS+=" -Wl,--no-keep-memory"   # to reduce the chance of build failure during linking due to running out of memory
./mach build -v --priority normal

Test

./mach run 

It should open your Firefox Nightly. If it works, install it to a folder debdir

DESTDIR="$(dirname $(pwd))"/debdir ./mach install

and create a Debian package for it. A detailed step by step manual "how to create a Debian package of debdir" is here:
_https://dev1galaxy.org/viewtopic.php?id=7214

Firefox Nightly is quasi portable. You can make a Debian package for Firefox Nightly on Devuan and install it on Linux Mint (and other way round).

./mach run --version
 0:00.13 /home/rich/Programs/firefox/objdir-frontend/dist/bin/firefox --version -profile /home/rich/Programs/firefox/objdir-frontend/tmp/profile-default
[73542] Sandbox: CanCreateUserNamespace() unshare(CLONE_NEWPID): EPERM
Mozilla Firefox 146.0a1

To add a binary to the AppArmor allowlist, you need to create or modify an AppArmor profile for that binary, specifying the necessary permissions. This typically involves editing the profile file located in /etc/apparmor.d/ and adding the appropriate rules, then reloading the AppArmor profiles with sudo systemctl reload apparmor.

./mach run --version
 0:00.13 /home/rich/Programs/firefox/objdir-frontend/dist/bin/firefox --version -profile /home/rich/Programs/firefox/objdir-frontend/tmp/profile-default

EDIT: but maybe this apulse is needed for kernel so that alsa can play several streams at the same time=?

A talent for creating credible myths involves blending familiar elements with fantastical ones to explain real-world phenomena...
A credible myth connects a familiar, real-world fact with a magical or fantastical reason for its existence.

If you have a talent, use it to develop your potential and take action. Start by understanding your own strengths and then consistently practice and apply your talent in every way possible, even by using the underlying qualities of your talent in other areas of your life. Remember that action is what matters, so begin before you feel completely ready to achieve results.

_https://github.com/i-rinat/apulse
apulse: PulseAudio emulation for ALSA.

The program provides an alternative partial implementation of the PulseAudio API. It consists of a loader script and a number of shared libraries with the same names as from original PulseAudio, so applications could dynamically load them and think they are talking to PulseAudio. Internally, no separate sound mixing daemon is used. Instead, apulse relies on ALSA's dmix, dsnoop, and plug plugins to handle multiple sound sources and capture streams running at the same time. dmix plugin muxes multiple playback streams; dsnoop plugin allow multiple applications to capture from a single microphone; and plug plugin transparently converts audio between various sample formats, sample rates and channel numbers. For more than a decade now, ALSA comes with these plugins enabled and configured by default.

apulse wasn't designed to be a drop-in replacement of PulseAudio. It's pointless, since that will be just reimplementation of original PulseAudio, with the same client-daemon architecture, required by the complete feature set. Instead, only parts of the API that are crucial to specific applications are implemented. That's why there is a loader script, named apulse. It updates value of LD_LIBRARY_PATH environment variable to point also to the directory where apulse's libraries are installed, making them available to the application.

Name comes from names of both ALSA and PulseAudio. As aoss was a compatibility layer between OSS programs and ALSA, apulse was designed to be compatibility layer between PulseAudio applications and ALSA.

apulse relies on ALSA's dmix, dsnoop, and plug plugins to handle multiple sound sources and capture streams running at the same time.

think it is based on MATE but could be wrong

tried with RaspiOS latest /(based on Trixie) and it would lead to broken Desktop/Black Screen and just cursor moving

...modern versions of KDE, especially the underlying components, have a strong dependency on PipeWire for its audio server... While it may still be possible to run KDE with PulseAudio, newer versions of core components like KWin have made PipeWire (specifically the pipewire-session-manager, which is provided by wireplumber) a direct dependency