Keep notes.

No recipe will work identically in all kitchens with all the various equipment types. Temperatures will vary. Timing will be different.

If you are just starting out, ty cooking something that you really enjoy, which is more of a one-pan/pot dish. Something that should take less than an hour. Make notes on how it tasted, how the protein felt to the touch (hard, firm, bouncy, soft, etc.), timing differences, texture while eating (dry, wet, soft, hard, etc.), things you would do differently next time. If you are confused about how things went, ask for help and suggestions. Take notes on those. And then cook the same thing again soon after. It will probably be better. Repeat until you feel confident.

Celebrate the win!

Next make something different but with the same main ingredient. Repeat that until it’s to your liking.

Once you repeat this a few times with different dishes you will find that you build up some intuition about the ingredients. Then it’s easier to branch out to other recipes and other foods.

Lots of people talk about meal prep for a week. Don’t get sucked into doing that until you are confident with a specific recipe and how it keeps leftover. You will build skill if you cook one meal at a time. Limit the time needed and ingredient cost so that a bad outcome doesn’t feel so bad.

If I was in your shoes I would probably figure that out first. It could be related to why the snapshot restore failed.

On openSUSE with the default partitioning and Snapper you rollback this way:

1. Boot to the snapshot from the grub menu.
2. Test to make sure it’s working.
3. Run sudo snapper rollback and reboot.

It may differ for Arch depending on how you have it set up. If you don’t have grub entries for the snapshots, you could install and configure grub-btrfs. It’s easy, but there could be gotchas depending on how you are set up currently. Maybe give this a read and see if it’s helpful: https://www.lorenzobettini.it/2023/03/snapper-and-grub-btrfs-in-arch-linux/

(Not my blog, it just looked useful)

If you have trouble with the soaking, black beans do very well with a “quick soak”.

1. Cover them with water about twice the depth of the beans. Add about 1 teaspoon (~5 ml or 5-7 g) salt.

2. Bring to a boil and keep it boiling for 2 minutes. Then cover and turn off the burner/hob. Let soak for 1-2 hours.

3. Add any extra seasonings now (but nothing acidic). Then bring back to a boil and then simmer until soft. Adjust seasoning and you’re done.

They should take much less time than cooking from dry. How long will depend on the beans. Older beans can take much longer, but most should be soft in 1 hour or so.

It’s bread, too. Try a bacon sandwich sometime. Delicious!

Very nice. Haven’t seen that before.

Could also be a stale DNS cache entry on one device or the router. If you ping your duckdns fqdn from the device that can’t connect while on your home network, does it resolve to the correct public IP?

I still think a firewall/nat issue is more likely tho.

What is your router make and model? You need to enable hairpin NAT.

Not when you change residency, but if you relinquish your citizenship: https://en.wikipedia.org/wiki/Expatriation_tax#United_States or your residency has been revoked.

So if you remain a US citizen you owe normal annual tax (minus a credit for foreign taxes paid).

The port is forwarded from your router to the pi, right? If so, you could test for the router as the bottleneck using the router’s WAN side IP address as the target.

This should give you a good data point for comparison. If it’s also slow then you can focus on the router performance. Some are slow when doing hairpin NAT.

Definitely!

It’s significantly immediate-er with induction - particularly going from cool to hot. Boil water in 2 minutes and handles don’t get hot in the process. And since nothing is heating except the metal of the base of the pan there is no residual heat from the cooktop parts or the sides of the pan when you turn it off. The temperature drops much faster.

I went back to gas after 5 years cooking on induction and miss it a lot. Cooking something like pasta that requires boiling a sizeable quantity of water takes 2x or 3x longer on gas, even with a very powerful burner.

Does this media server need to be accessible when you are away from home? Will you store personal data on it?

Out of band management: this is a server feature that lets you access and manage the server even if the OS is down. That’s important if you may be away from home and need to fix a boot problem.

You can simulate some of this with PiKVM (remote console access) and PDU solutions (remote power control).

Redundant power: servers often have redundant power supplies, so that if one fails it can still function.

You can simulate this, with short downtime, by having a replacement ready. Mini PCs make this easy by using relatively inexpensive laptop style external power bricks. But also think about the power circuit - is the server on the same breaker/fuse with something that could potentially take the circuit down while you are away?

ECC RAM: this is about data integrity. If there is a failure in non-ECC then a bit flip could cause data corruption.

You can’t really get this without ECC. Using a file system that has anti-corruption features can help reduce some of the risk. You probably trust your data to consumer PC hardware, so this would be no different really. It’s about risk mitigation.

And that’s the main thing here, deciding on the use cases and prioritizing/budgeting how you mitigate risks to each.

I’d say your chances are very good. Even their high end rackmount models work with the usbhid-ups driver. Don’t think they would change things up in this regard since they would also need to change their software.

Same, on both accounts!

Apron is a fun one. The Latin word for cloth, banner, tablecloth is mappa. It’s the same word used in “mappa mundi” meaning map of the world (we contract that to just map now). French often changed Latin m to n, so mappa became nappe, then nape.

English borrowed nape directly for cloth and added it’s native diminutive suffix -kin to refer to a small cloth, a napkin.

But there was also a similar diminutive in French - naperon. A cloth to keep your front clean. English borrowed that too, as napron. Then, sometime around the 15th century, “a napron” got mistaken for “an apron” since they sound identical. And that’s what we have today. (Source etymonline and others)

Powder detergent is the way. When I open up the dishwasher at the end of the cycle and find clean dishes and no residual foam at the bottom of the machine I know that I used just the right dose.

High Sierra and Dark Passage are both great. So is The Big Sleep. Anything with Bacall really.

To Have and Have Not is a good watch since it’s when the first worked together. But I would probably wait a while after seeing Casablanca for the first time since it suffers by comparison.

No, you’re holding it wrong!

That would be painful for GNU (GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for GNU’s Not Unix, where the first part stands for…