If they could read, they’d be very upset.

Inside git’s internal plumbing folder, git holds a file with the branch name and all of the references (files and changes) for that branch.

When you make a new branch git will update its internal plumbing checking to see if the new branch already exists, updates its references to the new branch if it doesn’t (all held internally in a case sensitive way). It will then make that new branch file, git has already checked that the case senitive name for the branch doesn’t exist internally, so it should be good to go.

Part of its process is creating that internal branch file… But wait!

Windows doesn’t have case sensitive naming so when it tries to make that new branch file it will overwrite the old one (since it shouldn’t exist by git’s own reference!) All of the files and references for it now get nuked.

Now you’re at best back to wherever that originally named branch came from, at worse your .git folder is properly borked.

Way ahead of you… I have a Brocade ICX6650 waiting to be racked up once I’m not limited to just the single 15A circuit my rack runs off of currently 😅

Hopefully 40G interconnect between it and the main switch everything using now will be enough for the storage nodes and the storage network/VLAN.

Home Petabyte Project here I come (in like 3-5 years 😅)

Confirmation of anecdotes or gut feelings is still science. At some point you need data rather than experience to help people and organizations change their perception (see: most big tech companies lighting billions of dollars on fire on generative AI).

Or… They do what they did last time the lifetime was cut down from 3-10 years down to 395 days… Just issue you a new certificate when the old one runs out and up to whatever the time period you bought it for…?

Let’s Encrypt isn’t the only CA to use ACME, you can auto renew with basically any CA that implemented it (spoiler: most of them have)

I’ve been using this to automatically skip ads on my Chromecasts (youtube ads and in video segments) for the past year.

https://github.com/gabe565/CastSponsorSkip

It’s literally sponsor block but for all of my Chromecasts

Why would it be risky? I’m genuinely curious if you have any resources (other than Apple’s, because they’re obviously biased) that show that a third party battery is dangerous.

As far as I know, as long as the battery meets the dimensions, nominal volatage, chemistry/max charge rate/communication to the charging circuitry, discharge rate, it will function safely.

A battery is a battery is a battery. There’s no concievable reason I can think of that would require you use an Apple branded battery. If you have evidence to the contrary I’d love to see it. Knowing proper battery safety is important if you mess with them in any capacity (which I do), so something I may not be aware of is important to know.

They said that it does not represent their values

IANAL; However Usually the contracts have a severability clause, meaning even if some parts of that contract are null and void the rest of it stands minus the parts that are illegal. Does that mean those clauses are also null and void depending on locality? Again IANAL, but I believe it’s pretty settled contract law at least in the US.