As a side issue I will add that when I first started researching this I had, in /etc/rc?.d/, links for S03opensmtpd & S04network-manager, which is why openstmpd was starting before network manager despite openstmpd being dependent on network manager.  I disabled and enabled network manager and then had S04network-manager & S14opensmtpd - which is the expected order.  cron & rsync also changed from S03 to S14.

I think this points to a problem somewhere with the way the init links are maintained.  Perhaps there should be a process that resets their order anytime a script is added/changed/deleted during an upgrade (while preserving the state of manually disabled services).

Even better: rsync -aHX

The "X" will preserve extended attributes and capabilities - kinda important for OS files.

Perhaps another factor is that systemd started as an init system and was rather innocuous.  Later it started taking over so much other functionality - DNS, NTP, booting, etc, kinda like the proverbial camel getting its nose in the tent.

Do you at least have cron installed?  Do you have /etc/cron.daily/logrotate?

I've been using privoxy and its IJB ancestor for close to 25 years yet I don't know if I can be of much help.  I've never gotten real deep in its capabilities and much/all of the HTML-rewriting features are of little use now that most traffic is going over HTTPS.  I can tell you that I've never modified default.action - only user.action.

I haven't tried it but I suspect you would put something like this in user.action:

{+standard.Cautious}
.dev1galaxy.org
.devuan.org

to apply that set of rules to this domain & sub-domains, and the devuan domain & sub-domains as well.  Note that once an action is switched on in the config, it is active for all entries below it until switched off (with {-standard.Cautious} in this case).

My usage is just to limit access to only specific domains.  I block all access via HTTP and HTTPS and then unblock HTTPS to specified domains:

{+block}
.*:80
.*:443

{-block}
.dev1galaxy.org:443
.devuan.org:443

That returns "home=/root;config=;cache=;"

Good idea.  During two boots the messages preceeding creation of /.cache were coming from smartd, but I don't know why it would need a cache file.  I deleted /.cache and restarted that service, and several others (chrony, opensmtpd, dovecot, rsyslog, cron, dbus), without a new /.cache being created.  I'll keep digging.  Or maybe not.  It's not hurting anything, it's just annoying now that I know about it.

Something to consider is that the more of your system that is encrypted, the less there is that can be tampered with.  Encrypting only the home dir leaves you vulnerable to keyloggers etc being installed in the system.

The tracker service can be disabled and masked.  Whether it gets surreptitiously enabled again is a question. Changing the directory where it stores its data to read-only might also hinder it.

But the whole point of the search engine is to rank the results in some way, isn't it?

Of course, there are some wingnuts that actually want their sites omitted from search engines so they have something to scream about.
https://www.techdirt.com/2022/10/07/ari … e-indexed/

...and call it Wine++ or Wine#

@hunter0one: The option has been here for a long time.