…and this ensures it will happen again. with greater magnitude. the machine needs more meat.
…just this guy, you know.
…and this ensures it will happen again. with greater magnitude. the machine needs more meat.
I am so so so expecting a nuclear exchange in or around the middle east witin 12 months - possibly after a “dirty nuke” attempt somewhere.
I am clutching at straws to even excuse this out of my top 3 worst case black swans.
only positive news is that nuclear winter will sure fix up that global warming thing real good.
exactly what the us allows them to do. I can only guess that kind old uncle sam has been feeding its billions in war change to israel for reasons more compelling than mere genocide (but that would suffice for some). a middle east ground “incursion” may be it.
because nothing could possibly go wrong with this. nothing at all.
hmmm… surprisingly self-consistent. I guess stopped clock and all that.
this resonates so much…
“ok, which one of you crackheads decided an unconstrained recursive C function was a good idea right her… oh.”
this thread is it in a nut shell. the x11/wayland situation can trip things when it really should be super seamless. that will be fixed soon enough.
if you are ok with an Ubuntu base (which these days is drifting further from its Debian base) then regular mint is great.
if forced…
not hating on ubuntu, its just been moving away from where I am at.
If you’re skeptical that this feat is possible with a raw 4004, you’re right: The 4004 itself is far too limited to run Linux directly. Instead, Grinberg created a solution that is equally impressive: an emulator that runs on the 4004 and emulates a MIPS R3000 processor—the architecture used in the DECstation 2100 workstation that Linux was originally ported to. This emulator, along with minimal hardware emulation, allows a stripped-down Debian Linux to boot to a command prompt.
that is 2^8 levels of insane! and of course its Debian.
edit: 4bit data 12bit addressing make it an 8bit processor ; -)
I will slowly corrode on this hill.
just when you are sure this article is going to fluff out on you, it doesn’t.
But how does AI tell when someone is most likely lying? They’re smiling like an American.
I was oddly surprised at how I connected with this article. a useful read in a defining epoch.
branding is important, yo!
these days old onion articles are prophecy and new onion articles cant even give me a raised eyebrow.
this is/does both.
someone genuinely interested for intellectual reasons would likely not fall for it. I would imagine that a non-trivial percentage of “antiquity enjoyers” are very light on history substance and heavy on history feelz.
once the appropriate brain tickles have been pushed into their heads their “history substance” feed content becomes decidedly propagandized.
nice test. I mean, I can use this info tomorrow - hows that for real world impact? :-)
wish he had rated ease/damage of non-failure removal.
as is traditional, one of our corporate innovators seeks to protect citizens (never simply consumers, no, no!) with a defensive patent - sure to now be locked away in a safe until natural corporate patent expiration 1000 years hence.
now and forevermore we shalll sing in praise of this beneficent corporate citizen and their efficacious lawyerly thrust deep into the heart of our once inevitable (but now vanquished) future boring dystopia of ads beamed directly into our brains 24/7.
the Rust kernel could be many years away from being finished.
the number I saw floating around was 3 years to production useful. regardless, C’s end days as the go-to, large systems level language are drawing nigh.
edit: tear
asm? ha! back in my day we were hammering ones and zeros into clay tablets.
no worries.
the net effect of client separation is that your device sees no other layer 2 devices on the wlan besides the gateway. this would typically be enforced at the frame level by the APs and is separate from any radio privacy cryptography.
a properly configured wireless setup would assume every client is compromised and would also disallow local client-client via source routing or proxy ARP or any other escape options. 100% secure? probably not, but its a non trivial barrier that would have to be circumvented.
as with e.g. broken WEP years ago, there are still options to mess with clients at ~Layer 1 but I dont believe its currently as trivial as it used to be.
most properly configured public wifi will enable client separation, of course that potentially still leaves lower level protocol and radio attacks.
more than a few actors may (likely?) have very low yield devices. only takes a few to panic people and governments into stupid actions.