Chaos Computer Club - recent events feed

Inhalte im Web verschwinden oft, Archive wie z.B. die waybackmachine sind aus dem digitalen Leben und der Wissenaggregation quasi nicht mehr wegzudenken. In diesem Talk wird es darum gehen, welche Vorteile Inhaltsaddressierung mit Blake3-Hashes bringt, und wie diese neben effektiver Deduplizierung auch dezentrale und kollaboratives Web-Archivieren vereinfacht. https://creativecommons.org/licenses/by-sa/4.0/ about this event: https://talks.mrmcd.net/2025/talk/JE9SQE/

............................................................................................................................................ https://creativecommons.org/licenses/by-sa/4.0/ about this event: https://talks.mrmcd.net/2025/talk/VHNYGD/

Präsentation der Projekte anlässich des «Jugend hackt» Events vom 5 bis 7 September 2025 im Hackerspace «Chaostreff» in Bern. Mit «Cryptic Pi» haben Elena, Lou, Max und Nic ein Tool programmiert, das dem Misstrauen gegenüber gängigen Messenger-Diensten entgegenwirkt, für alle installierbar, userfreundlich über eine Webseite eingesetzt werden kann und dann noch auch mit einem stylischen Design überzeugt. Emil, Illia, Karl, Lev und Rodion entwickeln mit «3D-Things.ch» das Projekt «Pet2Print» vom letzten Zürcher «Jugend hackt» weiter: Ob vorgefertigtes Modell, eigenes Design oder Auftragsarbeit: Dank eines neuen Webshops mit direktem Webhook zu 3D-Druckern können Kund:innen ganz einfach etwas bestellen, was ohne Lagerhaltung oder unnötige Plastikverschwendung automatisch gedruckt wird. Jona hat sich übers Wochenende stärker mit Hardware befasst und mit «Poluscanner» ein handliches Gerät für Hobby-Astronominnen und Artenschutz-Aktivisten gebaut. Das «Sensordings» sieht wie ein Fernglas aus und hilft den Betrachtenden, Quellen von Licht- und Wärmeverschmutzung zu erkennen, um sie danach beseitigen oder umgehen zu können. about this event: https://c3voc.de

Closing ceremony So long, and thanks for all the bees! about this event: https://talks.nixcon.org/nixcon-2025/talk/TEPUWK/

In this talk, we’ll share lessons from real teams using Nix in the wild: from startups building AI workflows to large orgs managing cloud infrastructure. Based on a series of interviews and stories, we’ll cover what’s working, what’s not, and how teams are making Nix part of their day-to-day development. We’ll talk about: * Why teams decide to use Nix * How they roll it out across engineering * Common challenges and how people solve them * Real-world examples of Nix in CI, AI, and production environments If you’ve ever wondered what it’s like to bring Nix to work — this talk will give you a clear, honest look. about this event: https://talks.nixcon.org/nixcon-2025/talk/XSRZH8/

Leveraging age and agenix, this project makes it easy to inject secret-containing environment variables into your flake-based devShells. It simplifies onboarding for new developers by enabling secure secret sharing, and helps make projects more self-contained by removing the need for external secrets managers. https://github.com/aciceri/agenix-shell about this event: https://talks.nixcon.org/nixcon-2025/talk/BABGSX/

I bought a receipt printer on eBay for $50, and it is one of the best purchases I've ever made. Here's how I packaged the drivers for Nix, how I legitimately use it in my every day life, and some significantly sillier Nix-related uses. about this event: https://talks.nixcon.org/nixcon-2025/talk/WNQEA8/

Running a production grade kubernetes cluster is a non trivial task. Although many commercial and non-commercial solutions are available, each comes with its own limitations. Some are primarily meant to set up a single node development cluster, others have hardly any flexibility. Here NixOS comes to the rescue, allowing us to build our cluster the way we want. However, because of the complexity of such a multi host setup, this is a bit more work than a services.kubernetes.enable = true;. We will look into the Kubernetes modules in NixOS, and how we can use them to set up a production grade cluster. For this we will consider what certificates we need, and how we can utilize a secret management solution like agenix to deploy them. We will also analyze how we can utilize Nix and the kubernetes addon-manager to configure our cluster from nix. Being able to install tools like ingress or the cert-manager is the final piece to describe the entire cluster in our nix config. about this event: https://talks.nixcon.org/nixcon-2025/talk/AZF8PR/

