HN user

danadam

66 karma
Posts1
Comments43
View on HN

So many of these things would have been really painful to find if I'd had to sift through every line of a big commit.

So to watch people intentionally balling up an entire PR's worth of commits and squashing them together to throw away the only (in my mind) thing that version control is good for, is truly baffling.

But yeah, there are plenty of people like the parent in that camp

I'm confused. The parent doesn't want big commits but rather, as they wrote twice, commits that are small, atomic and without noise. So presumably "fix typo" would be removed during rebase but "rename function" would stay and be separate from "implement logic".

EFF is leaving X 3 months ago

IIUC, "clearly shows" doesn't apply to "they have certain concerns" but rather to the part that you replaced with "...". In other words "the statement clearly shows that they value [their certain concerns] more highly than the kind of stuff we tend to think the EFF primarily cares about"

Normalization increases gain of all frequencies at any given point-in-time while reducing gain of all frequencies at other points in time.

When you do that then the difference between the loudest and the quietest part of the audio gets reduced. That's dynamic range reduction.

trace it down to the select bitset having a hardcoded max of 4096

Did it change? Last time I checked it was 1024 (though it was long time ago).

and no bounds checking!

_FORTIFY_SOURCE is not set? When I try to pass 1024 to FD_SET and FD_CLR on my (very old) machine I immediately get:

  *** buffer overflow detected ***: ./a.out terminated
  Aborted
(ok, with -O1 and higher)

page 112

if [[ "${1-}" =~ ^-*h(elp)?$ ]]; then

... is an option that starts with one or multiple - characters ...

"one or multiple" is + not *. The regex above will also match "h" and "help" without - character(s).

I have a bookmarklet, since forever, labelled "sane width", with the following code:

  javascript:(function(){var newSS, styles='body { width: 800px ! important; margin: auto !important } '; if(document.createStyleSheet) { document.createStyleSheet("javascript:'"+styles+"'"); } else { newSS=document.createElement('link'); newSS.rel='stylesheet'; newSS.href='data:text/css,'+escape(styles); document.getElementsByTagName("head")[0].appendChild(newSS); } })();
It forces the body width to 800px and centers it. Crude but it is enough for me.

No, the quotes are not seen by the program. The program receives a list of strings, it does not get the information about whether and how those strings were originally quoted in the shell.

With quotes the program will receive a single argument -n␣o␣p␣e instead of multiple ones -n, o, p, e. At least it works on the machine here:

    ]$ echo "-n o p e"
    -n o p e
    
    ]$ /bin/echo "-n o p e"
    -n o p e

However, if you put on a headset and apply only frequencies above 16kHz, you will distinctly notice a change in the pressure in your headset's ear cups.

If you put something above 16 kHz at full scale and/or if you play it extremely loud then maybe. With typical music content at typical volumes, I doubt it.

When I use an FFT to view the spectrogram on YouTube music videos, it is very obvious that YouTube applies a lowpass filter at 16kHz on all videos (true since 2023 at least).

Maybe with a browser that doesn't support Opus and gets AAC instead (Safari?). With Firefox or Chromium on Linux I get up to 20 kHz, which by design is the upper limit in Opus codec.

That's unrelated. This difference is the inter-aural or inter-channel difference and 16/44.1k can capture that to much greater precision than microseconds.

Some math [1]

44.1k file containing pulses with sub-sample delays [2]

Something similar, but square wave, and nicely showing that timing precision actually depends on bit-depth and not the sampling rate [3]

Some practical experiments with capturing the playback of such files and verifying that the delay is preserved: pulse [4] and square [5]

[1] https://troll-audio.com/articles/time-resolution-of-digital-...

[2] https://www.audiosciencereview.com/forum/index.php?threads/t...

[3] https://audiophilestyle.com/forums/topic/58511-time-resoluti...

[4] https://www.head-fi.org/threads/can-you-hear-upscaling.97295...

[5] https://www.head-fi.org/threads/can-you-hear-upscaling.97295...

The problem with sites that extract text from movies and other content is that they reduce people’s desire to pay a fair price for content

A bit strange to use "fair", which (to me) seems to be quite on a subjective side. Do people still think that the price is fair and only don't want to pay it? Or maybe some of them don't consider the price to be fair anymore :-)

Why Not Comments 2 years ago

So I appended a "=> yes!" to the existing comment as well.

You will read it in 3 months and cry in despair "But why, my past self, why is it needed?!" :-)