> patched an Encrypted DNS Server to store the original TTL of a response, defined as the minimum TTL of its records, for each incoming query

I agree that low TTL could help during an outage if you actually wanted to move your workload somewhere else, and I didn't see it mentioned in the article, but I've never actually seen this done in my experience, setting TTL extremely low for some sort of extreme DR scenario smells like an anti pattern to me.

Consider the counterpoint, having high TTL can prevent your service going down if the dns server crashes or loses connectivity.

If you work in powershell you can start out in the terminal, then when you've got whatever you need working you can grab the history (get-history) and write it to a file, which I've always referred to as a `sample`. Then when it becomes important enough that other people ask me about it regularly I refactor the `sample` into a true production grade `script`. It often doesn't start out with a clear direction and creating a separate file is just unnecessary ceremony when you can just tinker and export later when the `up-enter' pattern actually appears.

It's another reformulation rather than a true proof. Now, instead of wanting a proof of a theorem, now we just need to prove that this proof is actually proving the theorem. The proof itself being so incomprehensible that it can't on its own be trusted, but if it can be shown that it can be trusted then the theorem must be true.

Consider a similar layout to OP but the landscape images will span multiple columns as well as everything it already does.

The thing about masonry is that it adapts to the size of the images. You could already do masonry using flexbox if you know the image sizes (https://github.com/hannasm/masonflexjs). Doing it as a true mosaic layout would be a step above current capabilities. At that point it's probably pretty easy to create configurations that don't fit perfectly/ require lots of empty space to layout nicely though.

There's nothing special about whitespace (unless you write python).

Capitalization and a bunch of other stuff in your coding convention document are usually just signs that you have poor tooling and lack of skill.

Give me a PR that satisfies the requirements and the appropriate test cases and i'll happily rewrite it to spaces only indented with curly braces on newlines and etc... as I see fit.

The hard part is the first two tasks, you can train an intern to do the third

  > these papers keep stapling on broad philosophical claims about whether models can “really reason” that are just completely unsupported by the content of the research.

Usually there may be some interesting ideas hidden in the data but the paper's methods and scope weren't even worthy of a conclusion to begin with. It's just one data point in the vast sea of scientific experimentation.

The conclusion feels to me like a cultural phenomenon and it's just a matter of survival for most authors. I have to imagine it was easier in the past.

"Does the flame burn green? Why yes it does..."

These days it's more like

"With my two hours of compute on the million dollar mainframe, my toy llm didn't seem to get there, YMMV"

In a gerontological context: It would interesting to understand more about his genealogy. Does the age of 76 mark an above or below average age in his family and their historical lifespan?

As someone who has experienced great success in life, and also been (at least at one point) in peak physical shape, the cause of his demise seems especially interesting to me.

The security implications of trusting some random Linux distro produced by anyone, to put unfettered access to your stuff on the Internet seems iffy.

Also this doesn't actually seem to be a kvm because it requires a separate cpu to access the video and USB. It seems to me more like a vnc / remote desktop kind of thing. Is there something I'm missing?

Comments URL: https://news.ycombinator.com/item?id=43317420

Points: 1

# Comments: 1

To me it could be:

Something accessible via a file descriptor that can be read from and/or written to. Feel free to add some other details like permissions, as needed.

Perhaps they should allow for folders as well, since a complex piece of hardware undoubtedly needs to expose multiple files to be robust, but the underlying intention was to create a standardized way of interacting with hardware.

Sectors on disk, switches, analog devices like a speaker, i2c and other hardware ideas all need to be read from or written to in some form to be useful

  > A Thread Across The Ocean by John Steele Gordon

When learning a new codebase, and I'm looking for an example of how to use feature X I would look in the tests first or shortly after a web search.

It seems to me like the second half of this article also undermines the main idea and goal of using unit tests in this way though.

  > Descriptive test name, Atomic, Keep tests simple, Keep tests independent

A test with a bunch of mocks, helpers, overrides and assumptions does not help anyone understand things like how to use feature X or the correct way to solve a problem with the software.

There are merits to both kinds of tests in their time and place but good integration tests are really the best ones for documenting and learning.

  > In 2006 it was confirmed that the combination of phentermine and the serotonin precursor 5-hydroxytryptophan (5-HTP), in place of fenfluramine, significantly decreased alcohol withdrawal seizures in rats.[21]

It would be great to just have one nice calculator to lookup trustworthy load data on standard home depot materials.

But at planetary scale would Tor scale in an environmentally friendly way?