In this demo I will demo https://nix-ci.com/ to showcase how Nix can give us zero-config locally reproducible CI. about this event: https://talks.nixcon.org/nixcon-2025/talk/FHMLKZ/

The ssh-ng store implementation allows connecting to remote daemons over ssh. However, between server management, key exchanges, and device discovery, SSH is not the most user friendly. Unfortunately ssh-ng is also the only store implementation for active remotes built into nix. Let's ignore that fact and forward a remote daemon via P2P instead. Why would you do this? Does this work? And what can we learn from it? This talk might answer any or all of that. about this event: https://talks.nixcon.org/nixcon-2025/talk/FBZBUS/

When we think of reproducibility, we often focus on software builds, but what about the logos and visuals that represent our projects? In this talk, I’ll share how I approached logo design for the NixOS project with the same rigor we apply to software: deterministic outputs, minimal storage overhead, and fully free tooling. I’ll discuss the journey of building my own FOSS tooling to generate NixOS logos as SVGs from source code. Existing tools like Inkscape or Blender were either not parametric enough or not designed for clean, annotated vector outputs. By combining principles of CAD, typography, and color theory, I created a pipeline for reproducible, fixed-output derivations (FODs) that ensure all branding assets are versioned, verifiable, and easy to regenerate. This talk will cover: 1. The challenges of finding FOSS tools for parametric logo design. 2. Deep dives into fonts, kerning, and color spaces to build a consistent design language. 3. How I integrated FODs with verification tooling to ensure logo correctness. 4. Lessons learned about repository hygiene and why developers should expose overlays and NixOS modules rather than forcing consumers to hack around flake outputs. about this event: https://talks.nixcon.org/nixcon-2025/talk/HWQRXK/

Nix has got so many bells and whistles to meet most of the requirements, staying declarative with modularised setup to allow code reuse. However, this comes with a bit of a challenge for those who are starting the Nix journey -- it can be quite complex, or at least so does it seem. This talk focuses on some simpler approaches to use separate non-Nix files such as JSON, YAML and/or TOML for the configuration management. There are some gotchas around using file content, file as path, and potentially mixing and matching with Nix managed configs. The integration with other tools such as SOPS Nix will also be an interesting mix, where it is simpler to create a separate config file and substitute secret information with SOPS. Once you know the tools and solutions of not using Nix to get started, the Nix journey will be an easier one to get started with, and perhaps actually lead you to further Nix usage for areas where Nix language makes it easier. about this event: https://talks.nixcon.org/nixcon-2025/talk/CPF8EH/

Nix offers an unparalleled collection of readily packaged C/C++ libraries, with the added benefits of cross-compilation support and a declarative configuration language. That's why we chose it to manage third-party dependencies for our Bazel-built monorepo. This not-too-common use of Nix as a polyglot build system for external libraries and tools led us to approach Nix in a different way, both in how we think about it and how we used it. Our usage scenarios seemed rarely exercised an we found several opportunities for optimization in Nix code itself. At the core of the problem, we had 300+ packages that we needed to evaluate and build on demand. These evaluation times quickly added up, and we had to rethink the design to get some optimizations. This task set is embarrassingly parallel as each package evaluation is independent. But we realized along the way that full parallelism wasn’t the best we could do. We will explain how we leveraged nix evaluation caches (plural!), flakes, manually crafted store paths and parallel execution to reduce evaluation time from 5 minutes to 5 seconds, and bring other less quantifiable improvements. The work led to a few interesting scripts and two main PRs to nix itself (see below), one of which is already merged and released while the second is subject to discussion because of its impact on other cached operations. We will use that discussion to illustrate the tradeoffs of caching parallel evaluation. about this event: https://talks.nixcon.org/nixcon-2025/talk/FZNRLC/

NixOS is a remarkably flexible and powerful operating system, but its stability and scale can make it a challenging environment for exploring unconventional ideas. finix is an experimental Nix-based OS I built to break free from some of the constraints of upstream NixOS — a fully functional, Nix-built system that embraces rapid and bold experimentation over stability. This talk will walk through how I built finix, how I reuse much of NixOS’s scaffolding, and why I chose to try a different init system, finit. But more than the implementation details, I want to share how having a small, purpose-built codebase has created space to rapidly prototype ideas — like alternative service frameworks or minimal module sets — and see what works. finix isn’t meant to replace anything, but it could serve as a useful place to explore concepts that might one day feed back into the broader NixOS ecosystem, or at least help us think differently about how it’s designed. Beyond finix itself, I’d like to use this talk to advocate for a more diverse ecosystem of sibling projects in the Nix community — especially to better support efforts like the Nix-based BSD project. Valuable ideas don’t always need to go upstream to have an impact. Though built for experimentation, I run finix as my daily driver — and on my laptop, it’s just as smooth and capable as NixOS. That reliability makes it a practical foundation for trying out new ideas in real-world use, and it’s convinced me that we need more room for experiments like this — and more space for alternative perspectives in our community. about this event: https://talks.nixcon.org/nixcon-2025/talk/Q8VUKL/

