Linux server admin, MySQL/TSQL database admin, Python programmer, Linux gaming enthusiast and a forever GM.

  • 17 Posts
  • 1.21K Comments
Joined 3 years ago
cake
Cake day: June 8th, 2023

help-circle






  • I think you may be misunderstanding the situation. He’s telling AI critics to stop complaining or fork. If that happens, the main branch will still have AI submissions, and the fork will be the AI-free one.

    Important to note: Torvalds is not an LLM evangelist, nor does he just accept AI slop uncritically. The official policy is that LLM written/assisted code is fine, but the quality must hit the bar expected of Linux kernel submissions, and the submitter takes full responsibility for the code correctness whether they personally wrote it or not. Just submitting LLM code with no verification or tests is a great way of getting banned from submitting pull requests and getting a very angry email from Linus.


  • The point is I don’t think LLMs normally use copyrighted code in a way that would hurt open source projects.

    I don’t know. I’m not a lawyer, and copyright for code was a hot mess even before LLMs got involved. With how many opportunistic copyright/patent trolls there are and how easily convinced judges have been in the past, it could go either way.

    Lol, so how do humans code in comparison?

    The good programmers normally code by breaking down the problem into constituent parts and logically working through the problem, step by step. What differentiates this from tokenization is that instead of just looking for code that is similar for a similar problem, programmers can usually understand the effects of each line of code, visualize what the state of each variable will be in that step (or dump out the variables to look directly if unsure), and then move on to the next step. This logical problem-solving approach is fundamentally different from a tokenization+noise looking for a similar-looking problem approach. For one thing, you can solve problems that haven’t been solved before.


  • That would rely on the contact of that user using the admin’s public key. In most systems I’ve seen that’d result in a big flashing warning that the user’s key has been changed. So, dangerous for people contacting you for the first time, much more obvious if the 2 users have been talking before that point.

    Other people have raised the much more interesting and potentially dangerous point that it’s very difficult in this context to make sure that a particular public key corresponds with a particular user. I’m way more used to sysadmin style issues where you have a small number of known keypairs, while in this context it’s a large number of mostly unknown keypairs, so you need some way of confirming that. I’m starting to understand why this is a much thornier issue than it appears on the surface.




  • As long as the admin doesn’t possess the private key, that solution still prevents the latter issue. If the admin swaps out your public key for one they control, they could technically impersonate you and read messages after the swap, but not read any messages from before. The user would be unable to use E2EE as soon as the key is swapped, so the only real issue here is impersonation.

    An admin could theoretically take over a user’s account today, so there’s not really a new vulnerability here. And with E2EE, there’d be a big clue about something funky happening with the public key changing.

    EDIT: Oh.

    These aren’t encapsulation keys (a.k.a., asymmetric or “public key encryption” keys). Encapsulation keys belong to the MLS KeyPackages, which are NOT planned to ever be logged in a key transparency system. The KeyPackages will be signed by the keypair whose public component is stored, however.

    That seems… strange? Not sure why that approach was chosen.




  • Maybe it was a mistake to try and use natural language for this kind of job, it’s too fuzzy and interpretable. Maybe we need a new language, one with a much stricter syntax and no room for interpretation. If you make it simple enough, and use some natural language for important keywords, shouldn’t be too difficult to learn.

    We could call it “language for programming” or something like that.

    Eh, who am I kidding, that’ll never catch on.




  • Here is a paper on the topic, if you’re interested.

    CO2 is an aversive stimulant to pigs, which is why they respond in these ways. CO2 irritates the mucosal lining of the trachea and nostrils, and when combined with natural bodily moisture, carbonic acid can also form on the eyes. CO2 causes acidosis (acidifying blood and tissues) and hypercapnia (excessive levels of CO2 in the blood), which creates a sense of breathlessness, hyperventilation, and “air hunger”.This is a significant animal welfare concern. Ultimately, unconsciousness is initiated by the cerebrospinal fluid of the brain becoming too acidic and the brain ceasing to function. It takes an average of 3–5 min for pigs to die within these CO2 pits.