Skip Navigation

Posts
73
Comments
910
Joined
3 yr. ago

  • I'm not sure the Fediverse examples are instances of "co-op governance"?

    Lemmy is a protocol where you can make suggestions and join discussions, but ultimately, it's a project under the project governance. People then create their instances, and make their own rules with who they connect with and which they don't. This is cooperation, but not governance of the network as a whole. You can scope and draw some lines and say "this collective/collection is governed by cooperating people", but in my eyes, that's not the "coop" and "workers/users own the project" kind of thing.

    It's more of a dynamic, cooperative, collaborative system of localized governance and spanning cooperation. There is some governance on protocols etc, and you can fork it and give your opinion, but you don't own it.

  • Does that mean that we need a different kind of governance, or none at all?

    Successful independent projects have some form of governance too, no?

  • I have no explanation for the March thing.

    an easter surprise? 🤔

  • Looks like StatusGator mentions "Codeberg reported an issue on their status page" multiple times, but links neither to the status page nor the reported incident? That seems… lacking.

  • https://status.codeberg.org/status/codeberg

    Performance degradation for unauthenticated traffic

    We're facing severe traffic spikes for unauthenticated traffic, impacting performance and availability. Our primary goal is to avoid interruptions for authenticated users of Codeberg.org.

    Unrelated, the Mastodon instance used by the Codeberg.org status account is currently unavailable.

    Date Created: 2026-07-31 18:27:32 (16 hours ago)

    All Systems Operational

  • Looks like the mentioned platform does not exist yet. ETA 2027.

    A new online European repair platform will help connect consumers with repairers. The platform will have sections for each member state, helping consumers find available offers and boosting visibility for repairers.

    The platform, which will be an extension of the “Your Europe” portal, should become operational in 2027.

  • Sophos VPN is a rebrand of OpenVPN. How many of those are simple branding reusing existing VPN client infrastructure?

    If it's only about branding, it's pretty obvious to me why they do it. I doubt they [all] rewrite entire clients without a need?

  • Keyboard is a central part of my workflows and input, but CLI only narrowly.

    I regularly fire up Nushell, and occasionally use specific or dedicated tools (git, edit, …), but generally, no, relatively to other usage, I wouldn't say I leverage CLI tools much, although that's subjective and relative. I wouldn't call it unusual either, though. Relatively common, actually.

    I certainly have no problem firing up a shell and using Shell, CLI, or TUI, and if a tool or util is good or important enough, I will do so and use them when I need or want to use them for (specific) things or work.

  • From the linked webpage readme:

    2.1 Classify. Each file is labelled permissive (at least one permissive license detected, no conflicting non-permissive license), no_license (no licenses detected, or only non-license legal texts such as CLAs), or non_permissive. The permissive allowlist follows the Blue Oak Council list plus licenses categorized as Permissive or Public Domain by ScanCode. Files classified as non_permissive are excluded from both released datasets.

    From https://www.bigcode-project.org/docs/about/the-stack/:

    v1.1: The three copyleft licenses (MPL/EPL/LGPL) were excluded and the list of permissive licenses extended to 193 licenses in total. The list of programming languages was increased from 30 to 358 languages. Also opt-out request submitted by 15.11.2022 were excluded from this ersion of the dataset. The resulting near-deduplicated dataset is 6TB in size.

    So MPL/EPL/LGPL are already not part of the dataset.

    So… why were they in there? Was this added for v1.1?

    "one permissive license" - So if my project includes a lib and I include the license file for that for the license notice…?

  • 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

  • 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.
  • 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?

  • It's somewhat long for two policy changes, but a very well-written, wide assessment. It lays out good reasons for the [further restricting] changes.

  • 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.

  • Programming @programming.dev

    Protecting our FLOSS commons from LLMs — Codeberg News

    blog.codeberg.org /protecting-our-floss-commons-from-llms.html
  • Where's the programming part? I would like to see the source or docs and know how it solves endless render depth without hitting number calc limits.

  • 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.

  • 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.

    😬

  • 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.

  • 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.

  • Programming @programming.dev

    Zig 2026: No-AI Policy, $670K Foundation, Left GitHub & Why Zig Isn’t 1.0 - Andrew Kelley Explains

  • GitHub @programming.dev

    GitHub Stacked PRs

    github.github.com /gh-stack/
  • Linux @programming.dev

    If You See Me Use Ubuntu (Song Parody)

  • Opensource @programming.dev

    Sniffnet [network monitoring tool written in Rust] crosses 500k downloads

    sniffnet.app /news/500k-downloads/
  • Opensource @programming.dev

    Edit 2.0 Introduces Syntax Highlighting - Small-Size TUI Text-Editor

    github.com /microsoft/edit/releases/tag/v2.0.0
  • Programming @programming.dev

    Simplest hash functions

    purplesyringa.moe /blog/simplest-hash-functions/
  • Opensource @programming.dev

    I accidentally started a green screen revolution... - Corridor Crew (YouTube, 19min) (Repo-Links in desc)

  • Programming @programming.dev

    The Scapegoat Mechanism - mmagueta

    marcosmagueta.com /blog/casus-belli-engineering/
  • Programming @programming.dev

    The lost art of XML — mmagueta

    marcosmagueta.com /blog/the-lost-art-of-xml/
  • Opensource @programming.dev

    Why users cannot create Issues directly – ghostty

    github.com /ghostty-org/ghostty/issues/3558
  • Programming @programming.dev

    Coming soon: Simpler pricing and a better experience for GitHub Actions - GitHub Changelog (Adds self-hosted runner cost)

    github.blog /changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions/
  • Programming @programming.dev

    OpenAI Demo'd Fixing Issue #2472 Live. It's Still Open Months Later.

    blog.tymscar.com /posts/openaiunmergeddemo/
  • Opensource @programming.dev

    BentoPDF includes a “dad joke” with (almost) every release

    github.com /alam00000/bentopdf/releases
  • Programming @programming.dev

    Highlights from Git 2.52 - GitHub Blog

    github.blog /open-source/git/highlights-from-git-2-52/
  • Programming @programming.dev

    Announcing .NET 10 - .NET Blog

    devblogs.microsoft.com /dotnet/announcing-dotnet-10/
  • Programming @programming.dev

    GlassWorm: First Self-Propagating Worm Using Invisible Code Hits OpenVSX Marketplace | Koi Blog

    www.koi.ai /blog/glassworm-first-self-propagating-worm-using-invisible-code-hits-openvsx-marketplace
  • VS Code @programming.dev

    GlassWorm: First Self-Propagating Worm Using Invisible Code Hits OpenVSX Marketplace | Koi Blog

    www.koi.ai /blog/glassworm-first-self-propagating-worm-using-invisible-code-hits-openvsx-marketplace
  • Programming @programming.dev

    Pijul - DVCS, based on the theory of patches, inspired by darcs

    pijul.org
  • Programming @programming.dev

    Wasm 3.0 Completed - WebAssembly

    webassembly.org /news/2025-09-17-wasm-3.0/