We just all got lazy and decided to congregate around pre built platforms.
It's not just laziness. The economies of scale can potentially be worth huge cost savings, and higher reliability, in addition to a significantly less burdensome workload to maintain. Especially for smaller sites.
I mean even when I was running my own homelab for years, the FOSS software I relied on was in many ways "pre-built platforms." From the Linux kernel to a distro package manager (and all the maintained packages), I was always standing on the shoulder of giants anyway.
We're starting to see it in some cameras, mostly for still photography, but I don't see why the basic concept wouldn't extend to video files, too. Leica released a camera last year that signs the photo, including the timestamp and location data, and Canon, Nikon, Sony, Adobe, and Getty have various implementations of the technique.
Once the major photo software editing workflows support it, we'll probably see some kind of chain of custody authentication support from camera to publication.
Of course, that doesn't prevent fakes in the sense of staged productions, but the timestamp and location data would go a long way.
Stingrays don't do shit for this. That's mostly real time location data focused in by tricking your phone into reporting its location to a fake cell tower controlled by an adversary. That doesn't get into the data in your phone, and even if someone used the fake tower to man in the middle, by default pretty much all of a phone's Internet traffic is encrypted from the ISP.
The world of breaking disk encryption on devices is a completely different line of technology, tools, and techniques.
Weight distribution and jiggle control is something I can't relate to though
It's not hard. Put on a really heavy backpack and leave the straps super loose, and go try to move around, maybe a few athletic moves that involve changing speed or direction. Compare to a tight backpack with a waistband and shoulder straps properly strapped to your body, and try to move around again. The straps help control the extra motion so that you're in better control.
Or run around in shoes 5 sizes too big. Or go for a run with your arms loose and intentionally left limp, swinging around like pendulums.
The whole world has a million examples of why providing bracing and support makes for more efficient and comfortable movement.
With passenger vehicles, the problems have largely been solved. With motorcycles, there are still some tradeoffs on range (especially highway). With large cargo trucks, the weight causes issues with range, weight capacity, and charging times. With aircraft, there's not really competition on the horizon.
And electrification of heat production itself for climate control, cooking, hot water, industrial processes, etc. is coming along, too, on an application by application basis. (But note that the energy "lost" to heat is less of a factor for these uses.)
Yeah, so you have to divide it by a factor of 5. Which still makes gasoline roughly 5 times as energy dense than this prototype battery, instead of 25 times.
I haven't found anything that indicates it can differentiate a legitimate access from a dubious one
It's not about legitimate access versus illegitimate access. As I understand it, these keychains/wallets can control which specific app can access any given secret.
It's a method of sandboxing different apps from accessing the secrets of other apps.
In function, browser access to an item can be problematic because browsers share data with the sites that it visits, but that's different from a specific app, hardcoded to a specific service being given exclusive access to a key.
But aren't secrets stored there still accessible when the machine is unlocked anyway?
I think the OS prevents apps from accessing data in those keychains, right? So there wouldn't be an automated/scriptable way to extract the key in as easy of a way.
It's probably more likely that Microsoft wants out of the board so that it can be free to pursue acquisitions of OpenAI's competitors without a conflict of interest.
I remain unconvinced that this is some big paradigm shift, and that the instruction set itself is mostly irrelevant for battery life and performance per watt.
Yes, Apple achieved a big jump with its first M1 at delivering some pretty amazing performance per watt, compared to contemporary chips from Intel.
But a closer look has shown that each successive generation of M-series Apple Silicon has been chasing higher performance at the cost of energy efficiency. Which is fine, but shrinks the gap.
And then, if you look at AMD's low power x86_64 CPUs for laptops, you'll see that they're also able to deliver significant power savings compared to Intel. Comparing like for like, in terms of TSMC node, you see that AMD performance per watt seems to be in line with Apple's. It's just that Apple's comparative advantage in business/legal strategy (not engineering) has them locking up TSMC capacity earlier.
Finally, a comparison of Apple's mobile ARM SoCs to other manufacturers' mobile ARM SoCs (including Qualcomm and Samsung) shows that Apple has a significant performance/efficiency lead over even other ARM chips.
So it's probably not the instruction set. It's just the engineering of the chips themselves, boosted by Apple's business/logistics strategies getting their products to market first.
Frankfurt determines that bullshit is speech intended to persuade without regard for truth. The liar cares about the truth and attempts to hide it; the bullshitter doesn't care whether what they say is true or false.
They just move onto hyper-expensive cars, watches, Warhammer figurines, purses, jewelry, etc. The human instinct to flaunt and/or collect is pretty strong in certain people.
Do thin clients and PXE require a server specifically configured to serve a boot image? (Genuinely asking.)
I'm not sure whether this project is doing something new by just accessing network resources that are nothing more than shared files, without any specific software running on the server (beyond just a server serving files).
Blue hydrogen is made by stripping the hydrogen from fossil fuel hydrocarbons (chains of hydrogen and carbon, hence the name), and sequestering the carbon. It produces a fuel that contains enough chemical energy to be burned as fuel, but without the carbon atoms that would turn into greenhouse gases.
Most hydrogen currently produced though, is gray hydrogen (made from natural gas, but without sequestering the carbon, so that CO2 is emitted into the atmosphere).
Legacy nodes (known in the industry as "mature" nodes) remain in use after they're no longer cutting edge. Each run teaches lessons learned for improving yield or performance, so there's still room for improvement after mass production starts happening.
No, kw (power) is a fundamentally different unit from kwh (energy).
Energy is conserved, so that's how we use it and pay for it, but power capacity is very important for infrastructure. A battery that can hold 1 GWh worth of energy, but can only output it at a rate of 10 MW, might have a ton of limitations to its usefulness.
It's not just laziness. The economies of scale can potentially be worth huge cost savings, and higher reliability, in addition to a significantly less burdensome workload to maintain. Especially for smaller sites.
I mean even when I was running my own homelab for years, the FOSS software I relied on was in many ways "pre-built platforms." From the Linux kernel to a distro package manager (and all the maintained packages), I was always standing on the shoulder of giants anyway.