Stated reasons are safety and security. They are officially still in a health quarantine, but the leadership has expressed that the security situation has been better with no migrants, and so it continues. The opposition and neighbor states disagree.

A spicy near-land entry by air is sure to lead to an even spicier exit procedure when the visa is checked!

You could, except that Azerbaijan has kept their land borders closed for entry since covid. You can depart on land, and you can arrive or depart by air, but you cannot arrive by land.

This is why I switched from a multitool with pliers to a Swiss Army Knife and XS Knipex Cobra pliers. Overall smaller and lighter than most multitools, and higher quality materials.

Watched that episode a few months ago. I did a spit take when I heard it.

Liz Lemon’s ringtone

https://youtube.com/watch?v=6GT1797-rQQ

It’s true. Cameras have always been expensive, but even the thin economy of scale is gone with the competition from smartphones. That makes any new camera a premium product.

Same. Well, except the Patagonia part.

I didn’t find a camera that felt like the right mix of image quality, portability and affordability in the gap between our small travel camera kit (Sony a7c with 2 small primes) and a top end phone.

Better to spend the big money on a phone that will be in my pocket every day.

Btw: does anybody know what bad things actually happen if there is no metal cage that blocks all the radio?

Noise happens. Could be no problem, or it could hurt your wifi or mobile data connections, or maybe raise a neighbor’s ham radio noise floor. I saw this recently when setting up a pi to run BirdNet-Pi. The USB3 connection to an SSD caused enough noise in the 2.4GHz band that the onboard wifi radio could only connect on the 5GHz band.

To start - moving services from bare metal to rootless Podman containers running via quadlets. It’s something I have had in mind for a while but keep second guessing the distro choice. Long-ish release cadence, systemd-networkd and a recent Podman version in the native repos, well supported, and not Ubuntu.

So far openSUSE Leap seems like the winner. A testing machine is up to install everything, write some deployment scripts, and decide on a storage layout and partitioning scheme.

If anyone has another distro to recommend that checks these boxes let me know!

I like rolling release for the desktop, but only want critical patches in any given month for this server, and a major upgrade no more than every 3-4 years. Or an immutable server distro. But it doesn’t seem like networkd is an option for the ones I’ve looked at (Fedora CoreOS, openSUSE MicroOS), and I am not sure if I want to figure out Ignition/Combustion right now.

Next project - VLANs on Mikrotik.

OP - Navepoint makes good racks for reasonable money. I have a Pro series 9u from them and it went together without any problems. It’s on the wall with a pretty big ups in it.

Heck yeah! It should be great in borscht. I would reserve the liquid in the cabbage and use it to add acidity and salt to taste when the soup is done.

I’ll bet a mushroom and rice or barley cabbage roll would be great, if messy. We sometimes make unrolled lazy cabbage rolls. Chopped onion, celery and carrot, cooked in a little oil, add garlic and the chopped protein. Season with salt, pepper and caraway. Add the cabbage or kraut and a splash of beer or water, cover and let steam a bit. Stir and serve when the texture is as you like it. Chopped tomatoes are good on top as a fresh addition.

Whole head of cabbage, right? Probably intended to make cabbage rolls, aka holubky, golubtsi, sarma, etc.

You could also slice it to shreds and make choucroute garnie or any other sauerkraut dish.

My understanding of why is that it relates to their change to a scene-referred workflow. Up to v3, darktable used a display-referred workflow like other programs. In that model the image you start with is mapped on a tone curve from the start where 0 is pure black and 1 is pure white, and the midpoint is set to midway between. This is all from the standpoint of what your display can render. The scene-referred workflow in v4 doesn’t do that. All the tones are mapped in an unbounded and uncurved way. So images look flat, but you’ve retained maximum data, so you have more to work with. The developers assume that you want control and maximum fidelity. There’s a better explanation in the intro of the documentation. This impacts everything - especially the color balance.

One of the problems is that all of the display-referred tools remain as modules in the interface, and some are even used in the base processing, but you’re not supposed to use them. At least if you want to do things the ‘right’ way. We created a custom panel that has 90% of what we regularly use (shared UI with my partner). That plus creating some presets that work well with our cameras has made it very quick to get a satisfying output in a minute or less.

Honestly, if you want to do minor tweaks to a RAW and mostly want what the out of camera JPEG looks like, there are much easier tools. If you at least occasionally deal with really challenging photos, or you want to get creative in the processing of some of your RAW images, darktable opens up a lot of possibilities, while being free and open source. So I think it’s worth the effort to learn. Shooting with a colorchecker helped us get the presets we wanted for a variety of shooting conditions.

Same here. DigiKam and darktable.

Getting color balance with raw in darktable took quite a while for us. It was helped by using a Color Checker Passport in a few shooting conditions to use for reference and calibration. Once we got past that darktable has been great.

Is it just me or is the year on #3 suspect? The car to the left of the fire hydrant at lower right looks considerably later.

If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.

Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.

Run:

sudo systemctl edit systemd-networkd-wait-online.service

That adds the override.conf for the service. Add these lines:

[Service]
ExecStart=
ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any

The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.

If you want solid reliability, Debian is where you might want to start. Particularly on an older PC where the hardware should be well supported. Make a live install image USB boot drive and see if you like it before you decide.

Debian is all about stability, at the cost of having less recent software. For newer versions of the desktop environments you could try live boots of KDE Neon and Pop!_OS as well.

Interesting!

it wasn’t for dumb people who didn’t know any better

I mean, it kind of was though, wasn’t it?

Just because more knowledgeable people found it interesting and got it for the novelty or to see how it worked doesn’t mean it wasn’t a product intended for people who, Kodak hoped, wouldn’t know any better. That doesn’t mean I’m saying your father didn’t know better.

Hopefully he’s still around and you can ask him about the relative image quality between those formats. If he was interested in quality, he wasn’t going to grab the disc camera. It wasn’t like Betamax where it was superior but lost a battle in the marketplace. Disc film was objectively much worse than even 110 while being much more expensive to buy and process.

It’s not bad to get running, and the alerting is really flexible. You can add Nagios and syslog alerts easily too.