I especially like how this could reduce the need for irrigation in dryer climates.

Especially if you have Fail2Ban set up.

> if you have Fail2Ban set up.

Worth noting that if you are running a remotely recent version of SSH it has everything you need built-in. No need for Fail2Ban on SSH these days if your config is fully modernised.

Could you maybe explain a bit more about how one sets up OpenSSH to block brute-force login attempts with only its built-in features?

> Could you maybe explain a bit more about how one sets up OpenSSH to block brute-force login attempts with only its built-in features?

There are various ways, but you will probably want to start by investigating a combination of the below tuned for your environment :

      - PerSourceMaxStartups
      - PerSourceNetBlockSize
      - PerSourcePenalties
      - Match Invalid-User + RefuseConnection

`PerSourcePenaltyExemptList` is also worth a mention if its the sort of thing you like, we don't use it at $work as whitelisting IP ranges is not really in-line with modern security best-practice (zero trust etc.).

Fail2Ban is kind of required unless one like running out of sockets and are unburden by high cpu and disk load.

There is regular bot traffic attacking SSH, but it's not "saturate your downlink" level of traffic. If you're getting attacked that heavily then you're being specifically targeted.

Huh? I run ssh (OpenSSH) on port 22 with root login enabled and no fail2ban on a single-core laptop cpu from fifteen years ago. The load average is 0.00 even with the small mail and web server that runs on it

What cpu and especially what disk load are you talking about? Also not running out of sockets, not sure if that's RAM-dependent (the box has 2GB)

Working as a sysadmin, and with disk encryption the constant log writes generated from ssh was enough to cause heavy load on severs. Long lasting connections from bots also forced us to increase the maximum number of sockets, as some scan waves was enough to hit the maximum and block other connections. Fail2ban has mitigated those issues to the point where neither has been an issue.

I believe this depends on your exposure level. If you have one, or maybe no, domain names pointed at your server, you are probably fine. If you have tens, or hundreds, of domains pointed at your server (i.e. you are a web site hoster), you will probably need something like fail2ban.

On another server with the same setup, there's various services and websites running, so load average is never zero there (due to scrapers) but ssh has yet to catch my eye in htop. Whenever I've looked, even the amount of cpu that a Windows VM uses constantly while idle is many times higher than what ssh uses

Back in 1989 that was a rare skill. Many of the engineers who had experience were working on government projects. I mean TCP barely had congestion control at that point, it was very early days.

Maybe that second engineer who's laptop they were laser focused on was the CI/CD?

Maybe not so well on roads, but streets are a good place for bikes. Especially E-Bikes that can keep up with city traffic.

The bit you are missing is the space efficiency. Cars take up the most space by a large margin and getting people into more dense forms of transit (anything else) frees up space to be more efficiently used. Space is the most precious commodity in a city as many people are competing for every square meter.

This is also why suburbs and rural areas are a better fit for cars. Space is much more available and you can afford to be wasteful with it.

It's absolutely impossible everywhere except where it has been tried and works great. Car centric design is a poor match for dense urban development and reverting the city to be more transit and pedestrian focused almost always improves the situation, bringing more people to shops and restaurants and revitalizing previously moribund downtown districts.

Had a Chevy that was extremely obnoxious about this. If it was playing over USB it absolutely would not allow it to stop. Hitting pause on the phone would have the car immediately hit play to restart it.

Eh, if you only have a clock on only the microwave or oven then you lose access to the current time when you're cooking something or convert it over to timer mode. Having some redundancy isn't a bad thing in this instance.

Or simply have a dedicated clock in there and turn off the display on all of the appliances.

There should be two kinds of devices in my home: those allowed to connect to the Internet and keep their time up to date, and those that are not allowed to care what time it is. My microwave and my oven are in the latter category.

What are the odds they did have a centralized system for setting the clocks, but nobody knew how to operate it or cared enough to find out? Maybe someone set a password and then lost it. And of course if you have a centralized system it means you can't manually fix the individual clocks.