They’re not that different any longer: https://news.ycombinator.com/item?id=36770883

I have no idea how accurate this info on FindLaw.com is, but according to it, you don’t need a lawyer in small claims court (in the US). And according to https://en.wikipedia.org/wiki/Small_claims_court there are many other countries with similar small claim courts: “Australia, Brazil, Canada, England and Wales, Hong Kong, Ireland, Israel, Greece, New Zealand, Philippines, Scotland, Singapore, South Africa, Nigeria and the United States”. I know the list of countries is not even close to covering a large amount of Steam users, but I suspect that us Europeans are covered in other ways, so there’s that.

The Wikipedia page also mentions the lawyer thing, by the way:

A usual guiding principle in these courts is that individuals ought to be able to conduct their own cases and represent themselves without a lawyer. Rules are relaxed but still apply to some degree. In some jurisdictions, corporations must still be represented by a lawyer in small-claims court.

And I don’t think you need to sue Valve in the US. I think they’re required to have legal representation in the countries in which they operate, which should enable you to sue them “locally” in many cases. Again, not an expert, so I’m making quite a few assumptions here.

Yeah, you’re right. Sorry. I’ve edited my comment to reflect that. I didn’t read OP’s image but rather the news post by Valve on Steam, but missed the part that said: “the updated SSA now provides that any disputes are to go forward in court instead of arbitration”.

it’s certainly not GOOD for Steam users to not be able to complain without lawyering up.

But doesn’t the change open up for litigation in small claims court? (Again, I’m in no way knowledgeable in US law, so I’m just asking.)

If, for example, I want to return a game in accordance with the rules and they won’t let me, I’m not gonna lawyer up and sue them from the other side of the Atlantic.

While supposedly being a lot cheaper than litigation, arbitration isn’t free either. Besides, arbitration makes it near-impossible to appeal a decision, and the outcome won’t set binding legal precedent. Furthermore, arbitration often comes with a class action waiver. Valve also removed that from the SSA.

I’m far from an expert in law, especially US law, but as I understand it, arbitration is still available (if both parties agree, I assume), it’s just not a requirement anymore [edit: nevermind, I didn’t understand it]. I’m sure they’re making this move because it somehow benefits them, but it still seems to me that consumers are getting more options [edit: they’re not] which is usually a good thing.

but chose bash because it made the most sense, that bash is shipped with most linux distros out of the box and one does not have to install another interpreter/compiler for another language.

Last time I checked (because I was writing Bash scripts based on the same assumption), Python was actually present on more Linux systems out of the box than Bash.

Enterprise licensing for self-hosted setups is priced per chunk of 64 GB of RAM in your cluster. I.e. if you run Elastic on 2 machines of 32 GB RAM each, you pay for 1 node. It sounds like there may have been some poor communication going on, because they definitely don’t base the pricing for self-hosted setups on the number of employees or anything like that.

They’re also not super uptight about you going over the licensing limit for a while. We’ve been running a couple of licenses short since we scaled our cluster up a while back. Our account manager knows and doesn’t care.

I can dig both, but I much prefer precision platformers.

Odd. I replied to this comment, but now my reply is gone. Gonna try again and type up as much as I can remember.

Regardless, an algorithm expecting binary answers will obviously not take para- and extralinguistic cues into account. That extra 50 ms hesitation, the downwards glance and the voice cracking when answering “no” to “has he ever tried to strangle you before?” has a reasonable chance to get picked up by a human, but when reducing it to something that the algorithm can handle, it’s just a simple “no”. Humans are really good at picking up on such cues, even if they aren’t consciously aware that they’re doing it, but if said humans are preoccupied with staring into a computer screen in order to input the answers to the questionnaire, then there’s a much higher chance that they’ll miss them too. I honestly only see negatives here.

It’s helpful to have an algorithm that makes you ask the right questions […]

Arguably a piece of paper could solve that problem.

