[–] 14 points 1 week ago

It would be interesting to see whether the BSD community finds a way to keep working with Asahi under the new terms.

They could go GPL too. :)

Asahi dual-licensing would be difficult, because then it'd be out there as MIT or BSD, which they don't want. The BSD using custom-licensed parts - the BSD projects probably don't want that.

  • source
  • [–] 9 points 1 week ago (6 children)

    I am not entirely sure why the GPLv2 license wouldn’t work for the BSDs,

    The GPL is a copyleft license. Derivative and combined works must be published under the same license.

    You can use BSD with GPL and then publish as GPL, but you can not publish as BSD.

  • source
  • parent
  • context
  • [–] 10 points 1 week ago

    "Sad to see Asahi out there burning bridges for no reason.. relicensing m1n1 and drivers under GPL2-or-later, seemingly without the consent of all prior contributors, under the guise of "defending against AI bad actors", seems entirely disingenuous and misguided."

    "no reason" but there's reasons anyway and those are "entirely disingenuous and misguided"

    Too bad [their] twitter posts don't go into actual arguments. Why is it supposedly disingenuous? Why misguided? Are there better alternatives? Probably not.

  • source
  • [–] 6 points 1 week ago* (7 children)

    If you can compare the code and it matches you probably have a good case if the AI user can't demonstrate it's not coming from you.

    There's different kinds of datasets. Some respect, select and disclose licenses, others do not.

    Some model trainers use any data they can, others are selective on what they train on.

    It can also be a decision on principle rather than current or future enforcability. If you say "don't copy this" and someone blatantly does, the morality is clearer than if you didn't specifically say that.

    There's also a question of how court rulings and law may change the situation of enforcability and usage/ignorance risk.

    MIT requires attribution too. GPL is, at the very least, a stronger statement of intention and demand. It can also be seen as protest or indication of a broader move of corporate AI exploitation leading to damage to the whole FOSS ecosystem, with additional restrictions being applied. Corps that would use AI now can't use the MIT product anymore like before.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (1 child)

    When I see word matching like this, in the context of AI, I still fear it's embedded in text prompt interfaces, meaning it can be evaded. (D E L E T E instead of delete etc)

    It also doesn't tell me much about the wider risks and gaps of the connected system architecture - which, to be fair, I haven't inspected or analyzed, so I don't know one way or the other. One guard may be better than none, but doesn't define or fully describe overall/system risk.

    Naturally, I'm more risk-averse and skeptical than many other people. I guess the original commenter is, too. :)

  • source
  • parent
  • context
  • [–] 6 points 1 week ago* (last edited 1 week ago)

    Quoting here for full context/content and archiving:

    Hello all,

    Thank you all for the vocal and clear feedback. We intended this change to simplify the setup for developers who use agents to build APIs with coding agents as we see many people struggling in wiring these up. Installing skills for coding agents is a new way of working with Postman and we thought that the in-product and website messaging conveys the intent.

    Based on the feedback from the community, we understand this wasn’t the case so we will be re-designing the experience with the right level of control.

    In the meantime, we are reverting this change.

    Notably, early earlier comments

    • provided proof that information on the website about the cli being included was added later than the issue report
    • one comment said they received this stuff as an update

    So the "in product and website messaging" seems like bullshit/lies evading accountability, attempting to change facts.

    The supposed goal of "simplify setup for developers who use agents" leading to changes on existing workflows and setups for people without explicit consent, confirmation, or information - questionable at best.

    Seems pretty clearly like malware/malware behavior.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago

    voxl was built for things like software factories that use headless VMs and sandboxes (CI, computer-use agents), usually on Xvfb with no GPU. It streams them to a plain browser tab over one WebSocket and has APIs for agents.

    How is it different from RustDesk? RustDesk is an open-source alternative to TeamViewer and AnyDesk, for reaching your own computers or helping someone with theirs: you install its app on both ends, desktop or phone, and the two find each other through an ID server, then connect directly or through a relay. For that it's the better fit, and it also shares Wayland desktops (experimentally) and Android phones, which voxl doesn't. voxl is for desktops on servers, VMs and sandboxes: it's one process that serves its own page, so there's nothing to install on the viewing side and no ID or relay server to run. The stream goes wherever a URL does, can be embedded in another page and comes with the APIs agents use. RustDesk has a web client too, but it still goes through the ID and relay servers, and the self-hosted one comes with RustDesk Server Pro.

  • source
  • [–] 3 points 1 week ago

    This is about GitHub, not Git, so seems better fit to !github@programming.dev

    Resolved
    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
    Posted 6 hours ago. Nov 04, 2026 - 11:50 UTC

  • source
  •  

    GitHub issue [COMPROMISED] v2.6 Linux Ubuntu and AppImage release assets have been replaced (SOLVED, now restored) #1911

    rentry doc (dunno publisher)

    It has come to our attention that from 6th May to today (12th May) the AppImage and Ubuntu zip assets of Cemu 2.6 on our github were compromised by a pro-Russian threat actor.
    If you are a Windows or MacOS user you are not affected. If you are a flatpak user you are also not affected.

    This means that downstream projects like EmuDeck, which downloads and installs Cemu directly from GitHub Releases was also affected.

     

    s&box, from the creator of the popular Source Engine sandbox Garry's Mod, released three days ago. s&box is based on the Source 2 engine, and not only a sandbox but a game development and publishing platform, including publishing on Steam.

    The news post one day after release openly covers the mixed ratings, public finances, doubling their play fund that pays creators, and public roadmap.

    I was surprised to see they openly and transparently publish day-by-day finances.

    The public performance stats are interesting too.

    Refreshing. I wish more publishers would do these kinds of things with deliberate open communication and transparency.

    Their metrics pages:

     

    Syntax Highlighting

    Edit v2 adds the Lightweight Syntax Highlighter. It has a ~40kB footprint for a dozen languages plus runtime, barely grows with each language added, and runs at >100MB/s.

    The highlighter is based on a simple programming language that combines regular expressions with explicit control flow. It's designed such that the runtime can be easily ported to other languages, including JavaScript.

    From 1.2.1 to 2.0.0, the edit binary size increased from 267 to 330 kB for win exe and 217 to 300 kB for linux binary.

    What is edit? README intro:

    A simple editor for simple needs.

    This editor pays homage to the classic MS-DOS Editor, but with a modern interface and input controls similar to VS Code. The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.

     

    Corridor Digital released an open-source greenscreen keyer/extractor, powered by AI, usable on consumer GPUs.

    The video covers what happened after their initial release, community and professional responses, interviews with professionals about what can be improved, and finally a practical test/example in Davinci (Video Editor).

     

    The Ergonomic, Safe and Familiar Evolution of C

    C3 is a programming language that builds on the syntax and semantics of the C language, with the goal of evolving it while still retaining familiarity for C programmers.

    Thanks to full ABI compatibility with C, it's possible to mix C and C3 in the same project with no effort. As a demonstration, vkQuake was compiled with a small portion of the code converted to C3 and compiled with the c3c compiler.

    A simple and straightforward module system that doesn't get in the way, with defaults that makes sense.

     

    EYG's type system builds upon a proven mathematical foundation by using row typing.

    EYG programs are all independent of the machine they run on. Any interaction with the world outside your program is accomplished via an effect.

    Any effect can be intercepted using a handler. This allows the response from the outside world to be replaced.

    Other languages have the possiblity of closure serialisation, but EYG's runtime is designed to make them efficient.

    Hot code reloading – If you change the code the behaviour will update immediatly if safe.

    EYG has a prototyped strongly typed shell environment.

    EYG is built to support multiple runtimes. […] In the future EYG will be available in many more places, e.g. arduino, CLI's and IPaaS. EYG makes this easy by having a carefully designed minimal AST.

    Code example (from landing page):

    let initial = 10
    let handle = (state, message) -> !int_add(state, 1)
    let render = (count) -> {
      let count = !int_to_string(count)
      !string_append("the total is ", count)
    }
    {render: render, handle: handle, init: initial}
    

    GitHub Repository, Apache 2.0

    view more: ‹ prev next ›