[–] 7 points 2 days ago

Great news, great project. Projects staying below 1.0 for a long time are always tragic. No confidence in stability, and consequences of that for users.

I don't know if they were still iterating with such big changes or feature/model support gaps? Anyway, great to see this stabilization. Always feels better to use a stable >=1.0.

  • source
  • [–] 3 points 2 days ago* (1 child)

    They embedded videos to blend-in-animation their graphs. But I have autoplay off. So all I see is grey, with no video controls until hover. Quite confusing. And so unnecessary for a blend in animation. Could have been images. Or - probably not on huggingfaces there - a simple CSS transition.

    I was confused and assumed content/embed was not loading. Even when scrolling up and down.

  • source
  • [–] 3 points 2 days ago (1 child)

    You want "the big ones" or "at least the different platforms (forge software)" or would you also want every forgejo and gitlab instance listed? Presumably, you want only with open signup?

  • source
  • [–] 1 point 2 days ago

    <meta name="color-scheme" content="dark light" /> in the <head>, then the browsers defaults already provide dark mode defaults. If you overwrite with your own color scheme, use light-dark(#fff, #000) (obviously, you can use variables too) to define a color with light and dark variants in-place.

    So, no explicit toggle. Just respect my browser/system defaults.

    (It's not really visible because of the inline code coloring, but I linked the MDN docs on both.)

  • source
  • parent
  • context
  • [–] 4 points 5 days ago

    I'm lead in my team and AI is being used to varying degrees. One colleague is a problem, but was a problem before AI as well. Me and my other three colleagues have a common understanding of you have to take ownership, understand what you're doing, and document it.

    As a reviewer, I ask for the information it lacks.

    We (our company) has another project started with "AI first" too, and now still works mainly through "document features and behavior and stuff in md files and AI generates it" - so mostly about spec writing and AI generating. I don't know how well that works, but I've heard bad more than good things (which may be common anyway) and it certainly hasn't lead to meeting timelines (now more than half a year behind the original planned release).

    Personally, I'm still skeptical about AI use, but do use it occasionally. Our project is simply too complex (and legacy and long history of changed dotnet technology as well). It's more feasible on newer projects, but Blazor isn't a straight forward framework either, mixing razor, html, css, component isolation, SAP lifecycle, render modes and whatnot.

    I haven't used AI to a degree where I feel it significantly [negatively] impacts my capabilities. Thankfully, my team hasn't pivoted into that completely, either. I see the risk and hope pushes though. The promise of AI speeding things up. The customer saying "a bit more risk is fine"; but it's on us to communicate the difference between risks (the bug fix missed one additional unknown place vs long term maintainability and its associated risks).

  • source
  •  

    For five days in March 2026, a single stolen token let one group poison five software ecosystems including a package downloaded 95 million times a month. The attack started with a misconfigured GitHub Actions workflow, and ended with backdoored code sitting inside CI/CD pipelines around the world.

    Today, two people behind this attack were arrested. TeamPCP, allegedly operated by these threat actors, started attacks in late 2025 running opportunistic cloud exploits, then pivoted in early 2026 to targeting the software supply chain itself.

    Flare’s Emerging Threats Team wanted to share examples of some of the techniques that can be used to unmask one operator behind TeamPCP, using the Flare platform to trace a single alias across the accounts, credentials, and infrastructure that connected back to a real identity. There were other independent investigations on this topic, including by Brian Krebs. Below, we walk through who TeamPCP is and share the process of deanonymizing threat actors.

     

    For five days in March 2026, a single stolen token let one group poison five software ecosystems including a package downloaded 95 million times a month. The attack started with a misconfigured GitHub Actions workflow, and ended with backdoored code sitting inside CI/CD pipelines around the world.

    Today, two people behind this attack were arrested. TeamPCP, allegedly operated by these threat actors, started attacks in late 2025 running opportunistic cloud exploits, then pivoted in early 2026 to targeting the software supply chain itself.

    Flare’s Emerging Threats Team wanted to share examples of some of the techniques that can be used to unmask one operator behind TeamPCP, using the Flare platform to trace a single alias across the accounts, credentials, and infrastructure that connected back to a real identity. There were other independent investigations on this topic, including by Brian Krebs. Below, we walk through who TeamPCP is and share the process of deanonymizing threat actors.

     

    Game trailers which take their time to show gameplay can perform way better than trailers which are cut fast and make a hard sell. See a before/after for the Sheepherds' Announce/Launch trailer to see what a difference the editing style made!

    I explain how to make a game trailer which lets the viewer see what’s special about the game and how to apply it when you edit a gameplay trailer.

     

    In Brief:

    • Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed.
    • We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects.
    • We believe that LLMs endanger the free/libre software ecosystem as a whole.

    The blog/news post then goes extensively into where Codeberg understands itself to be in the development landscape, and their voting results. They present their interpretation of the current software development and hardware landscape under the influence of LLMs, and the consequences they take. And how it changes not only development in general, but FOSS collaboration and projects specifically.

    To us, it seems ridiculous to see projects with a single developer and virtually no users consuming as much or even more resources than some of the largest community projects on Codeberg, which operate frugal with CI/CD and storage resources. We do not believe it is reasonable for Codeberg to invest our precious donation money into hosting of large ghost projects.

     

    After loading a project, Cursor attempts to find git binaries at various locations including the current workspace. By creating a repository with a planted malicious git.exe in the root, the IDE will execute it with no user interaction and no prompting of the user. This occurs repeatedly on a cadence.

     

    Andrew Kelley quit his job in 2018 to build a programming language. Eight years later, Zig powers Ghostty, TigerBeetle and Uber's cross-compilation. It's top 5 most admired on Stack Overflow. There's just one thing missing: 1.0. Andrew Kelley explains why.

    Vitaly talked to Andrew about:

    • Why Zig has no 1.0 after a decade, and why that's deliberate
    • Why Zig left GitHub
    • Why Zig banned AI from Zig
    • What makes Zig better than C (and why every other C replacement failed)
    • Andrew’s take on Open Source

    It's a long interview, but I found it very interesting and worth it.

     

    ColorSym is a free, open-source color-identification system that pairs every color with a unique, memorable symbol. When color alone isn't enough to tell things apart, the symbol does the job, so the roughly 1 in 12 men and 1 in 200 women with color vision deficiency can read your components, charts, or UI with confidence.

     

    When using Central Package Management (Directory.Packages.props holds package versions), package version declarations can remain after package references have been removed. The package versions are unused and misleading.

    dotnet nuget why can be used to get a dependency tree across projects to answer how a package comes into the dependency tree. However, the extensive tree list result for a list of version declarations is not viable to simply determine what 'is in use' and what isn't.

    I am sharing my Nushell snippet which answers the question of what is declared but not referenced:

    # List Directory.Packages.props version declarations that are in no csproj
    def "dotnet unused-dirpackprops" [] {
      let defs = open Directory.Packages.props | from xml | get content | where tag == ItemGroup | get content.attributes.Include | flatten | sort --ignore-case --natural
      let refs = ls **/*.csproj | get name | each { open | from xml | get content | select content | flatten | flatten | where tag == PackageReference | get attributes.Include } | flatten | uniq | sort --ignore-case --natural
      $defs | difference $refs
    }
    
    ❯ dotnet unused-dirpackprops
    ╭───┬─────────────────────────────────────────╮
    │ 0 │ coverlet.collector                      │
    │ 1 │ System.Net.Http                         │
    │ 2 │ System.ServiceProcess.ServiceController │
    ╰───┴─────────────────────────────────────────╯
    

    Gaps: In this simple form, only covers the standard csproj package references. Package references included during build through other target or prop files are not covered (probably irrelevant for most users).

     

    They go over how the web and frameworks decided against horizontal, apart from deliberate emphasis, they go over some desktop layout attempts, failures and successes (more of the same vs navigation), a chapter about (paper) documents as the source, and endless panes now using horizontal.

    From the description:

    Almost every screen we use is a landscape rectangle, wider than it is tall. And on almost all of them, the content moves vertically. Always down.

    This video walks through a wrong question. If mobile scrolls down, why doesn't the desktop scroll sideways?

    The question turns out to be wrong.

    Chapters

    • [00:00] Introduction
    • [01:23] The Web Could, and Doesn't
    • [03:18] The Microsoft Bet - Windows 8 "Metro"/"Modern" failure
    • [06:18] What Makes a Difference - Layouts where horizontal works
    • [09:14] Horizontal Scrolling as Emphasis
    • [10:24] When Horizontal Axis Means Something
    • [12:13] The Document Model
    • [14:06] The Potential of a Glass Plane

    References

    view more: ‹ prev next ›