In general, candidates who are on the end of a rescinded offer do not have much in terms of legal recourse. Although it varies from state to state, unless otherwise specified, employment is “at-will”, meaning either the employer or the employee can terminate the employment relationship at any time and for any reason. Consequently, candidates have a difficult time enforcing a job offer or recovering damages for a rescinded offer when there is no duty on the part of the employer to keep the individual employed.

That said, there are some circumstances in which a candidate may have legal recourse if an employer rescinds a job offer. The candidate may be able to pursue a claim against the employer under one of the following theories: 1) Promissory estoppel, 2) Fraudulent misrepresentation, 3) Breach of contract, and 4) Discrimination.

https://career.mst.edu/resources/students/job-offers-and-rejections/

Promissory estoppel cases are generally a case of the juice not being worth the squeeze, but based on the information in the OP (i.e. hefty demonstrable sunk costs) this particular circumstance is likely to be an exception.

One of my cats, despite being an extreme clinger, absolutely will not tolerate being picked up under any circumstance.

Lone exception? If there’s a bug she wants but can’t reach, she will meow until I come lift her up to catch it. One hand under her hind legs, one under her stomach - so she has both front paws free to pin the bug with. Fortunately, she’ll let me summon her too, so whenever there’s a moth or something hanging out on the ceiling, I yell “bug” and the cat comes running to catch it for me.

Right ol’ on-demand vacuum cleaner, that one.

FWIW, minimizing synthetic fabrics is great in the big picture since it’s a major source of particles that can wind up in the water and food supply, but wearing them has minimal-to-zero impact on personal health.

There is a massive functional difference to anyone with two braincells to rub together.

The core devs can (and should) step in front of a bus (or tank) tomorrow; the core project will just fork, and LW and the other non-triad instances will do fine without them. I’ve had no issue on Lemmy blocking .ml client-side.

The only reminder of the triad’s existence is infiltrator trolls who make alts on other instances to post bad-faith arguments glazing the core devs.

You misunderstood the pinned post; it’s soliciting donations for core Lemmy development, not for the .world instance.

The core devs use donations to the project to fund their tankie .ml instance, which is why they’re getting pushback. There is zero comparable pushback among the community towards funding .world or other instances.

If you’d like to give away any free toasters with hackable embedded microcontrollers to prove your point here, I’m a willing recipient and will attempt setup of a searx instance.

You didn’t start by asking a question. You needlessly trashed a helpful suggestion from a place of ignorance, then asked a naive question defensively to mask a lack of knowledge.

That is rude and trollish behavior.

Since it seems like you don’t know much about bash at all, I promise the book will help you.

You can be someone who actually knows what they’re talking about instead of making embarrassing, snarky comments that expose your lack of education on the topic at hand.

Bash has had some nice minor features and syntax sugar added, but the fundamentals are entirely the same. All the examples in the book work just the same today as they did when it was written.

What was added in 4.X or 5.x that you can’t live without? What do you think has changed that merits inclusion?

It’s a 36 y/o language, mate. I still reference my copy all the time, and found it to be a great definitive resource when I was learning.

How many bash 4/5 features are you seriously using on a regular basis? What do you think is out-of-date?

I highly recommend O’Reilly’s Learning the Bash Shell in paperback form: https://www.oreilly.com/library/view/learning-the-bash/0596009658/.

The other responses you’ve received so far don’t offer much insight into the historical background and underlying mechanics of the shell, which are crucial to understanding the "Why?"s of command-line quirkiness.