oh lawd he comin

It depends on the subject area and your workflow. I am not an AI fanboy by any stretch of the imagination, but I have found the chatbot interface to be a better substitute for the “search for how to do X with library/language Y” loop. Even though it’s wrong a lot, it gives me a better starting place faster than reading through years-old SO posts. Being able to talk to your search interface is great.

The agentic stuff is also really good when the subject is something that has been done a million times over. Most web UI areas are so well trodden that JS devs have already invented a thousand frameworks to do it. I’m not a UI dev, so being able to give the agent a prompt like, “make a configuration UI with a sidebar that uses the graphql API specified here” is quite nice.

AI is trash at anything it hasn’t been trained on in my experience though. Do anything niche or domain-specific, and it feels like flipping a coin with a bash script. It just throws shit at the wall and runs tests until the tests pass (or it sneakily changes the tests because the error stacktrace repeatedly indicates the same test line as the problem).

I don’t think you can advocate for anything even remotely on the “right” in political discussions anymore unless you mean MAGA. That well is so poisoned at this point that everyone is going to assume you’re a MAGA troll wearing a mask the second you voice any right-leaning opinion.

It’s pretty unfortunate. There are plenty of “live and let live” types in the US that identify informally as libertarians and would make great allies.

No, the drop safety thing was “fixed” a while back. This is about a class action suit due to the reports of uncommanded discharges in holsters.

Thanks for sharing. That GAO report is pretty old, and seems to indicate potential issues with the first gen M9s. Not sure how much of that is still relevant today, I’m pretty sure my M9 was made after that report came out.

The CNA study is more interesting and relevant but kinda hard to interpret. There’s a lot of externalities in there, apparently only 64% of soldiers were issued cleaning kits with their weapons, and 23% used nonstandard lubricant. The second one is interesting because later on the study found that those using nonstandard lube were 21x more likely to experience malfunctions. I honestly wonder if “nonstandard” lube was KY jelly for a lot of those guys; Army grunts are pretty famously stupid when it comes to gun maintenance.

Don’t know that there’s enough here to change my mind on reliability. Clearly the M9 was the least satisfactory part of their kit, but I’m not sure that it was due to a problem with the gun itself. Double-action is a legit downside, so I can’t fault them for being unhappy with it; if they want to be able to draw and fire with a quick trigger pull, the M9 ain’t it.

I’ve never heard that about the M9. I had one of the original M9s (think it was late 80s/early 90s) for years with probably 10k+ rounds through it and never had an issue. Anecdotal, I know, but given I’ve never heard of widespread issues with the gun I’m finding this claim hard to believe.

Do you have a link to a study/article about this? Curious if there’s something I should be on the lookout for, as I am quite partial to that particular design.

100%. Sig’s handling of this is, without a doubt, going to be a landmark case study in how not to handle public relations. People getting communications degrees 50 years from now are going to read about it.

Brother, what Lemmy instance do you think this community is on? You aren’t going to get a good discussion with this topic here.

It’s around 7:30, he measures from the at-rest position to the wall. The screw is later put in to “barely press” into the wall. Definitely not very scientific, but I get what condition he’s trying to simulate. The take-up does nothing, but when you hit the wall you are starting to put pressure on the seer. The implication here is any pressure on the seer combined with impacts to the slide can cause a discharge.

I expect there to be a flurry of videos trying to reproduce this on various 320 models. Should be an interesting week, even if the end result is bad news for Sig and 320 owners.

It isn’t at rest, the screw basically holds the trigger at the wall. I think he says that near the beginning of the video. All the take-up is out, so this is simulating what happens if your trigger has some pressure on it, but not enough to push it past the break.

Some pressure can be put on the trigger easily in some holsters, which is why I never felt comfortable carrying the thing. Even if I knew for sure my 320 didn’t have this problem, it was still too much of a risk to me that if something snagged the trigger there’d be no external safety to make sure it couldn’t discharge.

The M17/M18 does have such a safety, but my understanding is that the safety is just on the trigger itself. If this problem is real, it’s possible that the same thing could happen anyway; the striker is always in tension and if the safety was a bit out of spec then the trigger could be put into the same position as shown in the video.

The video is not terribly scientific, but hopefully some of the other gun YouTubers will try to corroborate it as well and more data will come out. MoistCr1TiKaL made a video about it a few hours ago, so this is officially a mainstream issue that gets clicks. Just from the collections on the dozen or so gun channels I’m aware of, there’s a sample size of many dozens of 320s to test with.

