[–] 7 points 9 months ago*

relevant, from a PR comment

On Monday January 26, 2026, I intend to merge this pull-request and post an explainer blog post detailing some further reasoning and details behind this move. The change, the end of the bounty, is officially set for January 31 but I am certain it will take some days to "take effect" and by merging the update a few days early I don't think we actually hurt anyone.

  • source
  • [–] 30 points 9 months ago* (last edited 9 months ago)

    His comments came as cURL users complained that the move was treating the symptoms caused by AI slop without addressing the cause. The users said they were concerned the move would eliminate a key means for ensuring and maintaining the security of the tool.

    A single user commented, and they responded. “users complained” and "the users" is wrong. implying something different.

    “users complained” feels like a misrepresentation to me as well, at least how I read and understand "complained". The user wrote “As a security researcher, this is honestly painful to see, but also completely understandable.” Is it complaining if they understand the act and change?

    In a separate post on Thursday, Stenberg wrote: “We will ban you and ridicule you in public if you waste our time on crap reports.”

    The linked separate post is a /.well-known/security.txt file. It's not really a “separate post”. And I don't see where they got the date from. Maybe from whatever linked to that in the first place.

    An update to cURL’s official GitHub account made the termination, which takes effect at the end of this month, official.

    Isn't that from the merge request, which is not merged yet? It's definitely not in the main branch. Current MR state is something different. The MR discussion clearly states that they will merge on 26th - no early.

    “an update to the official GitHub account” makes no sense to me in the first place, when it's a file in a repo, not even the account.


    At first, I only wanted to point out one thing. Now this whole article feels like AI slop. Dunno how warranted that feeling/assessment is. Is it sloppy reporting? Am I, as a reader, the problem?

    /edit: The bleeping computer article posted in the community is much better/consistent/coherent. Of course, this one was earlier and already has traction.

  • source
  • [–] 1 point 10 months ago (1 child)

    If you want your organization to use your current username, you’ll need to rename your personal account first

    Is it possible to automate observing user renames and then create new accounts effectively blocking them?

  • source
  • [–] 5 points 10 months ago (3 children)

    After the first half, content repetition sets in, making me wonder about degree of LLM. I feel like at the end I read two things in particular three times.

    Either way, The first half or third was interesting and valuable.

  • source
  • [–] 4 points 10 months ago (1 child)

    They say they want to distance themselves from Microsoft. VSCodium is a stripped/forked VSCode, I have to assume that's why they want to evade it. Theia is a separate, independent project that adds VSCode-plugin-compatible APIs.

  • source
  • parent
  • context
  • [–] 1 point 10 months ago

    I used GitGitGadget to make all of my contributions. This meant that I could make a GitHub pull request (a workflow I’m comfortable with) and GitGitGadget would convert my PRs into the system the Git developers use (emails with patches attached). GitGitGadget worked great and I was very grateful to not have to learn how to send patches by email with Git.

    Interesting

    https://gitgitgadget.github.io/

  • source
  • view more: ‹ prev next ›