solidgrue

It's not DiGiorono, it's Dispensary!
-- stolen from Charlie Berens

Man, I got stuff to do. Lol.

I mean....

Steam? Maybe? I dunno, I don't game but the Steam kids seem to prefer Arch. I'm sure they have their reasons.

Practically? Probably nothing terribly significant.

Termux (on F-droid) is a userland environment that runs on top of your Android device's kernel. It has Debian/Ubuntu-like package management system that pulls from repos maintained by the termux team. If the package is available for aarch64, its probably available in the termux repos. Its not so much of an app as it is an alternate userland that runs on top of the same kernel, but can interact with Android a couple of different ways.

The main Termux app gets you a basic command line environment with the usual tools included in a headless Linux install. From there you can select your preferred repos, do package updates, installs, etc, just like on a desktop or laptop. You could even install a desktop environment and use RDP to access it.

Then there are some companion apps that are useful:

• Termux:boot is like a primitive rc.d feature that executes upon boot up any scripts found in the termux ~/.termux/boot directory. You could use the feature to launch an SSH server, or perhaps start your syncthing service when the phone starts up.
• Termux:Tasker is a Tasker plugin that allows Tasker to launch scripts in .termux/tasker based on whatever triggers or profiles you define in Tasker. For example, stop or start selected services when connected to your home WiFi
• Termux:API is a set of termux utilities to interact with the Android API, and do things like send messages, interact with the camera or battery, and manipulate system settings.

So you could install the syncthing package in Termux and (after setting up Termux access for your internal storage) configure it to sync folders from your phone to wherever syncthing syncs. You'd set up a start script under Termux:boot to launch it when your phone starts, or Tasker to start/stop the service on your home WiFi.

For the F-droid enabled users, it seems there's a Syncthing app in the Termux repos:

~ $ apt show syncthing
Package: syncthing
Version: 1.28.0
Maintainer: @termux
Installed-Size: 26.4 MB
Homepage: https://syncthing.net/
Download-Size: 7857 kB
APT-Sources: https://packages.termux.dev/apt/termux-main stable/main aarch64 Packages
Description: Decentralized file synchronization

I think that's the Gen2 or Gen3? I had a couple of them over a few years, and I'm ashamed to say I'm not sure whether I actually had the one in the photo, or the version just prior to it.

Plus 1 for a refurb or gently used Dell Latitude series. My daily beater for the last 5 or 6 years has been a pre-2020 Dell Latitude 7390 13". Works really well with the *bian distros I've run on it, decent battery life, OK mic and speakers.

I've had to replace the battery once, and the keyboard once (which I damaged myself by applying a small amount of Coca Cola).

Refurb ThinkPads are also great, but they have a high resale value.

I am really not sure how I feel about this. It feels like when Cisco Systems bought Kalpana back in '94 and brought us the Catalyst 3000. So sexy, much disaster. Very bugs.

I really wanted to like that switch. It got better, but so did I.

Where was I?

Oh right: Qualcomm buying Intel. That's not gonna help anything or anyone. Bad idea.

No worries, the other poster was just wasn't being helpful. And/or doesn't understand statistics & databases, but I don't care to speculate on that or to waste more of my time on them.

The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you'd get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.

If you want an all-time count, you'll have to track it off box because FTL doesn't provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.

Hey, this was fun. See you around.

#### MAXLOGAGE=24.0
Up to how many hours of queries should be imported from the database and logs? Values greater than the hard-coded maximum of 24h need a locally compiled `FTL` with a changed compile-time value.

I assume this is the setting you are suggesting can extend the query count period. It still will only give you the last N hours' worth of queries, which is not what OP asked. I gather OP wants to see the cumulative total of blocked queries over all time, and I doubt the FTL database tracks the data in a usable way to arrive at that number.

Ah, well if you know differently then please do share with the rest of us? I think the phrasing in my post makes it pretty clear I was open to being corrected.