The confounding part is that when I do get offered an "AI result", it's basically identical to the excerpt in the top "traditional search" result. It wasted a fair amount more time and energy to repeat what the top of the search said anyway. I've never seen the AI overview ever be more useful than the top snippet.

I broadly agree with your assessment that most of these are not sexual assault, even if they are inappropriate.

Tara Reade ultimately did accuse him of forced unwanted digital penetration, which if it had happened, would be absolutely sexual assault. So far this is the only allegation of that nature, but she didn't go unambiguously public until 2020 (though there's record of a more contemporary mention of the incident in a call to Larry King live, but the call was vague both in terms of what happened and who it involved).

However, it is still one person's word versus another, and a singular incident. Also a lot of incidents where Tara was pretty much grifting through people, so she had a credibility problem. In the accusation itself she accuses him of going to zero to 100 faster than she could have said no, but stopping when she did say no. So ultimately by every measure and the most pessimistic interpretation of the allegations, it is still not as bad as Trump's incidents. She alleges that he "grabbed her by the pussy" which would be a grave incident for bidens history while Trump just casually says that is something to do any old time.

Define "the OS package manager". If the distro comes with flatpack and dnf equally, and both are invoked by the generic "get updates" tooling, then both could count as "the" update manager. They both check all apps for updates.

Odd to advocate for docker containers, they always have the app provider also on the hook for all dependencies because they always are inherently bundled. If a library has a critical bug fix, then your docker like containers will be stuck without the fix until the app provider gets around to fixing it, and app providers are highly unreliable on docker hub. Besides, update discipline among docker/podman users is generally atrocious, and given the relatively tedious nature of following updates with that ecosystem, I am not surprised. Even best case, docker style uses more disk space and more memory than any other option, apart from VM.

With respect to never having to worry about bundled dependencies with rpm/deb, third party packages bundle or statically link all the time. If they don't, then they sometimes overwrite the OS provided dependency with an incompatible one that breaks OS packages, if the dependency is obscure enough for them not to notice other usage.

Depends on if you stick to distro provided dependencies, then you are generally good, unless a third party repo decided to supersede that dependency.

I have spent a long time carefully packaging as a third party repository and it's generally doable. Just sometimes another repository isn't as careful and blows away the distribution provided libraries.

Washington Post had a better picture: https://www.washingtonpost.com/world/2024/07/04/zelda-master-sword-jail-nuneaton/

I'm guessing it's pretty much a letter opener. From a read, letter openers count, and many people are mocking the idea of a letter opener being included in such a ban.

You don't need the distro to package your sodtware through their package management systems though. Apt and dnf repositories are extensible, anyone can publish. If you go to copr or ppa you can have a little extra help too, without distro maintainers.

The headache comes up when multiple third party repositories start conflicting with each other when you add enough of them, despite they're best efforts. This scenario starts needing flatpack, which can, for example concurrently provide multiple distinct library versions installed that traditionally would conflict with each other. This doesn't mean application has to bundle the dependency, that dependency can still be external to the package and independently updated, it just means conflicts can be gracefully handled.

Flatpack can be centrally managed, it's just like a parallel distribution scheme, where apps have dependencies and are centrally updated. If a flatpack is made reasonably, then it gets library updates independent of the app developer doing it.

"App image" and " install from tarball" violate those principles, but not snap or flatpack.

Generally their playbook is open, it just doesn't work. Their strategy is to let rich people do whatever they want and hoard as much wealth as they can, and that prosperity obviously will trickle down to everyone.

However when taxes are relatively higher on the rich and regulations do things like punish them for poisoning a water source, they spend their resources gaslighting the populace into thinking economy is just terrible and if your personal experience does not bear that out, well your just lucky and you'll be out on the streets in a few months unless you vote right.

How about the way you walk?

I would suspect never.

Either they are obsessed with their "work" and do it far more than that, or they do nothing.

Musk still counts as someone who likes Musk. Perhaps more than anyone else. So it still works.