"simple majority" is a technical term in this context, it refers to any number >50%. In the context of the Senate, that'd be a 51/49 split, or a 50/50 split broken by the VP.
There are some procedural measures that explicitly only require this simple majority to pass; most bills require a 60/40 in practice because that's the threshold required to bypass a procedural filibuster. They at the very least require a simple majority + 0 members of a body opting to invoke filibuster.
Say what you will about the people we've currently elected; I just stand by it being a sound procedural practice.
Yes they were, so I'm offering you an actual theory as to why this may actually be true, yet difficult to "prove".
Smoking was bad for your health long before anyone sat down and took the time to prove it. Autoregressive LLM tokenizer are a very new field of computer science and it's going to take a while for the community to collectively understand everything we're currently doing by trial and error.
I try to keep my commentary as apolitical as possible, so what I'll say is:
If you believe that the current ticket is the Cthulhu/Lucifer ticket, imagine what they could accomplish if every bill only required a simple majority.
Anecdotally, I use it a lot and I feel like my responses are better when I'm polite. I have a couple of theories as to why.
More tokens in the context window of your question, and a clear separator between ideas in a conversation make it easier for the inference tokenizer to recognize disparate ideas.
Higher quality datasets contain american boomer/millennial notions of "politeness" and when responses are structured in kind, they're more likely to contain tokens from those higher quality datasets.
I haven't mathematically proven any of this within the llama.cpp tokenizer, but I strongly suspect that I could at least prove a correlation between polite token input and dataset representation output tokens
There are a lot of moderates that are hesitant about AOC. She's expressed ideas like getting rid of the filibuster, which would be great while "your" party is in charge, but is one of the very few checks available for a minority party to halt truly controversial legislation. The extra steps are kind of dumb, but the foundational idea that legislation should at least require a 60/40 majority most of the time enforces an idea of compromise and representation in almost every bill.
I would shudder to think what a bad president could put through if unchecked by the opposition party in an essentially 50/50 politically divided populace.
I run clusters of both LSI-based hwraid and zfs at work. I strongly recommend zfs over hwraid. The long and short of it is hwraid hasn't kept up with software solutions, and software solutions are often both more performant and more resilient (at the cost of CPU/memory).
For homelab scale, zfs is definitely the way to go, especially for archive data.
Me too brother, but I disagree with your assessment on value
An non-blacklisted residential IP address with reasonable throughput is valuable in and of itself. DDOS botnets, proxies to bypass geo blocks or to obfuscate illicit traffic, etc. Also your gaming PC could be used for distributed compute workloads of compromised, usually crypto mining.
Any hardware/connection has value if it's "free". It's just a numbers game beyond that.
For now, ctt winutil does a pretty good job at removing the cruft. I've long since switched to debian for my daily driver, but as a remote-access sunshine host for games that require kernel level anticheat, it's surprisingly usable.
Every packet you send/receive relies on passive security. Your nic drivers, the driver kernel model, all of the userland applications that sit on top of it. I get that in practical terms, your firewall will do a lot of the heavy lifting but there are passive rce vulnerabilities in previous unsupported versions of Windows that are trivially exploitable today.
Even if you trust their intent to not misuse your data, there are now a lot of live rpc hooks into your operating system, controllable by anyone who can compromise their azure implementation, which has happened at least twice in recent memory. If the data never leaves your device, and they didn't have a way in, they wouldn't have those things to lose in the first place.
The interdependency itself, regardless of intent, is inherently more dangerous than the previous separate paradigm that used to exist.
Your dad probably got lucky, and your router's firewall probably did a lot of the heavy lifting. If you were to connect a win 2000/XP computer to the internet today without a firewall between, it would be compromised in minutes (there are loads of videos of people demoing this).
While I don't have proof that 7 would be the same, I strongly suspect it would be the same. 10 will get there soon too. Firewalls will stop most of the low hanging fruit, but an application that bridges connections through the firewall are that much more vulnerable to exploitations that won't be integrated by your running kernel.
They won't brick it, but you can bet that a lot of people are sitting on unreleased 0-days for win10. It will likely be dangerous to connect to the internet on day 1.
I would be genuinely surprised if fair use draws the line on format-shifted, legally purchased media, at "remote watch-together", leaving format-shifting and local watch-together in-tact.
If it were up to the studio's interpretation of the law, you'd need to purchase a license for each person during local watch-together.
RE: backups, I'd recommend altering your workflow. Instead of taking an image of a box, automate the creation of that box. Create a bash script that takes a base OS, and installs everything you use fresh. Then have it apply configuration files where appropriate, and lastly figure out which applications really need backup blobs to work properly (thunderbird, for example). Once you have that, your backups become just the data itself. Photos, documents, etc. Everything else is effectively ephemeral because it can be reproduced through automation.
Takes a lot less space, is a lot more portable. And much better in scenarios where something in your OS is broken or you get a new computer and want to replicate your setup.
I'd say that the ctt winutil does a pretty good job. I've been running installs cleaned by it for a good year now without major issues