https://news.ycombinator.com/item?id=39369886 outlines the (non) PR history. Expand the whole HN post to get links of (unrelated) people who cloned the LGPL v4 tree/tag/branch before they (PySimpleSoft) scrubbed/deleted the entire Github repo of pre-v5 content the past few days.
tl;dr - "bad blood". The SMT developer (one guy, "Tools") sold it to ZipoApps who immediately injected ads into the Play Store versions of all the tools and invented a name "Simple Mobile Tool" (note no "s") which angered a lot of people. There were blogs and news articles and discussions, you just missed them which happens - it's a period of transition in a difficult time.
Having participated lightly in the Github conversations, the community members who forked it took a lot of care to choose a new name (held several polls, etc.) and carefully constructed their presence in a positive manner without throwing any shade at the original developer or adware company who he sold it all to - they chose to take the noble route and just present their work without any vitriol or nastiness. They released Gallery first awhile ago, these are new updates and more apps being added - I saw changelog notes where they're removing license-encumbered libraries and stuff like that which somehow flew under the radar on F-Droid.
You're comparing apples to oranges as they say, Disroot is a volunteer group/organization who runs a suite of services (one of which is Nextcloud) which is intended toward a specific type of audience as a group of like-minded individuals; it is run by a named set of admins and is much closer to a foundation in an organizational sense which accepts donations to keep things running. Murena is a for-profit entity selling you Nextcloud-as-a-service without the underlying belief system which fosters Disroot.
The wiki functionality built into Gitea (which is functionally a clone of Github's design, being honest) works great and can keep your documentation notes about (a thing) next to the code/scripts/configs/etc. you're storing in a git repo right next to it (I assume you're using git somehow). The wiki content itself is just Markdown, and it's managed either (a) as a normal remote git repo, or (b) using the Gitea GUI editor as a WYSIWYG editor + git client. Test it out here on their live dev instance: https://try.gitea.io/
Give credit where credit is due, this is Manny the cat and they're super famous, so famous that you can't get away with social media karma farming their pictures without people knowing: https://www.instagram.com/yoremahm/
Perhaps this might help - as pipe is a replacement for pulse and sort of alsa it could be you're missing one of the various shims to make things cohesive. Here's what my Arch system has for those three:
$ pacman -Q | grep -E "(pipe|pulse|alsa)" | cut -f1 -d' '
alsa-card-profiles
alsa-firmware
alsa-lib
alsa-plugins
alsa-topology-conf
alsa-ucm-conf
alsa-utils
gst-plugin-pipewire
libpipeline
libpipewire
libpulse
pipewire
pipewire-alsa
pipewire-audio
pipewire-pulse
pipewire-v4l2
Outside of the classic "type a password" or "have the keys locally", Network Bound Disk Encryption (NBDE) is what the business world uses for this (but it's not cheap and/or simple to self host). On one side you have commercial vendors who will sell you a solution, such as Vormetric, and on the other side you have the open source world trying to leverage open code.
Red Hat has a good article to read as an NBDE primer as it outlines the concepts as well as implementing their solution/method using open software: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html/security_and_compliance/network-bound-disk-encryption-nbde
Making a guess (possible clue path for you to go down), the alsa-utils package deploys a udev ruleset and some systemd services to save and restore state. It sort of sounds like your system is not detecting audio state on boot or some other shenanigan which an uninstall/reinstall of the package fixes by tricking the system into re-running udev and/or a service related. Start maybe with looking at what these are doing in relation to your configuration:
usr/lib/systemd/system/alsa-restore.service
usr/lib/systemd/system/alsa-state.service
usr/lib/udev/rules.d/90-alsa-restore.rules
In theory there's data in /var/lib/alsa/ (usually an "asound.state" file, etc.) so it might be worth poking around there a bit as well to see what pops out of the woodwork.
Android suggestion: https://github.com/T8RIN/ImageToolbox (may or may not be good enough for your needs, give it a shot)
I use the below uBlock filters for old.reddit annoyance cleanup, whatchya got for new.reddit?
reddit.com##.native-ad-container
reddit.com##.premium-banner
reddit.com###chat
reddit.com###chat-count
reddit.com##.redesignbetabar-js
reddit.com###redesign-beta-optin-btn
The owner/programmer is a regular on HN and shows up in most all threads, as well as keeping an open blog of how he's built it, maintains it, and all the code challenges he has to work on to improve it. https://news.ycombinator.com/user?id=marginalia_nu
Crota, because he can destroy the Well
Have your Well player be tractor; boop once for sword guys, sword guys -> Crota kneels, Well jump in air and plant well on his head or back. Counts as a body shot and he can't break the well now.
Yah to both you and @KinNectar@kbin.run that example just caught my eye as "in the spirit of the asked question, looks cool" but I don't have any actual knowledge about Plume (or any of the blogging options).
This seems like maybe a resource you're looking for as it has many, many choices in this space: https://codeberg.org/fediverse/delightful-fediverse-apps
I don't blog, but this one catches my eye as an interesting platform (in that you don't have to self host it but you can if desired): https://fediverse.blog/ (Plume is the engine, https://github.com/Plume-org/Plume)
I do a ton of wiki work though, and one thing is cemented in my brain: data portability is a must-have. Choose a solution which has data which can be exported/imported in some standardized format - mediaWiki may be great software, but the pain of converting it's deep markup language into something else (say, Markdown) is just painful. My workplace switched wiki software must be 3, 4 times over the years and just migrating data from one to the other (say, mediaWiki to Confluence) is just... pain and suffering.
Your checkmark experience is RCS, not pure (classic, legacy) SMS. https://www.makeuseof.com/what-do-the-checkmarks-mean-in-google-messages/