cultural reviewer and dabbler in stylistic premonitions

  • 991 Posts
  • 1.68K Comments
Joined 5 years ago
cake
Cake day: January 17th, 2022

help-circle

















  • As you can see, it says nothing about researching, troubleshooting, reverse-engineering, etc. As long as you write and understand the code yourself AI is allowed for everything else. As long as you’re not using generative AI it’s fine.

    I’m not sure if you’re joking or legitimately confused, but, assuming the latter, fyi the “AI” that people use for “researching, troubleshooting, reverse-engineering, etc” is part of what is called “generative AI”. Given this, it’s not much a stretch to read it as saying that even posting in Nura forums about the existence of @sv1sjp@lemmy.world’s github repo would actually be a violation of Nura’s policy (as of today; I expect it will evolve in the not-too-distant future).




  • Nura will not accept generated patches, by the way.

    If you click OP’s github link and scroll down you’ll find this section which acknowledges that: https://github.com/sv1sjp/mi-max2-oxygen-msm8953-nura-drivers#about-ai-assistance-and-contributing-upstream

    The drivers, patches, scripts and write-ups here were produced in collaboration with an AI assistant and tested on a real Mi Max 2 (oxygen).

    The Nura project does not accept LLM-generated contributions. One of its maintainers explains the reasons in this post: the social and environmental cost of these models, and the risk that people use them to produce private knowledge instead of joining and strengthening the community whose work the models learned from. We respect that decision. So:

    • This repository is not a contribution to Nura or pmaports, and its code should not be submitted there as it is.
    • It is public documentation, not private notes. The reusable part is the knowledge: how the hardware is wired, register addresses and meanings, root causes, what was tried and ruled out, and how to test safely. These are facts anyone can check on their own device. It can save time for anyone who wants to understand what works and what does not, and then write their own code to submit upstream.
    • If you want to get this into Nura or upstream, learn from it, verify it on your hardware and write your own implementation, following the rules of the project you contribute to (Nura, the Linux kernel and libcamera each have their own contribution policies).
    • Please engage with the community. The Nura wiki, the msm8953-mainline project and the people credited below did the groundwork this builds on.

    @OP (@sv1sjp@lemmy.world) what isn’t clear to me is why you don’t try to upstream the kernel parts, since Linux is accepting LLM-assisted contributions (as is Nura actually, just only indirectly after their upstreams like Linux accept them).









  • Arthur Besse@lemmy.mlOPtolinuxmemes@lemmy.world•Several vulnerabilities
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    8 days ago

    I believe comma is more widespread per country

    it looks like you might be right… I’m surprised to learn that https://en.wikipedia.org/wiki/Decimal_separator#Conventions_worldwide lists 83 countries who use comma as decimal separator, and only 59 who use dot (and presumably the thousands separator is usually the opposite of the decimal separator). However there are enough countries which aren’t on either list that it isn’t entirely clear from that page which convention is actually used in more countries.

    Also, it’s much more complicated than the . vs , binary… among other oddities:

    • Historically, in Germany and Austria, thousands separators were occasionally denoted by alternating uses of commas and points, e.g. “1.234,567.890,12” (or “1.234,567.890·12” in Austria-Hungary and Austria prior to 1938) for “eine Milliarde 234 Millionen …”, but this is not seen today and contemporary German readers would require an explanation to understand it.
    • In Switzerland, there are two styles. Currency values use an apostrophe (') as a thousands separator along with a dot (.) as the decimal separator, like “1’234’567.89”. For other values, the SI-style “1 234 567,89” is used, with a comma (,) as the decimal separator. The apostrophe is also the most common thousands separator for non-currency values, like “1’234’567,89”.






  • But still listing year’s old vulnerabilities that got fixed long ago because they are still supporting ancient stuff like 5.10LTS is Debian-specific.

    The advisory this meme is about only relates to the 6.12 kernel in Debian 13 “trixie” (Debian’s current stable release), and 1,295 of these 1,313 CVEs are from 2026.

    Linux 6.12 is the SLTS (“super long-term support”) release from 2024, so the Linux Foundation’s Civil Infrastructure Platform plans to continue backporting security fixes to it until 2035.

    Debian stopped supporting Debian 11 “bullseye” (the one with a 5.10 kernel) in August, but that kernel is also an SLTS which CIP plans to support until 2031.

    So, no, continuing support for these kernels is not something Debian-specific.

    Here are the versions of linux-image-amd64 in Debian currently:

        bullseye (oldoldstable) (kernel): Linux for 64-bit PCs (meta-package)
        5.10.262-1 [security]: amd64
        bookworm (oldstable) (kernel): Linux for 64-bit PCs (meta-package)
        6.1.187-1 [security]: amd64
        bookworm-backports (kernel): Linux for 64-bit PCs (meta-package)
        6.12.95-1~bpo12+1: amd64
        trixie (stable) (kernel): Linux for 64-bit PCs (meta-package)
        6.12.111-1 [security]: amd64
        trixie-backports (kernel): Linux for 64-bit PCs (meta-package)
        7.1.13-1~bpo13+1: amd64
        forky (testing) (kernel): Linux for 64-bit PCs (meta-package)
        7.2.8-1: amd64
        sid (unstable) (kernel): Linux for 64-bit PCs (meta-package)
        7.2.8-1: amd64
    





  • Here is the Israel I support: https://youtu.be/GYr3hYjHlx8

    That is explicitly arguing for a “two-state solution” with 1967 borders. Is that really what you think can or should happen?

    Even if you do believe that having a colonial European ethnostate there is somehow a good idea if it was just limited to those borders, nobody in Israeli politics even pretends to be open to such a thing anymore so that idea is moot.

    The Israel you say that you support is a wholly imaginary one, while the one that exists is continuing to commit genocide every day.

    In a two state solution Israel would still be ~73% ethnically jewish

    Are you sure about that? See https://en.wikipedia.org/wiki/Demographics_of_Israel#Definitions : among other things, the Israel Central Bureau of Statistics’ definition of “Population of Israel” includes Israelis (and does not include non-Israeli-citizen Palestinians) in “Area C” (which fyi icymi is on the Palestinian side of those 1967 borders you said you support).

    Germany, which does have a special responsibility.

    Doesn’t it feel awkward as a German to be advocating for an ideology (Zionism) which has the core premise that… European Jews should not live in Europe?

    But I feel that responsibility extends to a free, equal, non-apartheid Israel and not the current course.

    How much do you know about the history of Zionism? I’m guessing not enough, because it certainly never involved any idea to have a “non-apartheid Israel”. See here and here for some previous posts of mine with some links you might benefit from reading.