> It has been argued that an interstellar mission that cannot be completed within 50 years should not be started at all. Instead, assuming that a civilization is still on an increasing curve of propulsion system velocity and not yet having reached the limit, the resources should be invested in designing a better propulsion system. This is because a slow spacecraft would probably be passed by another mission sent later with more advanced propulsion (the incessant obsolescence postulate).
I think carbon to value is the best way. If valuable uses for carbon are found companies will work on carbon capture themselves without political purpose.
A huge number of npm dependancies I use are basically unmaintained, have tons of forks and multiple PRs with the same fixes. I choose the one I like and move on, the magic of github!
Probably because there's a dispute over whether anyone was actually arrested, or if they arrested the wrong person, because the journalist who received the video says his source has not been arrested.
Once again, it seems that it was an excuse to weaken the security of all iPhone users rather than getting information from a specific device. In the case of San Bernandino the FBI was able to use Cellebrite to crack the attacker iPhone without Apple creating backdoors.
In that case, Apple already had a backdoor, or they wouldn't have been able to comply in the first place: the device in question did not yet have the "secure enclave" enforcement of pin code back-off and supported firmware updates by Apple without the user's pin code. Apple spending the time to make a firmware--which incidentally anyone with Apple's private firmware signing key (the real back door) could easily have done (as we seriously already have had custom firmwares for ssh bootstrap and pin code brute force in the community)--isn't them "creating" a backdoor, it is them "using" a backdoor. Thankfully, it is my understanding that Apple decided to fix both of these issues in subsequent devices, and so while there are clearly still bugs there hopefully are no longer any obvious backdoors.
>Thankfully, it is my understanding that Apple decided to fix both of these issues in subsequent devices, and so while there are clearly still bugs there hopefully are no longer any obvious backdoors.
Does this mean. There's a new unpatched exploit out there that greykey is using?
From what I can tell, it simply tries to brute force the password (perhaps with some informed suggestion). It does appear to have access to an exploit that bypasses/disables the encryption lock that wipes data off the phone after failed attempts, but it does not appear to utilize an exploit/backdoor to gain access to the device; it gains access the "legitimate" way.
As flohofwoe has pointed out, yes this can currently be done using Nvidia specific extensions.
If you are interested, a friend of mine and a few coworkers pieced together a small proof-of-concept game engine in their spare time that uses Vulkan ray tracing on Nvidia RTX cards. They finally released it on GitHub a few days ago:
There are days when I wish that DirectX was the open standard, rather than the other way around. It's such a cleaner, better designed API - quite possibly because it was not open, and so it doesn't have anywhere near as much of the design-by-committeeisms that infect OpenGL/Vulkan.
