[–] 2 points 2 weeks 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 2 weeks 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 2 weeks 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
  • [–] 7 points 3 weeks ago* (last edited 3 weeks ago)

    All 39 observed attempts to publish packages to our NuGet feeds were rejected.

    The observed attempts to access other customers' data or restricted resources were rejected. Tens of thousands of requests targeting our core systems did not result in unauthorised access.

    Did I just read about good security practices? It certainly feels like a nice change compared to catastrophic or non-transparent reports we often see from other parties.

    That they can trace, analyze, and recognize the attack activities and consequences stood out to me as well. (It's a topic/target in my work environment too.)

  • source
  • [–] 5 points 3 weeks ago

    On Tuesday, the world found out about two massive security vulnerabilities in PHP, a programming language that is used by roughly 70 percent of websites.

    Matthew Prince, the CEO of the hosting company Cloudflare, wrote that in the 10 hours before the flaws were publicly announced, “we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.”

    Surý, who lives in Czechia, does not work for the PHP Foundation. But alongside his day job as director of domain-name-system engineering at the nonprofit Internet Systems Consortium, in a volunteer capacity, he maintains and helps automate patches for the coding language. His work, with that of just a handful of others, has allowed countless websites and organizations to fix these vulnerabilities quickly. Over the past 48 hours, he’s become arguably the unsung hero of the entire internet—despite the fact that the only compensation he receives is from modest donations. “Ondřej will save the internet today,” a user in the PHP Subreddit wrote.

    I spoke with Surý today from his home about the unfolding AI-cybersecurity crisis, how the internet’s infrastructure is maintained by small crews of volunteers such as himself, and how it feels to go to bed after saving the web as we know it.

    (Bolding is mine to indicate who this is about.)

  • source
  • [–] 1 point 3 weeks ago* (last edited 3 weeks ago)

    Is it free (title claim) if I'm blocked from accessing it? I don't think so. At least not freely accessible.

    Is it free if I pay with personal data, tracking, and information about me being sold? I don't think so. (The block popover certainly doesn't give any information about their ad practices but I can only assume it'll be a big network tracking users.)

  • source
  • [–] 12 points 3 weeks ago

    Reading the tldr immediately made me think of special keywords being introduced that you wouldn't guess.

    Those in the know could then trigger the more secure mode, while everyone else wouldn't know any better.

    It could also be the language you prompt with. Make Chinese prompt results secure by default, and others not.

    The latter would be demonstrable. The prior would need discovering or leaking/whistleblowing the secret phrase before it would be demonstrable.

  • source
  • [–] 2 points 3 weeks ago*

    It's a broad topic.

    Be mindful of how you communicate. Differentiate between questions, risks, wrongs, subjective. Talk with your teammates. Establish a common understanding of deliberate word use or forms, intentions, and necessities to answer or change or not.

    Consider whether passive and non-aggressive communication is the best approach. Some people may not pick up on defensive tone and just not care. Maybe they need more direct and pushy speech and discussions where you point stuff out, including the overall approach to working together and your assumptions or expectations.

    Be mindful of sharing alternative approaches or knowledge vs not commenting to reduce own time investment and number of comments. Discuss with your team where the sweet spot is. This may change over time and is different with different people, their experience in general and in the project.

    Make it clear that the one submitting the code is the owner and person responsible. They have to take ownership.

    If necessary, establish a common understanding of where to commit time investment. Usually it's much preferable for the author to invest time into a well documented submission over a reviewer trying to understand and find things out through analysis and questions.

    Try to find a common understanding of not just the solution but what the authors understanding and intentions, what edges and alternatives did they consider, what risks or decision basis did they use.

    Establish understanding on what your role as reviewer is. Risk reduction? Common standardized solutions and code? Are you lead and give long term direction, including how things are implemented to reduce long term complexity and variance? Do you teach through reviews?

    If necessary or unclear, ask what or how deep you are being asked to review. Depending on the author expertise and trustworthyness and your load, sometimes merely approving a concept and a broad peek into the most risky parts or what you want to see the approach on may be enough. Sometimes they may be confident and just want approval on the concept, not every code change.

    Be mindful of when to not post comments but ask for a shared screen meeting and talk for them to walk you through or explain things. The author should also be mindful of when they think discussion before asynchronous written review makes sense.

    Consider whether you are always the one who should review. At all, or first. Maybe someone else can. Maybe you can do a second review pass, maybe only on remaining open questions.

  • source
  • [–] 1 point 3 weeks ago*

    who is brian hood

    Depending on the context, Brian Hood most commonly refers to one of two notable figures: […]

    It tells me about two Brian Hoods. I assume one of them is the supposed denied one?

    Or it is selective about what information it gives about them.

  • source
  • parent
  • context
  •  

    In our previous post “Reinventing how .NET Builds and Ships”, Matt covered our recent overhaul of .NET’s building and shipping processes. A key part of this multi-year effort, which we called Unified Build, is the introduction of the Virtual Monolithic Repository (VMR) that aggregates all the source code and infrastructure needed to build the .NET SDK. This article focuses on the monorepo itself: how it was created and the technical details of the two-way synchronization that keeps it alive.

     

    Users are not allowed to create Issues directly in this repository - we ask that you create a Discussion first.

    Unlike some other projects, Ghostty does not use the issue tracker for discussion or feature requests. Instead, we use GitHub discussions for that. Once a discussion reaches a point where a well-understood, actionable item is identified, it is moved to the issue tracker. This pattern makes it easier for maintainers or contributors to find issues to work on since every issue is ready to be worked on.

    This approach is based on years of experience maintaining open source projects and observing that 80-90% of what users think are bugs are either misunderstandings, environmental problems, or configuration errors by the users themselves. For what's left, the majority are often feature requests (unimplemented features) and not bugs (malfunctioning features). Of the features requests, almost all are underspecified and require more guidance by a maintainer to be worked on.

    Any Discussion which clearly identifies a problem in Ghostty and can be confirmed or reproduced will be converted to an Issue by a maintainer, so as a user finding a valid problem you don't do any extra work anyway. Thank you.

     

    On January 1, 2026, GitHub will reduce the price of GitHub-hosted runners by up to 39% depending on the machine type used. The free usage minute quotas will remain the same.

    On March 1, 2026, GitHub will introduce a new $0.002 per minute GitHub Actions cloud platform charge that will apply to self-hosted runner usage. Any usage subject to this charge will count toward the minutes included in your plan, as explained in our GitHub Actions billing documentation.

    Runner usage in public repositories will remain free. There will be no changes in price structure for GitHub Enterprise Server customers.

    We are increasing our investment into our self-hosted experience to ensure that we can provide autoscaling for scenarios beyond just Linux containers.

    Historically, self-hosted runner customers were able to leverage much of GitHub Actions’ infrastructure and services at no cost.

     

    This talk focuses on that evil little term “UX/UI,” which is responsible for so much confusion and tension in open-source projects. Not only does it unnecessarily pit programmers against designers, but it also limits our vision of what we could be doing.

    In this talk, Scott Jenson gives examples of how focusing on UX -- instead of UI -- frees us to think bigger. This is especially true for the desktop, where the user experience has so much potential to grow well beyond its current interaction models. The desktop UX is certainly not dead, and this talk suggests some future directions we could take.

    Scott Jenson has been a leader in UX design and strategic planning for over 35 years. He was the first member of Apple’s Human Interface group in the late '80s, and has since held key roles at several major tech companies. He served as Director of Product Design for Symbian in London, managed Mobile UX design at Google, and was Creative Director at frog design in San Francisco. He returned to Google to do UX research for Android and is now a UX strategist in the open-source community for Mastodon and Home Assistant.

    They present a bit of history, terminology, and current and alternative approaches to human interfaces.

     

    It is with great pleasure that we announce the new Jenkins Bug Bounty Program! The European Commission (EC OSPO) has partnered with YesWeHack to launch bug bounty programs for several open source projects. The Jenkins project was selected as a valuable asset for public administration across the European Union.

    • Initial scope: Jenkins Core and its main components, and four plugins related to security
    • Reward: Up to €5,000 for valid critical findings!
    • Platform: Jenkins Bug Bounty Program on YesWeHack
    • Funding: European Commission
     

    Let’s walk through why that history powers Visual Studio and why changing a shortcut like Ctrl+W is such a challenge.

    This is about them changing keyboard shortcuts [defaults], not the user changing their keyboard shortcuts.

    This walked you through the process we followed to map Ctrl+W to close the current tab in Visual Studio 2026. For C# profile users, we held off on this change to avoid disrupting existing workflows, especially given potential conflicts with sequenced shortcuts. If you’re using the C# profile and want Ctrl+W to close tabs, you can easily set it up yourself in the keybinding settings.

    view more: ‹ prev next ›