HN user

larntz

224 karma
Posts2
Comments99
View on HN

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

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/

I have a Pixel also, and have issues with is since the change to Gemini. It works _most_ of the time, but every once in a while it'll tell me it can't set a reminder.

I use reminders often so I suppose it is a low failure rate.

But, when they first made the change to Gemini I had to switch back for a few weeks/months before it could set reminders properly.

This may not count because it's not bash specifically or even Linux -> Linux, but one place you might run into this is running scripts between Linux and Mac/BSD.

In the past I've seen bad things happen because a script was written by someone on OSX that gets run on a Linux (GNU) based system.

Two common examples are the `sleep` and `sed` commands.

Edit: I meant to reply to the parent comment.

I've had a Pixel 2XL, Pixel 6Pro or XL (worst phone I've ever owned), and now a Pixel 8 Pro. I strongly considered moving to iPhone after my Pixel 6 experience, but decided to give it one last chance since I really prefer Android over iOS.

When I bought the 8 I got a "free" Pixel Watch 2 with the purchase. I have not owned an Apple Watch, but my wife has an older model.

They do have Fitbit integration and it works pretty well for tracking walks, jogs, and cycling. I don't use it religiously and I'm not an exercise maniac.

The watch is nice and very functional. My biggest complaint is the battery life is really bad. I have to charge it daily -- I usually only wear it during the day and charge overnight. It'll charge pretty quickly 1-2hr but I don't care enough to do it.

It looks decent and works well enough to manage notifications and take calls when I can't grab my phone. The normal functions are on par with my wife's (older model) Apple watch.

I think if I was a serious fitness and outdoor activity kind of person I would buy a Garmin. I didn't do an in-depth comparison of the watches because I only use the base functionality of fitness tracking watches (my previous smart watch was a Withings) so it's entirely possible a new Apple watch offers some great feature I'm not aware of or wouldn't personally use.

That's my personal experience with the Pixel Watch 2. It's fine for my use case, but the battery life truly is bad.

I have a pixel 6 pro and this has been my experience since they day I got it. I even had it replaced and still have to reset the cellular modem several times per week because I get the no service `!`.

Starting to believe it is a T-Mobile service issue in my area. Previously had a pixel 2 on Verizon and never had a problem. Planning to leave T-Mobile in the near future.

That has nothing to do with a majority of people imposing restrictions on themselves. 59% of people in Mississippi oppose abortion, including the majority of women. There is no need for California or New York to parachute in and tell them otherwise.

You could also argue that if 59% of people in Mississippi oppose abortion there's no need to make it illegal. No one will ever force that 59% to start having abortions.

The 59% could simply _choose_ not to have an abortion.

I think powershell is considered a scripting language. Even though the version that is included with windows is outdated you can still do quite a bit with it.

And if you can use WSL you basically have all the linux cli stuff available to you.

And if they don't blacklist all executables you can probably just download and run zipped packages -- powershell core, python, go, vim/neovim, and probably emacs can all be run as if they were portable apps and for most things you won't need admin rights.