fierro

Sorry, I did make a mistake in marrying my argument to "fasting." I meant, modulation I guess. You don't want to blast your system with dopamine constantly. Also "reducing the impulsive behaviors that are rewarded by it" is basically the same thing as "don't do the thing that gives you dopamine".

I think Deep Work is highly related to the discussion of distractions and superficial "candy like" experiences. Pretty tough to do deep work (and conversely, easy to do shallow work) when you're assailed with notifications, constantly responding to texts, etc.

facts

This is a pretty demonstrably false statement. I think what you mean to say is that dopamine fasting may have no concrete benefits? But certainly manipulating/controlling your own dopamine levels does do something, unless you're contending that dopamine itself does nothing, which you're not. Dopamine fasting does let your receptors upregulate and resensitize. Take Adderall every day for a month and see how you feel -- you'll realize your receptors have been pretty downregulated and you need a break.

yeah that particular passage is cringe and colors the whole article as condescending, when in reality there are a lot of good points made.

exactly. A tooling kerfuffle can really kill my vibe.

This is such an amazing point. It's not about time saved, it's about mental continuity and the ability to stay in a state of deep work.

my guy out here rolling his own TLS implementation

When can I run Kubernetes on this to host my personal blog?

wow thanks for calling that out. Just spent an hour browsing through it and was basically an Operating Systems refresher course. Great resource!

what is a real time kernel vs a normal kernel? just "faster"?

being found to be sexy by others is not against our rules

what keyboard do you use? And do you feel it's optimized for Vim?

How can you be sure the estimated max server capability is not actually just a limitation in the client, i.e, the client maxes out at sending 224k requests / second.

I see that this is clearly not the case here, but in general how can one be sure?

the fundamental tenet in Go is that every error should be handled. Here is an excerpt from Dave Cheney that clarifies this:

"For the truly exceptional cases, the ones that represent either unrecoverable programming mistakes, like index out of bounds, or unrecoverable environmental problem, like running out of stack, we have panic.

For all of the remaining cases, any error conditions that you will encounter in a Go program, are by definition not exceptional — you expect them because regardless of returning a boolean, an error, or panicing, it is the result of a test in your code"

These are great readings regarding errors in Go.

https://dave.cheney.net/2014/11/04/error-handling-vs-excepti...

https://dave.cheney.net/2015/01/26/errors-and-exceptions-red...

any sophisticated bots are rotating IPs or pulling from a large pool of IPs. In many cases of fraud/abuse, rate limiting based on IP doesn't work well enough.

What is the game theoretic outcome if both parties have read this article?

This feature is enabled at the behest of the site owner. I feel like site owners and operators should decide who gets to visit their site. Am I missing something obvious here?

why is it assumed the web ought to be crawleable?

what? Have you ever dealt with a DDoS attack and the consequences on your availability and infra health?

this is what the blog post fails to address. Is the FIDO2 hardware key approach abusable? Yes. More so than regular image based CAPTCHA? No, like you said, there are well established services for "mechanical-turking" away the problem.

I would also pay in the 10k+ range for this, easily.

This is a super cool idea that probably every startup has considered at some point -- "we should package this up and sell it as company-in-a-box". Executing well on this will be huge!

the problem isn't necessarily in the abstraction. It's in the language design. Terraform (HCL) started off as a declarative language. Then people wanted string concatenation. Then conditionals. Then modules. You end up with this kludge of a language that benefits from none of the foresight of having been designed as a general purpose programming language from the outset -- no unit testing, poor control structures, etc.

not really. these are all facts, not opinions.

not sure how anything more simple would be useful. We aren't writing Hello Worlds here.

most of that is boilerplate and not actually anything difficult

I see, so a workload spins up and wants to learn something about itself and uses identity verification to gain access to it? My use case was an untrusted node getting a centrally issued key to join a p2p VPN