And because they're basically lawnmower engines, the fumes are actually significantly worse than car exhausts.

There's nothing inherently EV-specific about that gripe.
You'll be pleased to know that even some modern ICE cars now have gigantic electronic displays on the dash these days. I only expect more of that in the future.

Which means that when you do launch the app, your mobile OS has revoked all its permissions and the servers have canceled your auth tokens.
Thus you need to set it up and sign into it all over again, which is where the failure points lie.

The whole way you'd handle this "at home" would be to plug the car in overnight.
But unfortunately, the hotel you're planning to stay at during the trip is highly unlikely to actually have any usable charging infrastructure whatsoever.

Sure, some hotels do have chargers. But never enough to actually be able to depend upon.

That kinda reminds me of how the tech press used to report smartphone marketshare statistics. You could scope your data any which way to basically tell any story you want. Just get creative in what time periods you're looking at, and how you define the market.

Especially since the Win11 requirements are all about TPM 2.0, and have nothing to do with whether the machine is actually powerful enough to run the OS otherwise.
There are likely countless machines that are plenty powerful for everyday use, but have CPUs that pre-date the cutoff.

Meanwhile, I still don't think I've upgraded to Wi-Fi 6 yet... I think my current APs go up to 802.11ac, whatever consumer-oriented name that corresponds to. Still seems to work fine, but I guess I should upgrade one of these years.

And this is very difficult for one reason, that's seemingly lost on so many experts...

There are a lot of people in this country who think science is (or should be) like religion, and your public position is not allowed to change based on the circumstances and/or evidence. The moment you do change your position, you've permanently lost ALL credibility among these people.

So by first trying to discourage mask use, then later trying to encourage mask use, they came across as flip-floppers who are full of it to a huge portion of the country. They permanently self-sabotaged their messaging on the entire subject by doing this.

I'm still amazed at how many people I see wearing a surgical mask under the nose, or a useless cloth mask, or a useless cloth mash under the chin... TODAY.

Today, when few people are still wearing masks, if you do still want to wear one then there is absolutely no reason to do it wrong. The only reason to wear a mask today is to protect yourself and/or others, not to meet some sort of poorly-enforced vague masking requirement. So why, among the few people still wearing masks, do I still see so many people doing it wrong?

Depends on what you define as the underlying problem.
If the underlying problem is that women are grossly underrepresented in the industry as a whole, then job fairs for women absolutely won't fix the issue. You'd need to attack it at the middle school level, and you wouldn't see any effects for a decade.

But if the underlying problem is that big notable tech companies, who show up at major job fairs and who publish widely-distributed gender/diversity statistics, are severely lacking in their numbers of women tech employees... Then providing a job fair where they can directly recruit from a large number of viable candidates will absolutely help their own numbers.

So will this directly get more women in technical fields overall? Not really. But will it get more women in technical fields at the companies everyone pays attention to? Most likely.

As someone who used to work for the sort of company who would be on the other side of the table at this event, I think everyone is looking at this from the wrong angle.

There are very few women in tech to begin with, and yet the court of public opinion is constantly trying to beat up big tech companies over this. As if they can somehow snap their fingers and suddenly hire a much larger percentage than they already do. I think they would if they could, but its kinda a pipeline problem.

As such, I don't think events like this are really about making it easier for women to get ahead in line and find jobs in tech.

Rather, its about giving these companies, who are desperate to increase the numbers of women in tech on their payrolls, an environment where they can actively and directly recruit from the small pool of qualified women that are out there.

When you're deploying E2EE at scale, how you handle and recover from the myriad of error conditions almost becomes more important than the success path. There are so many things that can break E2EE in the wild, and if you don't pay enough attention to those (or handle them in a user-unfriendly way) its only a matter of time before a lot of ordinary people in countries you've never visited suddenly start to complain that the product is completely broken.

AFAIK, the OMEMO spec doesn't talk much about this at all. The only mentions of this in the spec appear to range from "don't handle it gracefully" to "its a TODO for this other spec we haven't published or accepted yet."

Imagine an iterative development process going something like this:
- Start with XMPP as a baseline
- Develop an efficient binary encoding, because sending large chunks of XML between low-end smartphones was stupid circa 2010
- Redesign the login/setup process because you paid dearly for every round-trip packet back in those days
- Continue to add features all on your own, for a decade, not looking to someone else's protocol implementation as a guide

At this point, it probably only resembles XMPP if you're looking at a debug dump of the protocol messages as only a WhatsApp-side app developer would even be able to. Even if XMPP now has many common features, the implementations have diverged so far that there's likely nothing in common anymore.

Also, when you're running a system with millions to billions of users, you tend to find and solve issues in ways that might not actually match how someone chatting with their 10 friends would have done it.

I've been gradually switching a few things over to Namecheap in the past year, but my motivation has nothing to do with their prices. Its more that they're one of the few registrars that's mostly trying to just be a registrar and doesn't constantly shove ads for their value-add services in my face to the point that I want to vomit.

I'd gladly pay more for a service that just stays in their lane and sticks to what I actually want to pay them for.

But even when its caused by debris, the actual leak may still be slow enough that a pressure sensor can catch it in time to drive to a tire place at one's convenience and get it taken care of properly.