rgro

Although it was a little late to the party, flexbox solves a bunch of issues with css layouts.

Here's a working example that doesn't use tables: https://jsfiddle.net/q8zxxr3b/

Or, here's the inline example:

  <div style="display: flex; height: 100%; flex-direction: column; align-items:center; justify-content: center;">
      <div style="text-align: center;">
          <h1>Hello world</h1>
          The following green square should be centered:<br />
          <div style="display: inline-block; width: 30px; height: 30px; background: green;"></div>
      </div>
  </div>

The worst part about the DNT header was the requirement for the tracking companies to regulate themselves. Initially, the header was opt-in, but with the introduction of IE10, Microsoft decided that the option was going to be opt-out. Once the the DNT header was gaining traction and a not-so-small percentage of people began sending the header, the companies had no reason to comply, and the initiative sorta fell out of favor.

For blocking tracking, the most effective tools are browser extensions made to block ads. Ghostery provides comparisons on an non-biased website between the methods of blocking tracking through browser modifications [1]. According to the site, the Do Not Track header actually has an effect with a difference of 18% in cookie size when the header is set. AdBlock Edge and disabling third-party cookies results in a 59% and 40% decrease in cookie size respectively. It seems that the easiest thing you can do to lessen your internet footprint would be to disable third-party cookies and enable the DNT header, and the majority of tracking can be eliminated through the use of a browser extension. (But with the recent revelations [2], using a browser extension may actually reduce your browsing experience if you don't have the RAM to spare.)

[1] http://www.areweprivateyet.com/ [2] https://news.ycombinator.com/item?id=8802424

It seems that this also hashes the files to produce a fingerprint. Check out the fingerprinter [1] for the raw details on how it's done, but basically, if the file is below the "sparseFingerprintThreshold" of 5 MB, the whole file is hashed. Any file above is "sparsely hashed" where the first 512 KB, middle 512 KB, and end 512 KB are hashed and combined to produce the fingerprint for that file. It shouldn't produce any performance concerns on large files, so it should be safe to use for your movie collection.

[1] https://github.com/oniony/TMSU/blob/master/src/tmsu/common/f...