In this most remarkable presentation, I chronicle my extensive explorations through the untamed wilderness of enterprise landscape and the experiences of applying Nix within said corporate domain. The audience shall discover the arcane rituals of cargo cults development, learn to navigate the treacherous waters of organisational silos and master the craft of sanctifying Nix usage. Like a seasoned naturalist cataloging the flora and fauna of some newly discovered archipelago, I have meticulously documented the peculiar behaviors of people unfamiliar with Nix, the resistance patterns towards making the effort to learn it, and the curious customs of playing the responsibility ping-pong. This tongue-in-cheek talk aims to share a collection of arguments and concrete actions one can make, to convince others to use Nix at their workplace. The rebuttal of frequent misconceptions (Docker makes nix not needed) included. about this event: https://talks.nixcon.org/nixcon-2025/talk/3RHWND/

Let's follow the lifecycle of a change in Nixpkgs; from opening the Pull Request until the change makes it our local /nix/store. We'll explore all the CI systems involved in this process, how they interact, where and how they're defined in our codebases, and finally the security implications of each step. about this event: https://talks.nixcon.org/nixcon-2025/talk/RF93ZE/

In this talk we go over how we leveraged Nix to build our new Katla synthesizer. We go through setting up development environment, CICD, Linux kernel optimizations, cross-platform compilation and other steps that make Nix a standout solution when building hardware products with a team distributed around the globe. about this event: https://talks.nixcon.org/nixcon-2025/talk/YGL3MV/

Nix is a powerful tool, but it also comes with some well-known problems: a steep learning curve, bad error messages, and slow evaluation. What if we could solve these three problems in one stroke? garn is an experiment in doing just that. With garn, you define derivations with TypeScript instead of in the Nix language. TypeScript is familiar to most developers, well-documented, and supported by rich editor tooling - thus lowering the learning barrier. And instead of stack traces, you mostly get (much nicer) type errors. garn also rethinks the CLI, clarifying the core user-facing concepts in Nix, and how they relate to one another. What exactly is a devshell? A check? A NixOS configuration? What operations make sense with them? By thinking of these as first-class objects instead of "just derivations", garn makes the UX more approachable, and more powerful. The currently-released version of garn generates Nix code, which means we still incur the cost of (often slow) Nix evaluation. But we are working on a second version which ditches Nix evaluation altogether, and uses Nix only to build .drv files. This opens the door to substantial speed improvements, with techniques such as pre-evaluating Nix (FFI) code, caching evaluation in a finer-grained way, async IFD, and even using WASM as an alternative to IFD. This talk will show how garn works both above and under the hood. It's aimed at anyone interested in making Nix faster and more accessible. about this event: https://talks.nixcon.org/nixcon-2025/talk/RJSMCA/

When working on a software project, it can often be useful to spin up local development versions of services that run in production. This can be as simple as running a database to run your tests against, or as complicated as spinning up dozens of machines that talk to each other, while allowing you to observe and debug complex interactions. In some non-Nix projects, docker-compose is used for this successfully, but it requires a lot of manual configuration. In projects where production machines are declared as NixOS configurations, the Nix ecosystem provides a lot of powerful building blocks for running VMs. But existing tools require a lot of manual configuration in order to run networks of VMs locally. They also have unintuitive interfaces and poor documentation, making it hard to use them (and, often, even to know about them!). nixos-compose addresses these problems. It's a polished CLI tool that makes it remarkably easy to: Start one or more VMs from a flake file, SSH into them for debugging, enable network communication between them, and access VMs from the host. In this talk, we’ll tour through the features and implementation of nixos-compose. nixos-compose is an open-source tool built by garnix: https://github.com/garnix-io/nixos-compose about this event: https://talks.nixcon.org/nixcon-2025/talk/BRJ8XS/