Seriously. 55 victims out of the 98 homicide cases sampled were deemed at negligible or low risk. If a non-algorithm-assisted department presented those numbered I’d expect them to be looking for new jobs real fast.

Your point is valid regardless but the article mentions nothing about AI. (“Algorithm” doesn’t mean “AI”.)

so it’s probably just some points assigned for the answers and maybe some simple arithmetic.

Why yes, that’s all that machine learning is, a bunch of statistics :)

I know, but that’s not what I meant. I mean literally something as simple and mundane as assigning points per answer and evaluating the final score:

// Pseudo code
risk = 0
if (Q1 == true) {
    risk += 20
}
if (Q2 == true) {
    risk += 10
}
// etc...
// Maybe throw in a bit of
if (Q28 == true) {
    if (Q22 == true and Q23 == true) {
        risk *= 1.5
    } else {
        risk += 10
    }
}

// And finally, evaluate the risk:
if (risk < 10) {
    return "negligible"
} else if (risk >= 10 and risk < 40) {
    return "low risk"
}
// etc... You get the picture.

And yes, I know I can just write if (Q1) {, but I wanted to make it a bit more accessible for non-programmers.

The article gives absolutely no reason for us to assume it’s anything more than that, and I apparently missed the part of the article that mentioned that the system had been in use since 2007. I know we had machine learning too back then, but looking at the project description here: https://eucpn.org/sites/default/files/document/files/Buena practica VIOGEN_0.pdf it looks more like they looked at a bunch of cases (2159) and came up with the 35 questions and a scoring system not unlike what I just described above.

Edit: I managed to find this, which has apparently been taken down since (but thanks to archive.org it’s still available): https://web.archive.org/web/20240227072357/https://eticasfoundation.org/gender/the-external-audit-of-the-viogen-system/

VioGén’s algorithm uses classical statistical models to perform a risk evaluation based on the weighted sum of all the responses according to pre-set weights for each variable. It is designed as a recommendation system but, even though the police officers are able to increase the automatically assigned risk score, they maintain it in 95% of the cases.

… which incidentally matches what the article says (that police maintain the VioGen risk score in 95% of the cases).

The crucial point is: 8% of the decisions turn out to be wrong or misjudged.

The article says:

Yet roughly 8 percent of women who the algorithm found to be at negligible risk and 14 percent at low risk have reported being harmed again, according to Spain’s Interior Ministry, which oversees the system.

Granted, neither “negligible” or “low risk” means “no risk”, but I think 8% and 14% are far too high numbers for those categories.

Furthermore, there’s this crucial bit:

At least 247 women have also been killed by their current or former partner since 2007 after being assessed by VioGén, according to government figures. While that is a tiny fraction of gender violence cases, it points to the algorithm’s flaws. The New York Times found that in a judicial review of 98 of those homicides, 55 of the slain women were scored by VioGén as negligible or low risk for repeat abuse.

So in the 98 murders they reviewed, the algorithm put more than 50% of them at negligible or low risk for repeat abuse. That’s a fucking coin flip!

I don’t think there’s any AI involved. The article mentions nothing of the sort, it’s at least 8 17 years old (according to the article) and the input is 35 yes/no questions, so it’s probably just some points assigned for the answers and maybe some simple arithmetic.

Edit: Upon a closer read I discovered the algorithm was much older than I first thought.

The article mentions that one woman (Stefany González Escarraman) went for a restraining order the day after the system deemed her at “low risk” and the judge denied it referring to the VioGen score.

One was Stefany González Escarraman, a 26-year-old living near Seville. In 2016, she went to the police after her husband punched her in the face and choked her. He threw objects at her, including a kitchen ladle that hit their 3-year-old child. After police interviewed Ms. Escarraman for about five hours, VioGén determined she had a negligible risk of being abused again.

The next day, Ms. Escarraman, who had a swollen black eye, went to court for a restraining order against her husband. Judges can serve as a check on the VioGén system, with the ability to intervene in cases and provide protective measures. In Ms. Escarraman’s case, the judge denied a restraining order, citing VioGén’s risk score and her husband’s lack of criminal history.

About a month later, Ms. Escarraman was stabbed by her husband multiple times in the heart in front of their children.

It also says:

Spanish police are trained to overrule VioGén’s recommendations depending on the evidence, but accept the risk scores about 95 percent of the time, officials said. Judges can also use the results when considering requests for restraining orders and other protective measures.

You could argue that the problem isn’t so much the algorithm itself as it is the level of reliance upon it. The algorithm isn’t unproblematic though. The fact that it just spits out a simple score: “negligible”, “low”, “medium”, “high”, “extreme” is, IMO, an indicator that someone’s trying to conflate far too many factors into a single dimension. I have a really hard time believing that anyone knowledgeable in criminal psychology and/or domestic abuse would agree that 35 yes or no questions would be anywhere near sufficient to evaluate the risk of repeated abuse. (I know nothing about domestic abuse or criminal psychology, so I could be completely wrong.)

Apart from that, I also find this highly problematic:

[The] victims interviewed by The Times rarely knew about the role the algorithm played in their cases. The government also has not released comprehensive data about the system’s effectiveness and has refused to make the algorithm available for outside audit.

I read every single word of it, twice, and I was laughing all the way through. I’m sorry you don’t like it, but it seems strange that you immediately assume that I haven’t read it just because I don’t agree with you.

This is such a fun and insightful piece. Unfortunately, the people who really need to read it never will.

I get notifications for calls (obviously), SMS messages (of which I receive an average of 1 per month) and IMs from my immediate family. Everything else I check up on when I actually feel like I have the time for it. This has dramatically reduced the number of emails and other things I forget to reply to/act on, because I see them when I want to and when I have the time to actually deal with them; not when some random notification pops up when I’m doing something else, gets half-noticed and swiped away because I’ll deal with it later.

Cloud Saves may be difficult to deal with, depending on what games you play.

The headline is supposedly CISA urging users to either update or delete Chrome — it’s not Chrome/Google itself. However, I’m having trouble finding the actual CISA alert. It’s not linked in the article as far as I can tell.

Fair enough, and thanks for the offer. I found a demo on YouTube. It does indeed look a lot more reasonable than having an LLM actually write the code.

I’m one of the people that don’t use IntelliSense, so it’s probably not for me, but I can definitely see why people find that particular implementation useful. Thanks for catching and correcting my misunderstanding. :)

