You can also just do the initial import on a NAS. It might take a day perhaps but, honestly, does that matter?

I’d suspect the bots would just try again with a masked user agent when they receive a 403.

I think the best strategy would be to feed the bots shit that looks like real content.

The originals remain untouched.

It is possible to override existing commands with aliases though. This is useful for setting flags by default. I have alias ls='ls --color' for instance such that whenever I run ls, it actually runs ls --color, providing colourful output.

Note that aliases are only a concept within your command line shell though. Any other program running ls internally won’t have the flag added and wouldn’t be able to use any of the other aliases either (not that it would know about them).

It’s very easy to program your own “proper” commands though on Linux. If you had some procedure where you execute multiple commands in some order with some arguments that may depend on the outputs of previous commands, you could write all that as a shell script, give it some custom name, put it in your $PATH and run it like any other command.

You could make aliases that are easier to remember for you.

If you e.g. had trouble remembering that mv does a rename, you could alias rename=mv. Ideally just put whatever you would have googled in “linux command to x” as the alias.

That’s the power of Linux; you can tweak everything to your preferences and needs.

There’s nothing further I can tell you. You’ll need to figure out which parts those sensors correspond to to draw any sort of conclusion.

I’d recommend you try the out-of-tree driver I linked. You can just rmmod the normal one and insmod the custom one at runtime.

First of all you need to figure out which sensor this even is. On my nct6687, there’s a sensor on the PCIe slot that is constantly >90° and that appears to be totally normal.

Could you post the output of sensors?

Here is how it looks like on my machine:

nct6687-isa-0a20
Adapter: ISA adapter
+12V:           12.26 V  (min = +12.14 V, max = +12.46 V)
+5V:             5.06 V  (min =  +5.00 V, max =  +5.08 V)
+3.3V:           0.00 V  (min =  +0.00 V, max =  +3.40 V)
CPU Soc:         1.02 V  (min =  +1.02 V, max =  +1.04 V)
CPU Vcore:       1.27 V  (min =  +0.91 V, max =  +1.40 V)
CPU 1P8:         0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU VDDP:        0.00 V  (min =  +0.00 V, max =  +0.00 V)
DRAM:            1.11 V  (min =  +1.10 V, max =  +1.11 V)
Chipset:       202.00 mV (min =  +0.18 V, max =  +0.36 V)
CPU SA:          1.08 V  (min =  +0.61 V, max =  +1.14 V)
Voltage #2:      1.55 V  (min =  +1.53 V, max =  +1.57 V)
AVCC3:           3.39 V  (min =  +3.32 V, max =  +3.40 V)
AVSB:            0.00 V  (min =  +0.00 V, max =  +3.40 V)
VBat:            0.00 V  (min =  +0.00 V, max =  +2.04 V)
CPU Fan:        730 RPM  (min =  718 RPM, max = 1488 RPM)
Pump Fan:         0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #1:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #2:  490 RPM  (min =  421 RPM, max =  913 RPM)
System Fan #3:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #4:  472 RPM  (min =  458 RPM, max =  939 RPM)
System Fan #5:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #6:    0 RPM  (min =    0 RPM, max =    0 RPM)
CPU:            +37.0°C  (low  = +30.0°C, high = +90.0°C)
System:         +25.0°C  (low  = +22.0°C, high = +48.0°C)
VRM MOS:        +22.0°C  (low  = +20.5°C, high = +66.0°C)
PCH:            +21.5°C  (low  = +18.5°C, high = +49.0°C)
CPU Socket:     +21.0°C  (low  = +19.0°C, high = +56.5°C)
PCIe x1:        +92.0°C  (low  = +76.5°C, high = +97.0°C)
M2_1:            +0.0°C  (low  =  +0.0°C, high =  +0.0°C)

Note that I use the https://github.com/Fred78290/nct6687d/ kernel module though. The upstream one doesn’t label many temps.

I wouldn’t go ARM unless you really like tinkering with stuff.

I bought a used Celeron J4105-based system years ago for <100€ and it’s doing just fine. The N100 is its successor that should be better in every way.

Don’t be afraid to buy cheap used hardware. Especially things like RAM or cases that don’t really ever break in normal usage.

Two 4TB HDDs for 120€ each is a rip-off. That’s twice what you pay per GB in high capacity drives. Even in the lower capacity segment you can do much better such as 6TB for 100€.

If you have proper (tested!) backups and don’t have any specific uptime requirements, you don’t need RAID. I’d recommend getting one 16TB-20TB drive then. That would only cost you as much as those two overpriced 4TB drives.

I generally prefer to not get shit in my mouth at all but you do you.

It’s entirely useless. Even more advanced views such as BetterBatteryStats or analysing a bug report only give minimally useful information.

The best you can do is disable shit you don’t need and measure what impact that has on power draw (usually measured in %/h).

with regard/respect to

Whoever told you text is expensive to draw has no idea what they’re talking about.

No terminal emulator ever should affect the performance of the rest of your system.

I mean that totally w.r.t. how it feels to interact with the terminal emulator.

A screencast cannot really capture that. Practically any terminal is fast enough to render a shitton of text quickly and “smoothly”.

The difference in speed can only really be felt.

W.r.t. UI, it looks exactly like you’d expect a GTK4/adwaita terminal emulator to look.

Unless you frequently build this from source, you don’t need to care about the pandoc build-time dep.

IME it feels much snappier than foot.

I mean, it’s a terminal emulator; what’s it supposed to show, a bunch of white text on black background?

The problem with xterm is that everything else about it sucks. The only other half-decent performer is mlterm which is decent but has its share of issues.

This one feels quite snappy; better than foot.

Chill, it’s just pandoc.

This is not an Android feature. This is a Google feature and I believe it relies on a round-trip through their servers too.

after a week of runtime it told me 2.5kwh average. could be average per hour

If it gives you kWh as a measure for power, you should toss it because it’s obviously made by someone who had no idea what they were doing.

At the federal level, yes. There’s lots of things going wrong in the “greatest” country on earth. That doesn’t mean you should stick the head in the sand and ignore advocating for incremental improvements. If no sensible transport advocate actually does anything for it because they think there isn’t enough public support, you’ll never achieve that goal, no matter how many advocates there actually are.

Not just bikes recently released a video which touches on this topic with some more differentiated discussion:

https://nebula.tv/videos/notjustbikes-these-two-cities-used-to-be-the-same
https://youtu.be/4uqbsueNvag