[–] 4 points 3 months ago

with a Markdown list with all your repositories you want removed.

The repo readme linked FAQ says

You can choose to request either (1) all repos, or (2) you can specify select repos that you own to be removed.

so "all of them" should be acceptable

  • source
  • parent
  • context
  • [–] 6 points 3 months ago*

    Noteworthy: They crawled only the default branch HEAD and inlined all source content.

    • The file contents are included inline. The decoded UTF-8 source text is embedded directly in the dataset, so it is fully self-contained — you can start training the moment the download finishes.
    • It reflects the state of GitHub in August 2025. The corpus is a direct crawl of GitHub repositories at their default-branch HEAD, capturing roughly two additional years of open-source code compared to The Stack v2.
  • source
  • [–] 20 points 3 months ago* (last edited 3 months ago) (1 child)

    We want to give developers agency over their source code by letting them decide whether or not it should be used to develop and evaluate machine learning models.

    crawled directly from GitHub and built to pre-train code LLMs with full-repository context

    Repositories that opted out are removed from the dataset before each patch release.

    "agency"

    Which AI company will not use v1 which has all of the data but will use later patch releases instead which have less data?

  • source
  • [–] [S] 9 points 3 months ago (1 child)

    Unfortunately, these crawlers instead try to read every single page from Codeberg, no matter if it makes sense. This includes all the different issue filter variants, Git history, as well as the actual files at any point in Git history - even if they are still equal.

    I'm surprised they don't lock some things behind account logins. Is it that hard to decide what would be acceptable to no longer serve without an account?

    Does the full commit and change history have to be available without an account, under these circumstances? If we think about what would be minimally enough:

    • Current branch head tree
    • Tag trees (you can link to release source state and [potentially/manually] compare between releases)

    Not having a change log history nor code change diff seems like a big loss to me, but you have to draw the line somewhere, and that seems acceptable to me.

    To me, Codeberg is in a better position to do so than smaller instances. I already have an account because it has many [relevant/significant] projects, is a home of public good, and is under an appropriate org.

  • source
  • [–] 4 points 4 months ago

    They share some real-world/practical example limitations and how they use AI as an accessibility tool.

    The uncomfortable truth is that if we'd done a better job of making the web accessible, if we'd let the web realise its accessibility potential, far fewer people would be turning to AI to compensate now.

    If you want to resist AI, make accessibility part of everything you do, every decision you make, every product you design and build. Remove the need for people to use AI to compensate, and remember, accessibility is resistance.

  • source
  • [–] 3 points 4 months ago (2 children)

    When did you first hear of Godot? *

    I love required questions with very specific answers I don't know how to answer. I guess I'm out.

    Earlier I did the StackOverflow survey and everything was optional. I liked that.

  • source
  • [–] 10 points 4 months ago

    Granular repository watch settings

    Ooh, very nice. Watching for release notifications is something I use excessively on GitHub. Looking forward to being able to use that on Codeberg.

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

    Forgejo v13.0 added the capability to remove EXIF metadata from images that are uploaded in a user’s avatar. Unfortunately, a licensing mistake was made and Forgejo relied on an AGPL-licensed library to accomplish this work. While other options are being pursued, Forgejo has removed this capability to bring us into license compliance.

    😬

  • source
  • [–] 13 points 4 months ago*

    Yeah. Building something and solving your gaps yourself is much better for learning than following a walkthrough.

    A walkthrough can be effective onboarding if you're already familiar with the concepts. Otherwise, it takes the right kind of learning mindset to effectively take away results; not just following along, but internalizing the concepts and constructs.

    For beginners, both the language and the concepts are new. Repetition/Multiple occasions help with internalizing.

  • source
  • parent
  • context
  • [–] 2 points 4 months ago

    The only way this assessment makes sense is if you're looking at specific industries or something. Meta can't compare to Microsoft in other areas. We have to use Teams and Office because all our customers do. Enterprise/Companies are integrated and bound to their tooling and user and system management.

    Meta is localized. I don't see it even nearly as prevalent as Microsoft is.

  • source
  • parent
  • context
  • view more: ‹ prev next ›