In this case it’s somewhat different.

We have seen almost these exact formations on earth, where they are created by microbiological lifeforms which could survive in the condition of how we expect ancient Mars was like when this sediment was formed.

We have been able to reproduce similar patterns in the lab, but only in conditions with much higher temperatures or with much higher acidity than what we’d expect Mars to have been like back then.

So the possible options are:

1. Ancient Mars was how we expect it to have been, and these patterns were formed by ancient microbiological, Martian lifeforms.

2. These patterns were formed by a known chemical process, and ancient Mars was much hotter or more acidic (or both) than we expected based on all other research.

3. These patterns were formed by a currently unknown chemical process that does not require the high temperature of acidity that the known processes require.

So in this case it’s not just wishful thinking. The hypothesis of this being formed by microbiological life is the hypothesis that best fits with what we currently know about the conditions in which the sediment was formed (which doesn’t fully prove that it’s true, but does give it credibility). And even if options 2 or 3 will end up being the right explanation, then we’ll still at least learn something interesting from this.

x86 has bit manipulation instructions for any bit. If you have a book stored in bit 5 it doesn’t need to do anything masking, it can just directly check the state of bit 5. If you do masking in a low-level programming language to access individual bits then the compiler optimization will almost always change them to the corresponding bit manipulation instructions.

So there’s not even a performance impact if you’re cycle limited. If you have to operate on a large number of bools then packing 8 of them in bytes can sometimes actually improve performance, as then you can more efficiently use the cache. Though unless you’re working with thousands of bools in a fast running loop you’re likely not going to really notice the difference.

But most bool implementations still end up wasting 7 out of 8 bits (or sometimes even 15 out of 16 or 31 out of 32 to align to the word size of the device) simply because that generally produces the most readable code. Programming languages are not only designed for computers, but also for humans to work on and maintain, and waisting bits in a bool happens to be more optimal for keeping code readable and maintainable.

FYI messing with communicating infrastructure, such as by jamming phone signals, is highly illegal and most networks are actively being monitored for disturbances.

A wooden toothpick is probably a bit too thick. You’d want something thin enough that it can be inserted without touching the electrical contacts. If you do have something plastic then that’s probably better, but if you do the cleaning when the device is off the USB port should be unpowered and there shouldn’t be a risk of causing a short, and modern USB ports are quite well protected again shorts anyway so it’s very unlikely to cause damage just by being conductive. You mainly want something that is long and thin enough to get all the way to the bottom of the port without having to apply any force. If the only things you have that are long and thin enough to reach the bottom of the port without having to be forced in are made of metal, then that’s still a safer option than jamming something too thick into the port that can deform the center contacts.

Grab a thin needle or piece of wire, thin enough to easily insert into the USB-C port, and scratch all of the dirt and lint out of it. Always point the needle towards the outer surface so you don’t scratch the electrical contacts in the middle.

There is often a surprising amount of junk inside even if you can’t see it from the outside, and that can greatly affect the connection quality.

My phone recently had a similar issue where it would only charge if the cable was inserted in a specific way, and any movement would cause it to stop charging. The cable also wasn’t really held well even though it looked like it was fully inserted. I cleaned out the port even though I couldn’t see anything inside, and managed to pull out a bit of dust anyway. And now my phone no longer has charging issues and holds on to the cable much better.

USB-C unfortunately just seems to have a design that makes it very easy for dust to get stuck in it, while also having a relatively low tolerance for foreign material buildup before the connection quality gets affected, making this a quite common issue.