Hacker News: mnarayan01

New comment by mnarayan01 in "Implementing Cosine in C from Scratch (2020)"

mnarayan01 — Wed, 30 Mar 2022 00:47:46 +0000

For anyone else confused by this, the control logic described in the comment happens in https://github.com/ifduyue/musl/blob/master/src/math/cos.c

New comment by mnarayan01 in "Improving Git protocol security on GitHub"

mnarayan01 — Thu, 02 Sep 2021 01:47:27 +0000

Git has all sorts of options for using proxies, but running socat would be the quick and dirty way to do this, something like:

  socat TCP-LISTEN:8080,fork,reuseaddr OPENSSL:github.com:443

would let you use an HTTP connection to your less archaic machine. Could even configure git to automatically do the rewrite similar to https://stackoverflow.com/questions/1722807/how-to-convert-g.... There's security considerations here so don't just do this blindly, but if no more unencrypted git protocol is a real pain point there's pain free ways around it.

New comment by mnarayan01 in "A Look at the CPU Security Mitigation Costs Three Years After Spectre/Meltdown"

mnarayan01 — Thu, 07 Jan 2021 03:40:59 +0000

Unfortunately e.g. the RHEL 7 world doesn't have mitigations=off yet (in addition to many other kernel command line sugars).

New comment by mnarayan01 in "Fixing Mass Effect black blobs on modern AMD CPUs"

mnarayan01 — Sun, 19 Jul 2020 19:33:51 +0000

0/0 = NaN

New comment by mnarayan01 in "Things Markdown got wrong"

mnarayan01 — Sat, 04 Apr 2020 04:57:49 +0000

> Code Blocks probably aren't necessary

When you're reading raw markdown they're extremely useful for short snippets since they save you two wasted lines per block.

New comment by mnarayan01 in "A QUIC look at HTTP/3"

mnarayan01 — Sat, 14 Mar 2020 12:50:04 +0000

The other requests are still taking the latency hit.

New comment by mnarayan01 in "Types will be part of Ruby 3 stdlib source"

mnarayan01 — Sat, 20 Apr 2019 04:54:01 +0000

That's a block returning a Hash; see bhuga's sibling comment where he notes that they're using blocks to lazy load the constants in the type definition, which may seem silly for e.g. Integer, but consider e.g. some high-dependency Rails model which requires auto-loading 10,000 other classes.

New comment by mnarayan01 in "Types will be part of Ruby 3 stdlib source"

mnarayan01 — Fri, 19 Apr 2019 12:27:01 +0000

Then you'd need an extra set of delimiters, e.g.:

  sig {{name: String, returns: Integer}}

New comment by mnarayan01 in "Types will be part of Ruby 3 stdlib source"

mnarayan01 — Fri, 19 Apr 2019 10:31:44 +0000

The parser thinks that's a block not a hash.

New comment by mnarayan01 in "Problem solving with Unix commands"

mnarayan01 — Thu, 14 Feb 2019 15:28:12 +0000

> mouse(!) selection of arbitrary text that can be piped to commands and so on

E.g.:

  xclip -out | ...

or do you mean something different?

New comment by mnarayan01 in "Major sites running unauthenticated JavaScript on their payment pages"

mnarayan01 — Thu, 29 Nov 2018 15:52:31 +0000

You can specify multiple digests for an asset, so a non-versioned one can be updated sans downtime:

1. Provider informs clients that a new version with digest X will be deployed.

2. Clients add the new digest in addition to the current digest.

3. Provider switches to new asset version.

4. Clients remove old digest (optional).

Versioned assets are obviously better unless you're in a really weird situation, but SRI doesn't particularly require them.

New comment by mnarayan01 in "Major sites running unauthenticated JavaScript on their payment pages"

mnarayan01 — Thu, 29 Nov 2018 14:36:05 +0000

> 3rd parties should version their JavaScript resources with a version number in the URL

I mean yes this is true, but it seems almost totally orthogonal to SRI (which is aimed at security AIUI), particularly given you can give more than one hash for a particular resource. If for some reason a third-party can't use fingerprinted URLs, they can still update the resource provided they give "sufficient" advanced notification of the new fingerprint to clients.

> And this should be a manual process because automating it would defeat the whole point of SRI.

Obviously it should be offline/write-once, but unless you're reviewing the actual assets as well I'm not sure I see the need to avoid automation.

New comment by mnarayan01 in "Killing processes that don't want to die"

mnarayan01 — Tue, 25 Sep 2018 04:11:17 +0000

https://www.kernel.org/doc/Documentation/cgroup-v1/freezer-s...

New comment by mnarayan01 in "µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime"

mnarayan01 — Wed, 08 Aug 2018 18:53:57 +0000

The #ifndef rigamarole is https://en.wikipedia.org/wiki/Include_guard and at least used to be fairly common. I also used to see the __FOO_BAR_H__ naming convention for these defines all over the place. I'm not sure if __ identifiers being reserved is a (not very) new thing or if it's always been around and people are just now more generally knowledgeable about the fact that they shouldn't be used.

New comment by mnarayan01 in "µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime"

mnarayan01 — Wed, 08 Aug 2018 16:11:21 +0000

If you include it (possibly indirectly) in a file which you compile, then no, you do not need to compile it separately.

New comment by mnarayan01 in "How I gained commit access to Homebrew in 30 minutes"

mnarayan01 — Tue, 07 Aug 2018 17:18:48 +0000

> Signing each commit is totally stupid. It just means that you automate it, and you make the signature worth less.

New comment by mnarayan01 in "How I gained commit access to Homebrew in 30 minutes"

mnarayan01 — Tue, 07 Aug 2018 16:50:31 +0000

Linus (from 2009) on problems with signing every commit: http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-t...

New comment by mnarayan01 in "Building an Inclusive Code Review Culture"

mnarayan01 — Mon, 30 Jul 2018 16:50:03 +0000

  if a = foo()

versus:

  if (a = foo())

Sometimes idiomatic patterns vary based on things which are not amiable to mechanical correction.

New comment by mnarayan01 in "The unreasonable effectiveness of Soccermatics? (2017)"

mnarayan01 — Thu, 26 Jul 2018 16:01:10 +0000

The article looks like it's just a generic sports' journalist reporting on a novel statistical technique, with cross language translation added into the mix for extra confusion. I wouldn't take it too literally.

I'd guess that either "Impect disregards all passes that go backwards or don’t beat any defender" would be better phrased as "Impect disregards passes unless they go forward or beat defenders" or the statisticians would defend the original solely in terms of it being a heuristic that makes the problem more tractable.

Additionally, your linked example, with #25 picking up the ball in a danger position after a deflection, is the kind of "penalty box slop" that, naively at least, seems extremely difficult to handle analytically.

New comment by mnarayan01 in "Transfer.sh – File sharing from the command line"

mnarayan01 — Thu, 21 Jun 2018 14:50:40 +0000

From your source machine:

  < /path/to/source ncat remote-host 8001

On your destination machine:

  ncat -l 8001 > /path/to/dest

Though in most situations with files of reasonable size, you're probably going to be better off running through `gzip -c`.