[–] 6 points 2 days ago* (last edited 2 days 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 3 days 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 3 days 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
  • [–] 2 points 4 days ago
    • Fixed "Illegal instruction" error on certain x86_64 CPUs without SSE4.1. pr#5162
    • Fixed "lock() not supported" error on Solaris. pr#5167

    Further details are available in the changelog!

    me follows link to changelog, same two list items

  • source
  • [–] 8 points 4 days ago*

    I guess I don't know what kind of posts you mean specifically, but yes, please do.

    "Programming" can be and is typically interpreted quite broadly. It's not just "writing code" but development in general, and entails computer science.

    Looks like this programming.dev instance does not have a computer science community yet, but I would love to see one. Cross-posting is possible too.

    Tangential, there's !experienced_devs@programming.dev, but that's a different branch even if it can entail compsci.

    I would love to see more practice or science or theory or hands-on posts in this community.

    In the end, there's the option of just trying and seeing what votes and comments tell; appreciation or rejection.

  • source
  • [–] 3 points 1 week ago

    I didn't have this issue, but I will share my opinion anyway.

    What do you mean by "actual programming"? I would expect that to include not knowing stuff beforehand, to explore and prototype solutions and missing information. That's the opposite of what you seem to expect, judging from the rest of your sentence? (missing know how, unclear docs, no youtube course to follow along to)

    I learned through hacking website and related stuff in php, going into a popular C++ FOSS project, and other projects. I oriented myself through what already existed and documentation.

    The best way to learn is through self interest, through actual projects or functionality you try to implement. If it's scoped small enough, with a doable challenge, that's how you grow.

  • source
  • [–] 4 points 1 week ago*

    Implementations

    • Vervis is the reference implementation of ForgeFed. It serves as a demo platform for testing the protocol and new features.
    • Forgejo is implementing federation.
    • Pagure has an unmaintained ForgeFed plugin.

    Only one of the three weblinks works. And no, it's not the reference implementation…

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

    In this game at least, there doesn't seem ot be any items or XP.

    But I thought of this as an interesting mechanic as well when they mentioned expert period and deliberately falling to regenerate the following area. It leads to a weighing of lost time due to falling/falling back vs the chance of better alternatives.

    Even for a novice period, falling, whether deliberately or accidentally, and getting a better outcome doesn't seem like a bad thing to me. They describe how that makes progression easier by chance rather than through explicit deliberate game design with easing and fallbacks.

    Other games and game mechanics make use of risk vs potential reward too. I'm thinking of roguelites right now where you can pick something up or not or activate something at a cost. A gain may not be guaranteed. Or it offering a reroll of items on offer.

    I don't see this much different. The form is different through level generation/spooling and a different cost, but the tension or strategy mechanism is not fundamentally different in my eyes.

    I guess it comes down to what you see as "exploitation". When you see it as deliberate game design it's not really exploitation. If it's deliberately part of the influenced scoring then it's not an exploit either. Even if it's multiplayer, it can be part of game depth and game strategy.

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

    It wasn't a scarce resource before. Why is it more scarce now if we're just offloading into the cloud which makes it, supposedly, significantly more efficient? People had RAM before. Now they can't get any [for similar price].

  • source
  • [–] 2 points 1 week ago

    The advantage of decompilation as a task is that you have a reference output you can validate against.

    I would assume the approach, mechanisms, and quality of produced code is similar to general/prompted code generating.

    I assume the produced code (and its quality) depends on the compiled code; how much was stripped or obfuscated, and what runtime are we talking about which may or may not have language constructs that guide structure. With little metadata or code structure left AI would shift more into it's general patterns than if there is more metadata available that already defines structures or names.

    The thought of integrating a deterministic decompiler and then use AI to structure it and make it more readable while verifying the output remains the same seems like an interesting extension or alternative workflow and toolchain.

    I have not used these kinds of AI decompilation tools or workflows, but thinking purely from my background and general experience.

  • source
  • [–] [S] 7 points 1 week ago

    A classic that crossed my path again. It has not been shared in this community yet, so I am posting it.

    Great resource about platformer control forgiveness with visual references.

  • source
  • [–] 10 points 1 week ago (2 children)

    Now, with all that telemetry in place and a coding agent I can finally engage with production properly: not reactively when something goes wrong, but every day I can chat with the production, ask it about its concerns, about what is going on lately, if something feels wrong.

    Good luck

  • source
  • view more: next ›