HackerTrans
TopNewTrendsCommentsPastAskShowJobs

larntz

no profile record

comments

larntz
·2 months ago·discuss
He didn't get the job. :(
larntz
·3 months ago·discuss
I think a few games are only on NFL Network (not always included in the base cable subscription) also. And you'll need Peacock if you don't have cable/antenna.
larntz
·8 months ago·discuss
Anyone remember Lycoris? https://deadlinux.fandom.com/wiki/Lycoris

I never used it and had to look it up, but this post reminds of it. I think they might've charged for it also.

Here's a review thread from 2002 slashdot... https://linux.slashdot.org/story/02/03/18/1916248/lycoris-de....
larntz
·10 months ago·discuss
This is ridiculous logic. When a person makes a premeditated decision it was their choice, and only their choice. There is no one else responsible.

Is he required to permanently fire anyone because of a government shutdown? If the answer is no, then he made a choice to do so (if firings happen).
larntz
·10 months ago·discuss
Has anyone read The Programmer's Brain and have an opinion about it? I'd like to improve my ability to read and understand code and was thinking about reading it.

https://www.manning.com/books/the-programmers-brain
larntz
·12 months ago·discuss
If you're working locally I can't think of much. OSC52 works to copy to your local clipboard from a remote system (e.g., over ssh) from within tmux or nvim as long as you are using a terminal that supports it.

I use it to copy from remote system when I'm in nvim (`"+y`).

Here are a couple links that relate to tmux and nvim.

- tmux: https://github.com/tmux/tmux/wiki/Clipboard

- nvim: https://neovim.io/doc/user/provider.html#clipboard-osc52
larntz
·last year·discuss
> Your secrets are not safe from someone if someone needs them to run your code.

This is true. I don't disagree with that or you're assessment of repo secrets.

My comment was in the context of the grandparent committing secrets to a private repo which is a bad practice (regardless of visibility). You could do that for tests, sure (I would suggestion creating random secrets for each test when you can), but then you're creating a bad habit. If you can't use random secrets for tests repo secrets would be acceptable, but I wouldn't use them beyond that.

For CI and deploys I would opt for some kind of secret manager. CI can be run on your own infrastructure, secret managers can be run on your own infrastructure, etc...

But somewhere in the stack secret(s) will be exposed to _someone_.
larntz
·last year·discuss
I wouldn't rely on anything other than rotating leaked credentials.
larntz
·last year·discuss
Yes. Either via a secret manager (eg vault) or configured as repo secrets if that kind of infra isn't available.

https://docs.github.com/en/actions/how-tos/security-for-gith...

Never commit secrets for any reason.
larntz
·5 years ago·discuss
This tweet seems to confirm it is a bgp issue...

https://twitter.com/GossiTheDog/status/1445063880963674121?s...