If I’m reading the code correctly, this uses the duration of your “time lock” as the duration for how long it will perform scrypt operations on the key derivation.

In other words, if you say you want to “lock” the secret for 5 days, the code will perform scrypt to generate the key for 5 days!!! Then it expects you to remember the iteration count to decrypt it.

I don’t see any use case where that’s a useful mechanism. Especially since it ignores other computers are likely faster at scrypt then yours is.

Sorry, I’m not seeing how your source is helping your argument.

The line I’m responding to is

“This is absolutely false. GitHub Copilot (and it’s competitors) alone are already actively helping and assisting virtually every software developer around the world.”

While your source says: "The majority of respondents (76%) let us know they are using or are planning to use AI code assistants. "

An un scientific survey (aka not random) which it’s self claims the 75% of people who respond used OR ARE PLANNING ON USING (aka, not use it yet), does not equal virtually every developer.

Also wasn’t stack overflow recently getting bad press for selling content to AI companies? Something that pissed large parts of the developer community? Something that would make developers not happy with AI not take the survey?

Anyway, have a great day, and enjoy your AI assistant.

I think you are vastly over estimating how many developers are using GitHub Copilot.

Am I the only one who can’t think of a time DNS has caused a production outage on a platform I worked on?

Lots of other problems over the years, but never DNS.

Assuming these are messages from the businesses customers, in what world would it be sane NOT to listen and respond to your customers?