This talk will be in the format of an experience report. We will go over how to use the module system to declaratively manage BGP sessions, set up routing policies to manage traffic between hosts using addresses within advertised prefixes using systemd-networkd and nftables in a multi-upstream setup, and how to run a primitive anycast CDN. The talk will also include hiccups encountered while experimenting with the BIRD Internet Routing Daemon, Tailscale, and improvement plans. GitHub: https://github.com/stepbrobd/router about this event: https://talks.nixcon.org/nixcon-2025/talk/7YWTUC/

Discussion & Q&A about this event: https://talks.nixcon.org/nixcon-2025/talk/RZPTFK/

The most subtle part of Nix's store layer is the exact logic used to sandbox derivations. Mess up the daemon protocol, Local Store SQLite usage, drv file parsing, or other such things, and things should blow up immediately. Fail Fast helps a lot! Mess up the sandboxing logic, however, and you might not notice for a while until you try to build just the right sort of derivation. For most of Nix's history, the sandboxing logic has been embedded within the build scheduling logic (which builds or downloades dependencies) thus entangling it with hefty other machinery that makes all sorts of assumption about how IO, concurrency, etc. should work. In other words, it was not written in a way that made it easy to use from any other program but Nix itself. In the last few months, however, we've finally untangled it and moved it into its own component, and then reworked it to give it a simple interface for FFI. In this talk, we'll briefly go over that work, and then demonstrate its use a simple example executable written in a friendlier language than C++. about this event: https://talks.nixcon.org/nixcon-2025/talk/ZAHLMN/

There is a broad range of possibilities when packaging Python with Nix. The amount of Python formats alone can be overwhelming: requirements.txt, setup.py & pyproject.toml, not to mention Conda! This talk aims to explain Python packaging with Nix, focusing on pyproject.nix & uv2nix, but I will also talk about other approaches and their trade-offs. We'll start off with a short primer on the different Python packaging formats & methods while explaining a few of the things that make Python packaging particularly murky & difficult. Then we'll go through a range of Nix packaging possibilities, starting with using plain nixpkgs & culminating in pyproject.nix & uv2nix. Along the way the pros and cons of each will be explored and what approach to use when and where. about this event: https://talks.nixcon.org/nixcon-2025/talk/Y8TSAW/

Explain the current state of the LoongArch64 ecosystem, issues encountered with the Nixpkgs/NixOS port, and what to expect next about this event: https://talks.nixcon.org/nixcon-2025/talk/BMXTFW/

The history of how the official Nix formatter was successfully established, along with its struggles and lessons. We go over: - How Nix didn't have a formatter for its first 15 years before the first ones were written - How an RFC to standardise the formatter took 3 years, 50 meetings and 600 comments to get accepted - How one of the most active codebases with 40k Nix files and 15k monthly commits got fully reformatted - What problems still exist and what the future of Nix formatting holds about this event: https://talks.nixcon.org/nixcon-2025/talk/GCGE7K/

Opening day 2 about this event: https://talks.nixcon.org/nixcon-2025/talk/XVBSXD/

Given the amount of software written in memory unsafe languages, and the rise in supply chain attacks, I prefer to run as much software as possible within some kind of security boundary (mostly using bubblewrap and qemu). Bubblewrap is the sandboxing tool at the core of Flatpak, but it is intentionally designed to be very low level. Using bubblewrap, one can write wrappers for every package on their system, but getting the flags right can be error prone, and often lead to annoying debug cycles to get a program to run correctly. jail.nix is a nix library I have been working on to make wrapping Nix derivations in bubblewrap jails more ergonomic by using higher level combinators to achieve concrete objectives (like giving a program access to the network, or allowing it to render to a Wayland compositor). The library is open source, the source can be found here: https://git.sr.ht/~alexdavid/jail.nix This talk will give a tour of the features of jail.nix and how to integrate it with a NixOS configuration. about this event: https://talks.nixcon.org/nixcon-2025/talk/3QH3PZ/

I made a thing to manage the Linux machines of my friends and family: https://sraka.xyz/posts/ricochets.html, it's a hack with a custom NixOS default channel :) about this event: https://talks.nixcon.org/nixcon-2025/talk/RDSBZN/

