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....

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).

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

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

I wouldn't rely on anything other than rotating leaked credentials.

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.

Repo secrets are just stored on someone's computer and they obviously have the keys. This is what I mean.

Same for your vault. The vault might be encrypted, but at some point you have to give the keys to the vault.

Your secrets are not safe from someone if someone needs them to run your code.

> 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_.

Does that entire model fit in gpu memory? How's it run?

I tried running a model larger than ram size and it loads some layers into the gpu but offloads to the cpu also. It's faster than cpu alone for me, but not by a lot.

you're right, actually noticed gpu clocking up and down with 32b, 14b clocks up fully and actually runs faster

I wrote a similar post about a week ago, but for an [unsupported] Radeon RX 5500 with 4Gi RAM with ollama and fedora 41. Can only run llama:3.2 or deepseek-r1:1.5b, but they're pretty usable if you're ok with a small model and it's for personal use.

I didn't go into detail about how to setup openweb-ui, but there is documentation for the on the project's site.

https://blue42.net/linux-ollama-radeon-rx5500/post/

You have a typo in your ollama.service:

Environmetn="ROCR_VISIBLE_DEVICES=1"

The 't' and 'n' are transposed.

Great blog

This is what I'm using on a old-ish Dell Latitude. Everything works except the fingerprint reader, but I knew that going in and I'm ok with it.

Which makes me wonder, would docker have gained traction if they didn't offer free registry services?