sfilipov

They went a step further. Once a Windows 10 machine is activated, a "hash" of its hardware is taken and associated with the product key. When you reinstall Windows 10, the activation service matches your hardware information with the product key. You need to enter a product key only the first time you install Windows 10 on a particular machine.

True, if real life conversations were like interview conversations, we would judge people/friends whether they gave us the answer we expected when we asked them a question or not. That's ridiculous. People misunderstand questions. If what you get is not what you expect, you can always ask clarifying questions.

1. The idea behind the overlays is to "cache" and reuse as much as you can between images. If you have a long list of packages you install before you copy your app source to the container, you don't have to install the packages again and again every time you do a change to the source and rebuild.

2. You can point Docker to a file - use 'docker save' and 'docker load'.

I think the demand for real chicken/beef will go down but there always will be people who buy "organic", "real", etc.

It is very anecdotal, I believe I read it in an article long time ago around the time the Fukushima disaster happened. It is probably an inaccurate number.

The point is, all 3 faults/human errors shouldn't have happened according to statisticians/mathematicians.

Whenever an article like that appears about a proprietary password manager, I just wonder if there has been any audit on the popular open source ones like KeePass. In fact I've heard that KeePass has some security issues. Is KeePass more secure?

The only overhead I notice is the fact that VirtualBox Shared Folders are really slow. If that's the case, using the paid VMWare plugin can help.

Additionally, if a hacker gets 2 of your passwords, they can see that all you passwords are of the form AxxxxxB, from there it is quite easy to get all your passwords. If you have an "algorithm" that is easy enough to remember, then it is most likely breakable by a smart hacker.

Slightly off-topic but we are really bad at predicting these "very unlikely events" that actually happen more often than expected. Whenever I hear a similar story, I am reminded of the 3 nuclear reactor disasters (Three Mile Island, Chernobyl, Fukushima), each of which shouldn't have happened in 15000 years.

And relay them out of order i.e. a Tor node receives a packet from A, then from B, then resends packet from B, then from A.

The idea is not that expansion per se is bad. Taking VC money to expand is. If you can expand fast without using other people's money then great.

That's the thing with Linux - if you don't like the default DE/WM because it changes too much, then use one which doesn't. User friendly distros pack things like Openbox or i3 with some sensible defaults.

I am always "sudo apt-get install i3" and "git clone dotfiles" away from a configured tiling window manager if that's what I'm after.

If they can crack the database, what's preventing them from getting the key used to encrypt the database?

Probably not. AFAIK the MBPs with PCIe SSDs use a proprietary connector. This SSD uses the standard one. It should not be physically possible to fit one inside the MBP.

Additionally, I thought that's what key stretching and PBKDF2 - to slow down brute force attacks.

According to ArchWiki[1] the Windows version and Developer editions use Dell DW1560 and Intel 7265 respectively.

[1] https://wiki.archlinux.org/index.php/Dell_XPS_13_(2015)#Mode...

Just a reminder regarding the Dell XPS. Dell officially supports Linux on these only on the developer editions. The Windows versions differ in things like the Wi-Fi module and are not recommended if you plan to use Linux.

I doubt there is any (for the user). While there are many benefits to keep using an ad blocker.

To support your point, virtually all crypto vulnerabilities we know of for sure are a result of bugs in implementations rather than problems with the underlying algorithms.

On the other hand there are algorithms which are believed to be backdoored by the NSA (some elliptic curves). These algorithms can be avoided.

In the end, cascading encryption has very limited benefits because the weakest point of a security application is almost never the algorithm used.

I think he refers to File Explorer (explorer.exe) which has nothing to do with Windows Store Apps.

Another humbling aspect is how fragile we are. Even today, there is a number of unpredictable cosmic events outside our control that can destroy humanity and life on Earth very quickly. And every one of us is just a "meat bag" that doesn't know whether it will wake up tomorrow. I find these realizations humbling. Some people get depressed by these thought but they make me appreciate life even more.

He referred to what the GP said - use "git add -p". Here's some introduction (I haven't watched it myself and can't comment on the quality):

http://johnkary.net/blog/git-add-p-the-most-powerful-git-fea...

I believe it is. Being rich and powerful means you'll most likely want to remain such. You would act in the best of your own interest. Ageing has been the absolute guarantee that even the worst of human beings (dictators, criminals with a lot of power) will eventually lose their power thus stop damaging society as a whole.

I think you found the answer already. Already there are server processors with a lot of cores (i.e. 20) - if you can utilise them all then buy one.

However, for most client workloads, more cores does not translate to better performance because many of those cores will just idle. Single-threaded performance is still the king.

I personally like it when the form inserts a space for me after every 4 digits and has a maximum length of the field set to (number of digits + spaces between). For some reason I rarely see websites that have such forms. Maybe it is actually confusing for the majority of users.

How much work it is to extend Electron to create the same thing but for a different language i.e. "Turn Haskell/Python web applications into native desktop apps"?

I am also currently learning Haskell and went with LYAH. I think it is a good enough textbook to introduce the theoretical part while giving enough examples.

My problem was that I was able to understand the concepts but couldn't write functions that do what I want them to do. To gain some experience I am working through 99 Haskell [1] and HackerRank FP domain [2]. Quite a lot of exercises there.

[1] http://www.99haskell.org/ [2] https://www.hackerrank.com/domains/fp/intro

Windows doesn't do queued TRIM (yet).

You are right I don't have emperic data. Maybe I'm wrong.

The reason I believe that retention is higher until you exhaust the cell cycles is explained in the article. For instance, the reason why the active temperature during which writes were done is because lower temperature during such time will somehow strain cells more. But that effect will be noticable if you are close to exhaustion of the cell cycles. Let's say that 3000 write cycles at temperature best for retention are equal to 2000 write cycles at suboptimal temperatures (that's on the pessimistic side I believe).

Well, that's order(s) of magnitude less than the amount of writes a normal user does. The cycles I've used should be ~60 out of 3000. If I've used 2 orders of magnitude less cycles than the product is designed to survive, I expect to have retention which is at least a multiple of the guaranteed one after all cycles (1 year).

In other words, what makes SSDs to eventually fail reads is that the cells can't hold charge. They can't hold charge because the insulation has been damaged ("by design"). At 2% of the designed cycles, the cells are almost brand new, retention of electrons within cells is great.

I want to point out this is worst case retention after the maximum guaranteed writes are done to the SSD. For a typical SSD that means 70TB to 150TB. An SSD which is not close to that level of writing will retain for much longer.

My Crucial m4 from 2 years ago, which I regularly abuse - full disk encryption (more random IO), no TRIM (eventually filling the SSD), and I am at 98% life (i.e. I have used only 2%). The retention at this point is much more than a year. Yes, I expect that if I write something and leave my SSD on the shelf it will be readable in 5 years or more.