Nix's package composition model makes developer environments a natural extension of its core abstractions. A simple shell.nix declaration combined with nix develop provides native tooling access and IDE integration that other build systems struggle to achieve without significant engineering investment. At LinkedIn, I experienced this contrast firsthand while migrating Go repositories to Bazel. I spent six months reverse-engineering Bazel's sandbox internals, writing custom rules to extract SDK paths, generate direnv configurations, and create LSP settings files. This enabled developers to use native Go commands via shell and IDE within Bazel workspaces, which proved crucial for broader adoption (Bazelcon 2024 talk on this topic). In this talk, I'll contrast months of custom engineering against Nix's declarative approach - just a few lines of config that solve the same problem in a manner that's harmonious with the build system. about this event: https://talks.nixcon.org/nixcon-2025/talk/HMKXYP/

Kubernetes is good for many machines with complex networking setups, but not that good for a 2-machine one, especially when there's only one maintainer and zero documentation. At GeekPie, I've migrated our mirror infrastructure to NixOS and in this talk I want to show how Nix helps us achieve more with less code & maintenance. about this event: https://talks.nixcon.org/nixcon-2025/talk/MKJPLZ/

When I first saw a colleague of mine typing "nix-shell", I had no idea what it did — but running it felt like magic. A swirl of "/nix/store/..." messages later, a fully working dev environment, with all the right tools and no system mess! Like Alice, I was “curiouser and curiouser.” In this talk, I’ll share the key “aha!” moments from my first few weeks with Nix — how I came to understand derivations, the Nix store, and pure builds. I’ll walk through the “from confusion to clarity” moments that helped me go from feeling lost in a sea of unfamiliar terminology to confidently writing my first Nix expressions. Along the way, I’ll highlight the resources, metaphors, and mental models that made the biggest difference — and the ones that didn’t. The Nix community is filled with passionate and experienced users, but for newcomers, the learning curve can feel overwhelming. This talk is not a tutorial, but a reflection: a newcomer’s perspective on what it’s like to learn Nix today, what helped me “get it,” and where the community can do more to support others on the same journey. about this event: https://talks.nixcon.org/nixcon-2025/talk/FMTH39/

Nix is a very promising technology for fundamentally improving supply chain security. In some ways its lives up to this promise already, in a lot of ways pieces of the overall puzzle are still missing, fall short in implementation, adoption or UX. Our panelists all work on supply chain security related tools and topics in the the Nix ecosystem, which we will use as a starting point to plainly discuss which issues they are trying to address and how they might fit into an overall picture. Come join us to find out what we all do and do not see in the overall picture, based on the puzzle pieces we, you or other people in the community are holding. about this event: https://talks.nixcon.org/nixcon-2025/talk/XWQC8U/

Over the past year at Shopify we've undergone a lot of changes internally. We moved from cloud development to local development, multirepo to monorepo, and Homebrew / Apt to Nix. Today, the majority of development is being done inside Nix-based environments. Some may recall that Shopify was using Nix back in 2019, so what happened? This talk will cover: * Why that effort stalled * How devenv reignited interest in Nix * How we approached incrementally migrating a huge collection of projects * Where we're at today, and lessons learned along the way * The many benefits Nix has brought * The challenges of supporting a large polygot org with developers working at every layer of the stack * Where we're headed about this event: https://talks.nixcon.org/nixcon-2025/talk/UPHTPD/

The Cyber Resilience Act (CRA) is the EU's most important regulation for software in the last decade. While it makes an exception for open-source software and impact NixOS directly, any commercial product that includes NixOS has to comply with the CRA to allow offering in the EU. In this talk, we give insights into the CRA’s requirements, showcase that Nix tooling with its focus on reproducibility is very well positioned for compliance, and point out the unsolved shortcomings. We focus on the update mechanism, SBOM tooling (together with matching CVEs from vulnerability mechanisms), and support durations. about this event: https://talks.nixcon.org/nixcon-2025/talk/3XBNPB/

Behind the Scenes of cache.nixos.org: Scaling Nix’s Binary Cache to Infinity The Nix binary cache is the silent powerhouse of the Nix ecosystem: every day, it fields thousands of requests per second—amounting to nearly 6 billion requests per month!—for NixOS and Nix users worldwide. But what makes it work at scale, how—or why—is its simplicity a virtue, and how does an ongoing partnership between AWS and the Nix Foundation ensure its availability for years to come? In this fireside chat, join Ron (Flox), Tarus (AWS), Tom Bereknyei and moderator Ross (Flox) for a conversation about: - What the Nix binary cache actually is… - …and why it matters for the community, reproducibility, and even the survival of historical software; - How AWS came to support cache.nixos.org - Why the binary cache’s “dumb” design is a feature, not a bug; - What goes in the cache? - Challenges and lessons learned: scaling, cost optimization, and keeping things simple - Why this partnership is important for the Nix ecosystem Whether you’re a builder, a Nix maintainer, a user, or just curious about how open source infra runs at global scale, this conversation will offer insights, anecdotes, and a look at how communities and clouds can support each other. about this event: https://talks.nixcon.org/nixcon-2025/talk/QXZJ9H/

