LucidMew

I'm still waiting for the Define R4 unboxing/review. 

That isn't concrete, that's cement.  You didn't add any aggregate (you know, the sand the instructions on the bag called for), so stop calling it concrete.

"Lazy" is a term in computer programming that pretends to load the information and if that information is actually used then it actually calculates it for you. https://en.wikipedia.org/wiki/Lazy_evaluation
 
You can have an "infinite" list in python, and store it with a finite amount of memory, because you only calculate what you actually use. It's also commonly used in databases as well with Hibernate. 

Source 1: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00145.html
Source 2: http://seclists.org/oss-sec/2018/q2/189
 
 
 
 
Honestly, I don't care about all these vulnerabilities. I'm not going out of my way to patch my 5820K, because I'm not a cloud service provider. However, with all these similar vulnerabilities being found with Intel's CPUs, I wonder how many unknown vulnerabilities are still undiscovered, and when all these will actually be fixed in hardware.
 
There is a patch available on the seclists website, but I'm not sure what exactly that patches; Intel's website says software engineers can use Eager FP restore instead of Lazy FP state restore, so it seems like an update to windows and/or applications can fix this? It's not entirely clear if that'll fix it, or even if it's exploitable from javascript from the browser.
 
These sort of registers do hold AES encryption keys, so it's fairly high priority for people who actually use it.
 
 
edit/update 1:
For those who don't know, "Lazy" is a term in computer programming that pretends to load the information and if that information is actually used then it actually calculates it for you. https://en.wikipedia.org/wiki/Lazy_evaluation
You can have an "infinite" list in python, and store it with a finite amount of memory, because you only calculate what you actually use. It's also commonly used in databases as well with Hibernate. 
 
Another source that puts it in more human readable terms: https://www.theregister.co.uk/2018/06/13/intel_lazy_fpu_state_security_flaw/
 
 
 
No word if desktop windows 7/8.1/10 is patched or not.
 
 
I guess it kinda makes sense that eager might be faster than lazy, depending on the data size and how frequently they need to be evaluated to its actual value. But I would think that it's more complex than "more often than not, eager is faster than lazy".
 
Mitigated for years. Cool. People don't have to freak out. And AWS is protected. With no exploit code using this bug discovered in the wild just yet.
 

"Lazy" is a term in computer programming that pretends to load the information and if that information is actually used then it actually calculates it for you. https://en.wikipedia.org/wiki/Lazy_evaluation
 
You can have an "infinite" list in python, and store it with a finite amount of memory, because you only calculate what you actually use. It's also commonly used in databases as well with Hibernate. 

There were also a bunch of (xbox) codes for The Witcher 3 that flew by right before the trailer.

There were also a bunch of (xbox) codes for The Witcher 3 that flew by right before the trailer.

There were also a bunch of (xbox) codes for The Witcher 3 that flew by right before the trailer.

There were also a bunch of (xbox) codes for The Witcher 3 that flew by right before the trailer.

My subscriptions page (not front page) isnt showing this video. Anyone know what is happening?

Nicehash is paying $1.88/day for a 1070 right now,  which is lower than you would make direct mining. So maybe not bad for someone who isn't very tech savvy? But pubg goes for $30 and in 28 days you can make $52.64 with nicehash (before electric costs) which is ridiculously easy to use. 
 
Neat idea, not that great in practice. You'd be better off just pool mining zcash and using an exchange or two. 

This is actually a pretty damn big deal. After reading the Equihash algorithm whitepaper, I've always liked the algorithm. Super customizable and requires a bunch of memory, plus the fact that GPUs get not even a thousand solutions a second is pretty cool.

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking:

This OP: iPhone X is dead
That OP: iPhone X got 35% of the industry profits in 2017
 
:thinking: