Noxy

any CEO advocating for it must be legally forced to cede their job to it.

confused me when I suddenly had to give Firefox this permission to access websites on my LAN

More ways to control what can access what is a welcome change for me

(I’m on GrapheneOS but yeah, Android 17 based now)

Synology Photos has served me well for years. ThiughI really would like to migrate to Immich, I’m just unsure how to do so with a >1tb photo/video library without doing it over NFS cuz I don’t want to run Immich directly on my NAS and I have an oldish work laptop that would probably crush it if it had more than a 1tb SSD, and like hell am I gonna buy a 2 or 4 tb SSD right now

the alternatives do not include a nationwide search as part of their features

that’s what palantir is for, unfortunately. I would be shocked if they didn’t already have a “solution” for this, or at least if they aren’t already working on it.

and Axon sure as shit ain’t broke, being the rebranded literal Taser company, they can afford the R&D to develop it, and will probably get free cash from the fascist government to do so in the near future anyways

Good, there’s no damn reason any of those things should exist at Rockstar. Go union!

I managed to get my immediate family all on Signal, so that’s my vote!

if I understand right, DLSS (outside frame generation, a relatively newer DLSS feature) isn’t interpolating frames, it’s upscaling frames. and its never before altered the look beyond just upscaling it.

this new shit is definitely a different direction for DLSS and it sucks and I hate it

Following the openbsd example from the original comment I replied to, it has absolutely nothing to say about what brackets mean, so this advice would not be helpful for an openbsd system: https://man.openbsd.org/man

On my personal linux system (arch derivative, by the way), it at least mentions brackets meaning optional, but only in the context of arguments:

   [-abc]             any or all arguments within [ ] are optional.

I think this would trip up some new users. The destination, with or without the username to connect as, may not seem like an “argument” to a new user since it doesn’t have a dash before it like the example does

No worries, didn’t feel demeaned but wanted to be clear that it was an attempt to try to ignore ~23 years of ssh muscle memory to try to guess what might trip up a new Linux user

Very much true in my case - I couldn’t explain what the, like… “idiomatic” meaning of those brackets is, I only guess from context and experience, and it remains a minor peeve of mine that such symbology is widely used but rarely explained

I’ve been using ssh for decades, you don’t have to explain it to me. It was a purely contrived example to simulate what I think a new user might experience if faced with that particular man page as their only documentation.

BS. I’ve been using linux for over 20 years and I still don’t know what those mean. I can only guess from context. It’s a stupid convention to just use symbols like that and never explain it.

ssh connects and logs into the specified destination, which may be specified as either [user@]hostname or a URI of the form ssh://[user@]hostname[:port]

ssh [admin@]192.168.1.1
ssh: Could not resolve hostname ]192.168.1.1: No address associated with hostname

That’s how I would interpret that part of the man page had I no familiarity with ssh. It doesn’t seem reasonable to expect the reader to know what those brackets mean.