Nix and Flatpak are often seen as solving similar problems from different angles: one declarative and reproducible, the other sandboxed and user-friendly. But what happens when you try to make them work together? And why would you want to do it? In this talk, I’ll present nix-flatpak (https://github.com/gmodena/nix-flatpak), an open-source project to declaratively manage Flatpak apps with Nix. This project started as a personal learning experiment to understand Nix, flakes, and module design, and grew into a practical tool to bridge the Nix and Flatpak ecosystems. We’ll cover: - A quick primer on Flatpaks and why they matter for desktop NixOS users - How Flatpak installations are managed declaratively in nix-flatpak - Architecture decisions and tradeoffs: convergent state vs full reproducibility - How to test and validate the module logic across system and user installations - What’s ahead: improving UX, stability, and community feedback The talk is intended to be interactive. I’ll share how the project evolved, but also open the floor to ideas, questions, and use cases from the community. Your feedback will directly shape the future of nix-flatpak. about this event: https://talks.nixcon.org/nixcon-2025/talk/XJ9JLH/

Imagine a Sim-City-style interface for managing your infrastructure: drag a machine onto the field, connect it to a service, and you're done. Behind the scenes, the clan.lol project turns that visual layout into the correct Nix modules - automatically configuring machines, managing secrets, and setting up a mesh VPN. In this presentation we detail: - Visualize and Configure Networks in 3D - A "Sim City" inspired 3D-UI to configure your selfhosted network without writing Nix! - Portable Multi-Machine Module System - Network-wide modules that configure multiple machines - Support for complex, role based relationships between machines (e.g. client, server) - Generation and distribution of secrets via generators - Multi VPN support - Support for running multiple VPNs at once - Deployment picks best suitable VPN connection - Extensible interface so users can define their own. - Multi-Platform support - Integrated MacOS support with nix-darwin. - Service Provisioning support about this event: https://talks.nixcon.org/nixcon-2025/talk/KX7AMW/

This talk explores the challenges and opportunities faced by the free software movement today. It offers a broad reflection on what "freedom" means in modern computing — and why it's more relevant than ever. Touching on questions of trust, corporate co-option, licenses, and the ethics of technology, it emphasizes the role of community engagement and governance structures. With urgency and clarity, it calls on developers to think beyond code and to take responsibility for the digital world we are collectively building. about this event: https://talks.nixcon.org/nixcon-2025/talk/NGPKNY/

NixOps4 is the successor of NixOps. Why did NixOps fail, and how does NixOps4 address its shortcomings? Will NixOps4 replace Terraform/OpenTofu? Will the demo work? https://github.com/roberth/nixcon-2025-slides about this event: https://talks.nixcon.org/nixcon-2025/talk/YCDXZM/

Ever wondered how “nix develop” works? What kind of arcane horrors make our reproducible developer environments work? In this talk we’ll begin by explaining how “nix develop” works, then we’ll use that understanding to explore what it looks like to create an improved devshell experience, including improved startup times, extension to shells other than Bash, and adding packages without needing to exit and re-enter the shell. Along the way we’ll discuss some of the cursed idiosyncrasies of different shells, and some of the patterns for working around them. In the end we’ll all need therapy, but we’ll know more about how our shells are conspiring against us and why we should all be using Fish. about this event: https://talks.nixcon.org/nixcon-2025/talk/MAEMPM/

The Hydra Queue Runner is a critical component responsible for orchestrating and executing build tasks within the Hydra infrastructure. Its reliability and efficiency are paramount for our Nix community, serving as a key component of the Nixpkgs infrastructure that builds the world's largest package set. A significant challenge with the current implementation lies in the communication between the Queue Runner and the builders. This system, built on SSH, directly read from and wrote to the running Nix daemon, which imposed a hard limit on connected builders. This talk will begin by explaining the current Hydra CI infrastructure and how Hydra works as a whole, looking at the evaluator, Queue Runner, PostgreSQL, hydra-notify, and hydra-web components and how they interact with one another. We will then detail the comprehensive redesign and re-implementation of the Hydra Queue Runner, transitioning from its existing architecture to a robust, high-performance solution built in Rust, specifically to overcome these limitations. We will present an overhaul of the remote communication protocol, migrating from the SSH implementation to gRPC, leveraging its benefits for performance, type safety, and interoperability. This change also benefits our ability to introduce generic messages unrelated to the Nix protocol, which enables the monitoring of the system utilization of all builders, making scheduling decisions more agile. Furthermore, we introduced comprehensive tracing capabilities, making the new Queue Runner significantly more debuggable and maintainable. We will then dive into the build pipeline, distinguishing between steps and runnables, examining the changes made to the build queues (now handling each platform with a separate queue) and what is needed to resolve a derivation. Lastly, we will present compelling benchmarks demonstrating how these changes have significantly accelerated builds and enabled a substantial increase in the number of concurrently connected machines. about this event: https://talks.nixcon.org/nixcon-2025/talk/SNFQ7J/

Presenting https://nixos-mediation.org/ what it is, how you can benefit from it, and a small retro. about this event: https://talks.nixcon.org/nixcon-2025/talk/CDU788/

We're going to dive into examples behind how GitHub Actions can be designed using Nix, while having little to no difference between local development environment and CI running somewhere else. about this event: https://talks.nixcon.org/nixcon-2025/talk/S8SKEG/

Lets explore how to ensure the sustainability of the Nix ecosystem with community leads including the SC and Foundation. We will dive into what it takes to create and maintain a robust, reliable environment for years to come. Covering the community’s milestones in 2024, from infra to governance, and about both the hard-won lessons and the innovations shaping Nix’s future. about this event: https://talks.nixcon.org/nixcon-2025/talk/9VKFRM/

Opening of the conference about this event: https://talks.nixcon.org/nixcon-2025/talk/QEN3WD/

Seit knapp 30 Jahren informiert das Chaosradio. Über (digitale) Technologie, wie sie aus Sicht des (Berliner) CCC die Gesellschaft und die politische Landschaft beeinflusst, und umgekehrt. Seit dem hat sich das Format immer wieder der Zeit angepasst: War es anfangs eine der einzigen Live-Sendungen im öffentlich-rechtlichen Radio mit digitalem Tiefgang die Dinge wie das “Internet für Fortgeschrittene” erklärte, ist es heute ein Podcast, der vor allem über Dinge berichtet, die in der sonstigen Berichterstattung oft zu kurz kommen. In diesem Vortrag zeichnet Danimo diesen Werdegang des Chaosradios nach, wirft einen Blick auf andere Sendungen des CCC und erklärt chaotische Radiotheorie in der Praxis. Über den Referenten: Danimo gehört seit Folge 200 zum Team des Chaosradios, hat in der ein oder anderen Folge auch vor dem Mikrofon mitgewirkt und ist heute vor allem für das zuständig, was einem Podcast widerfährt, nachdem an den Mikrofonen alles gesagt ist. Ansonsten treibt er sein Unwesen beim Video Operation Center des CCC und in diversen Hackspaces. Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/ about this event: https://c3voc.de

Licensed to the public under http://creativecommons.org/licenses/by/4.0 about this event: https://programm.froscon.org/2025/events/3460.html

Präsentation der Projekte anlässich des «Jugend hackt» Events vom 15 bis 17 August 2025 im Hackerspace «Bitwäscherei» in Zürich. Beim Projet Pet2Print ging es darum, ein eigenes Filament aus PET Flaschen, die in den Ozeanen als Abfall herumschwimmen, zu produzieren. Dafür haben Florin, Karl, Emil und Lev ein eigenes Gerät gebastelt, mit Kugellagern und einem Schneider, um das Vorprodukt, d.h. auf die richtige Breite zugeschnittene Plastikbändchen zu erstellen. Diese Bändchen wurden dann durch die Düse eines 3D Druckers, mit einer eigens dafür entwickelten Halterung geführt, womit dann die ersten Prototypen eines Filament produziert wurden. Beim Projekt Glowing Jellyfish diente das oben beschriebene Projekt Pet2Print als Inspirationsquelle. Die Überlegung beim Glowing Jellyfish war, wie Plastik aus den Ozeanen weiter nutzbar gemacht werden kann. Daraus entwickelten Ilse, Ida, Christian und George eine Jelly-Fish Lampe, an der LED Leuchten angeheftet wurden. Für das Design der Lampe verwendeten sie Blender. Das ganze wurden dann mittels eines 3D Druckers produziert und zusammen mit den LED Leuchten assembliert. Das LED Licht kann dann direkt angesteuert werden und die User:innen können für ihr Zuhause die Jellyfish Lampe farblich so einstellen wie sie es gerne haben möchten. Viele von uns haben Sachen im Keller, die besser weiterverkauft als fortgeworfen werden sollten. Um bei der Recherche für die Beschreibung des Artikels und Models nicht viel Zeit zu verlieren, haben Addy und Julian dafür eigens die App Flohbot erstellt. Damit kann man ein Bild zur Analyse an eine KI senden, die dann eruiert um was für ein Produkt es sich handelt und danach das Modell sowie die verkaufsrelevanten Informationen für den zu verkaufenden Artikel liefert. Für die Programmierung von Flohbot wurde Ollama, Java und Ionic (React) verwendet. Das Resultat war erstaunlich, zumal die beiden Jugendlichen vorher überhaupt keine Erfahrung mit der Entwicklung von Apps für Mobiligeräte hatten. Bem Team BSOD kam Tshehla bereits mit der Basis für ein Spiel bei Jugend hackt an. Emmi, Kyra, Max, Yann und Robin unterstützen Tsehla bei der Erstellung einen neuen Levels und einer neuen Welt. Eigens dafür entwickelte Modelle von Pilzen sollten in diesem neuen Level Teil der Landschaft sein. Die Jugendlichen teilten ihr Projekt in verschiedenen Bereiche ein. Tsehla arbeitete weiter an der Basis für das Spiel. Kyra hat sich in Eigenregie ihr Wissen für Blender angeeignet und konnte damit bereits ihre ersten Modelle erstellen. Robin hat das Concept Art dafür erstellt und dafür sehr schöne Bilder kreiert. Yann kümmerte sich um das 3D Model der Landschaft für das neue Modell. Und last but not least hat Max die Hintergrundmusik dafür beigesteuert. about this event: https://c3voc.de

When it comes down to scaling time series monitoring solutions things can get messy. That’s one of the reasons why VictoriaMetrics, a Silver member of the Cloud Native Computing Foundation (CNCF), started its journey some years ago. It is a simple, reliable and efficient set of Observability Solutions that's been adopted by many organizations. It's open source, with a strong community behind it, with enterprise and managed (Cloud) options for those who need support. VictoriaMetrics plays well with many standards, including Grafana and OpenTelemetry. Apart from that, in case you didn’t know, VictoriaLogs is the new kid in the block that's seriously outperforming other solutions. In this presentation, we’ll present the VictoriaMetrics Open Source projects and how they differ from other solutions, especially when it comes to scaling from single small setups to massive cluster deployments. Come learn how VictoriaMetrics projects can help to ease Observability! Licensed to the public under http://creativecommons.org/licenses/by/4.0 about this event: https://programm.froscon.org/2025/events/3368.html

Welche Art von Code wird im Forschungsprozess produziert und wie können wir ihn für spätere Nutzung aufbereiten? Wir sprechen darüber, wie wir Forschungsskripte langzeitarchivieren wollen, was Nachnutzbarkeit für Forschungscode aus der Psychologie bedeutet und geben einen Einblick in die Praxis. Mit der Open Science Bewegung halten auch neue Arten von Forschungserzeugnissen Einzug in die Wissenschaft. Während es für die Wissenschaft einen großen Mehrwert bedeutet, dass mehrheitlich durch öffentliche Gelder finanzierte Forschung transparenter und dadurch vertrauenswürdiger wird, entstehen durch neue Forschungsobjekte neue Herausforderungen im Umgang mit ihnen. Das Leibniz-Institut für Psychologie (ZPID) ist ein Infrastrukturinstitut und stellt mit PsychArchives das Fachrepositorium für Forschungsdaten aus der Psychologie bereit. Abgelegt werden hier u.a. Forschungsskripte und die Forschungsdaten, auf die sie sich beziehen. Die Aufnahme ins Archiv an sich garantiert aber noch keine Nachnutzbarkeit, vor allem nicht in der fernen Zukunft. In diesem Vortrag stellen wir unseren Plan vor, wie wir den Code unserer Datengebenden langfristig nachnutzbar machen wollen und erzählen von den Fällen, über die wir beim Entwurf einer Langzeitarchivierungspipeline gestolpert sind. Licensed to the public under http://creativecommons.org/licenses/by/4.0 about this event: https://programm.froscon.org/2025/events/3350.html