Employees have to pay for basically everything in the US, so salaries have to be a lot higher here. School, childcare, healthcare, retirement, you name it. Also, all those things are more expensive here because they’re provided by companies that need to make a profit. It sucks.

Listed salaries are almost always what the employee pays, not what it costs the company. In the US, this includes the payroll tax, and cost of “benefits,” like healthcare and unemployment insurance, and is referred to as the burdened rate. This is separate from the income tax the employee has to pay to the government, mind you.

The burdened rate for most employees at the companies I’ve worked for in the US is like 20-50% higher than the salary paid. Not sure exactly how it works in France, but I do know there’s a pretty complex payroll tax companies have to pay. I think it’s something like 40% at the salary you quoted.

This is not snark, it’s genuine concern: are you doing research by asking AI bots questions? If so, for the love of God please stop, you’re ruining your brain. This information is freely available from any search engine if you use the date feature. I used Kagi to find these in like, 5 minutes:

https://www.forbes.com/sites/petersuciu/2024/10/02/iranian-media-claims-israeli-f-35-fighters-destroyed-in-missile-strike/

https://www.tehrantimes.com/news/504777/Nearly-20-Israeli-fighter-jets-destroyed-during-Iran-s-October

Not sure that’s a credible source. Didn’t Iranian media claim they destroyed dozens of F-35s in missile strikes of Israeli airfields last October and then it turned out to be completely fake?

I’m not sure if you know this, but…that doesn’t fix most of the security issues in the linked list. All the reverse proxy does is handle hostname resolution and TLS termination (if you are using TLS). If the application being proxies still has an unauthenticated API, anyone can access it. If there’s an RCE vulnerability in any of them, you might get hacked.

I run Jellyfin publicly, but I do it behind a separate, locked-down reverse proxy (e.g., it explicitly hangs up any request for a Host header other than Jellyfin’s), in a kubernetes cluster, and I keep its pod isolated in its own namespace with restricted access to everything local except to my library via read-only NFS volumes hosted on a separate TrueNAS box. If there is any hack, all they get access to is a container that can read my media files. Even that kind of bothers me, honestly.

The overwhelming majority of Jellyfin users do not take precautions like this and are likely pretty vulnerable. Plex has a security team to address vulnerabilities when they happen, so those users would likely be a lot safer. I appreciate the love for FOSS on Lemmy, but it is scary how little most folks here acknowledge the tradeoffs they are making.

All I can say is that is not at all like my experience with Jellyfin. Every person I’ve ever shared it with wanted to go back to Plex. Most complaints had to do with the jankiness of the various apps. Lots of issues with the UIs acting funny, a few connection drops, and some settings not getting respected. I do also recall an episode of Severance that would not stream in the correct color space in Jellyfin but worked perfectly in Plex.

Yeah, I’m not interested in setting all that up and maintaining it for every user I share with. For myself, this is exactly how I access Jellyfin remotely, but I am not explaining to my remote family members how to set up a VPN on their TV.

If you want to be on the hook for all IT requests from folks you share with, this is a fine approach. There are people out there who honestly don’t have a problem with that and more power to them. I doubt they are the majority, and a lot of selfhosters completely ignore this aspect of software. There is a reason non-free services exist beyond just “capitalism bad.” I mean, capitalism indeed bad, but your time is worth something.

This will affect any server that does not already have a Plex Pass/ Lifetime Plex Pass. If your server does not have one, your remote users will have to pay. The service Plex provides is still worth it though, it largely just works on dozens of platforms and that shit isn’t free to make.

Sharing a Jellyfin server with others remotely is still a lot more complicated than it needs to be to compete (no, it’s not as simple as opening a port, and if you think so then you’re either lucky or you aren’t sharing with lots of folks). I run both and I would never try to share Jellyfin with non-technical people. Honestly, I wish Jellyfin would start offering an optional paid relay service to fund their development. They could use the revenue to improve their app ecosystem and still produce mostly open-source software. Homeassistant does this with Nabu Casa and it’s great!

That being said, the new Plex Android app kinda sucks ass. If there was anything that would make me switch it wouldn’t be having to pay for software, or services it’d be a garbage experience on my most common platform.

Normally, I’d not be so blunt about this, so apologies but: you’re wrong. The majority of Americans picked fascism in 2024 knowing exactly what they’d get. Nothing anyone did to him mattered before he was given a clear mandate to burn everything down, there’s no reason to believe it will matter now.

The Democrats need to get dirty or we are all fucked.