• 1 Post
  • 23 Comments
Joined 2 months ago
cake
Cake day: July 16th, 2025

help-circle




  • Seems like something you may need to change in Transmission’s configuration, somewhere. Because it’s Transmission that is redirecting you and what you want is for that redirect to include the uri prefix.

    Otherwise, I see two options:

    • use a regex location block and match against all expected patterns
    • use a dedicated subdomain (i.e: server block) for this (each) service you want to proxy and just proxy all traffic to that domain with a root location block.

    The latter is what I would do.








  • It’s complementary to robots.txt.

    • It’s weird that it’s XML, in 2025.
    • It’s weird that it doesn’t use the .well-known/ prefix which has trended in the last decade for placement of files like this.
    • It’s weird that it canonically uses the generic “license.xml” file name instead of “license.rsl” or “rsl.xml” or something that more clearly indicates its semantics.

    But I do like the idea of having some widely adopted conventional way of expressing, in unambiguous terms, which usages are expressly prohibited, and that AI training is among them.







  • In years past, I’ve used Elasticsearch and Kibana. The learning curve is steep and the system resource requirements warrant a dedicated machine, but once you get it dialed, it’s really effective as a centralized logging server.

    Prometheus and Grafana are for time-series data (metrics), not logs. If you’re already getting that from netdata, don’t bother with these, as they’d be redundant with what you have.

    syslog is about as idiomatic as it gets for log management in linux, but i don’t have enough experience using it effectively to give any pointers there. If you don’t really know what you want, yet, and just want to collect logs from all the things and see them in one place so you can begin to try and make sense of them and make refinements from there, then syslog seems like an excellent place to start.


  • I’ve installed Debian Linux on over 50 devices by now. A vanilla configuration with GNOME works pretty much out of the box for me on a high-end desktop with a modern NVIDIA graphics card.

    I’d say the biggest part of the learning curve is figuring out which apps are good and suitable for what you’re trying to do. Just like with Windows and macOS and Android and iOS, there’s only a handful of viable options among an overwhelming sea of poor ones.

    There are many wrong ways to install NVIDIA on any given Linux distro and architecture, and only one functional way. As others here are saying, that’s on NVIDIA, not you or Linux.

    General advice: whenever possible, strongly prefer your distro’s standard package manager to install things over any other method. With Ubuntu, I believe that’s either apt or snap.

    Also: if you find yourself poking around in some obscure system internals while troubleshooting an issue, you probably took a wrong turn somewhere.


  • Occam’s Razor: coincidence is the most likely explanation. Most of us aren’t as unique as we think we are. It doesn’t take very long for a keen observer (or algorithm) to profile our behavior based on direct surveillance.

    Think of it this way: if you were the algorithm and were looking at a detailed account of every second of time you spent on the platform, and also had the same accounting for every other user… what inferences and connections might you, the algorithm, be able to make about you, the person?

    It’s a feature, not a bug, for platforms to recommend relevant content. It’s also intrinsic for you to engage with the platform authentically, engaging with it in a way that aligns with your interests, preferences, and demeanor. Relevant content drives engagement. Engagement drives revenue. Irrelevant content does the opposite and serves to benefit no one involved. The popular platforms blew up exactly because they are so good at knowing what you want to see even before you do.

    In short: no amount of tech can save us from ourselves.