With the French guy on this. Weed is expensive even when legal, and if it’s not, you really don’t want to share it with any rando because you can get pegged for distribution.
It helps if and only if the glucose stays as glucose and is not metabolized. Wood is a good application of this, as its cellulose fibers are made of glucose, in a form that is very stable and can stay locked away for a long time (especially if the tree is alive as it does not metabolize the glucose in its own wood and has anti-predation adaptations that actively guard it against other organisms). However, if the glucose decomposes, i.e. is metabolized, it is converted either directly to CO2 or into other compounds that eventually end up as CO2, essentially returning the captured carbon back to the atmosphere.
I assume they mean how long many old growth forests have been growing (though even then thousands of years is on the younger end), not the time it took for trees to evolve.
It’s expensive and has only the advantage of catching CO2
It doesn’t even do that well. Algae have short lifespans and when they decompose, the CO2 will go right back into the atmosphere. It’s the same reason you can’t reasonably capture CO2 with small plants like grasses, nor does the carbon inside you count as captured. The reason trees “capture CO2” is because trees live for a long time and wood decomposes very slowly, and therefore keep its carbon locked in the wood for a long time. The point of capturing carbon is you take it out of circulation for as long as possible.
There are ways to have algae capture carbon, but they are fairly involved (read: very expensive) processes whose scalability is still uncertain. Certainly not a tank in the street.
It breaks the cardinal rule of executing privileged code: Only code that absolutely needs to be privilaged should be privileged.
If they really wanted to have their logo in the boot screen, why can’t they just provide the image to the OS and request through some API that they display it? The UEFI and OS do a ton of back and fourth communication at boot so why can’t this be apart of that? (It’s not because then the OS and by extension the user can much more easily refuse to display what is essentially an ad for the hardware vendor right? They’d never put “features” in privileged code just to stop the user from doing anything about it… right?)
The article didn’t mention this, but would disabling the UEFI logo in the boot screen mitigate the vulnerability until proper patches get rolled out? (Or honestly at this point, I’d keep it disabled even after it’s patched in case they didn’t patch it right. UEFI’s are all proprietary so it’s not like you can check.) Since the vulnerability is in the image parser, would bypassing that be enough?