I’m just this guy, you know?

  • 6 Posts
  • 158 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • As someone on semaglutide therapy, I can share that a large calorie deficit hits you in the wills to live. At some point even just eating feels like a stop at the gas station to fuel up, and it hardly matters whether it’s 87 or 95 octane. Hell, rancid fry oil would even work. At some point, you stop caring whether you eat because it feels like another chore.

    Eventually your metabolism syncs up again with your energy demand and you start getting interested in food, except you’re way more selective about how you’re (edit: spending) acquiring those calories. I almost can’t abide by junk food, fast food, or breaded fried crap anymore. But neither do I want salad or vegetables because they’re “fluffy.” Too much volume, not enough calories. I want about 6 or 10 forks full of food, and then that’s it. And it’d best taste good, or I can’t be bothered. Restaurants easily stop looking like a good deal.

    Anyway that’s a digest of my diary for the last 22 months. Do with the info as you will.







  • 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
    



  • SolidGrue@lemmy.worldtoLinux@lemmy.mlLaptop for Linux use
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 month ago

    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.








  • 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.