cultural reviewer and dabbler in stylistic premonitions

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

help-circle
  • 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 (@[email protected]) 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).



  • Why is Tuta shitty?

    here and here are two of my past comments about them with more links, but, tldr:

    • their email encryption is not interoperable
    • their encrypted email service encourages people to use a browser-based thing with an incoherent threat model: the server that the e2ee is supposed to protect you from is the same one that serves you the code each time, which means that it would trivial to subvert it on-demand for targeted users with a negligibly-small chance of anyone catching them in the act. this is an example of cryptographic snake oil.
      • note that whether (or how often) they actually do subvert their encryption for targeted users is unproven; it has been alleged in court testimony that they do, and that the entire service is in fact a honey pot for doing exactly this (see my other comments for a link about that), but the testimony is perhaps not the most credible. however, the fact that they have the ability to do this (and without much chance of being caught) is undeniable and obvious to experts while being very much not obvious to most of their users.
    • they are incessant blog spammers, writing advertorials about every vaguely-privacy-related news event to promote their products
    • and, a new item on the list (not particularly surprising, given their history of shameless hucksterism): their README claims a clear policy against AI contributions but if you click that link and scroll up and click the three dots next to the commit message (“test plugin kit and nextcloud plugin”) you can see it says “Assisted-by: Claude:claude-sonnet-5”. (This kind of dishonest bandwagon-jumping-on is very on-brand for tuta.)











  • Arthur Besse@lemmy.mlOPtolinuxmemes@lemmy.world•Several vulnerabilities
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    6 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”.











  • This might be useful for some Linux users who want (but don’t need) to run Microsoft 365 occasionally, but actually relying on this kind of hack is a terrible idea.

    Once fully implemented, this will help draw in people into Linux, as many shudder at the thought of switching to the platform because their preferred office suite doesn’t work here.

    I certainly hope this doesn’t “help draw in people into Linux”. It’s sad to think about people and organizations switching to Linux on the basis of someone misleading them into thinking that relying on this kind of thing is a good idea because when it breaks it will give them a bad impression and they’ll blame “Linux” instead of Microsoft (or Bottles or whoever told them it was a good idea).

    When the lack of a Linux version of a specific proprietary program is the blocker preventing someone from switching to Linux, relying on a workaround which remains unsupported by the proprietary/adversarial software vendor is… a recipe for a bad time.

    Even if this mostly works today, it is extremely likely that (either intentionally or inadvertently) Microsoft will break it in the future.

    So, although I do see how this can be useful for some people when/while it works, in my opinion Linux and the world at large would be better off if this software didn’t exist. I hope Microsoft breaks it sooner than later!