I’m closing in on 30 years too, started just around '95, and I have yet to see an LLM spit out anything useful that I would actually feel comfortable committing to a project. Usually you end up having to spend as much time—if not more—double-checking and correcting the LLM’s output as you would writing the code yourself. (Full disclosure: I haven’t tried Copilot, so it’s possible that it’s different from Bard/Gemini, ChatGPT and what-have-you, but I’d be surprised if it was that different.)

Here’s a good example of how an LLM doesn’t really understand code in context and thus finds a “bug” that’s literally mitigated in the line before the one where it spots the potential bug: https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-for-intelligence/ (see “Exhibit B”, which links to: https://hackerone.com/reports/2298307, which is the actual HackerOne report).

LLMs don’t understand code. It’s literally your “helpful”, non-programmer friend—on stereoids—cobbling together bits and pieces from searches on SO, Reddit, DevShed, etc. and hoping the answer will make you impressed with him. Reading the study from TFA (https://dl.acm.org/doi/pdf/10.1145/3613904.3642596, §§5.1-5.2 in particular) only cements this position further for me.

And that’s not even touching upon the other issues (like copyright, licensing, etc.) with LLM-generated code that led to NetBSD simply forbidding it in their commit guidelines: https://mastodon.sdf.org/@netbsd/112446618914747900

Edit: Spelling