social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Hey,
cry for help here
do I know anyone who knows both #zmk and #nix?
I use https://github.com/lilyinstarlight/zmk-nix to build my keyboard firmware; except this repo doesn't work anymore.
By 'doesn't work' I mean: Do
git clone https://github.com/lilyinstarlight/zmk-nix
cd zmk-nix
nix build .
and you will run into errors.
I believe this happens due to
solution would be
A new module is available: 'services.wbg'. wbg is a super simple wallpaper application for Wayland compositors.
#NixOS #Nix #HomeManager
A new module is available: `programs.gram`. Gram is a powerful and modern source code editor. It features solid performance and is highly configurable, yet comes with batteries included out of the box. Find out more here: <https://gram-editor.com/>
#NixOS #Nix #HomeManager
Klassische Linux-Distributionen folgen seit Jahrzehnten einem vertrauten Muster:
Ein Paketmanager entpackt Dateien direkt in gemeinsame Systemverzeichnisse wie /usr/bin, /usr/lib oder /etc. Auf Systemen mit #APT unter #Ubuntu, #DNF unter #Fedora, #Zypper unter #openSUSE oder #Pacman unter #ArchLinux funktioniert das im Alltag verlässlich – stößt aber an prinzipbedingte Grenzen, sobald widersprüchliche Anforderungen aufeinandertreffen.
Wird ein Paket aktualisiert, überschreibt es geteilte Dateien anderer Programme. Schlägt ein Systemupdate fehl oder bricht mitten im Entpackvorgang ab, verbleibt das System oft in einem inkonsistenten Zwischenzustand, der manuelle Reparaturen erfordert.
Nix wählt ein radikal anderes Architekturmodell:
-> https://admindocs.de/de/linux-neulinge/nixos-der-leitfaden-vom-paketmanager-nix
#nixos #nix #linux #paketmanagement #devops #linuxadmin #sysadmin #reproducibility
The absolutely most unnecessary
#nix error ever:
error: cannot coerce an integer to a string: 50000
So nix can't coerce integers to a string, okay. But what's that '50000' back there in the error message, then, huh? 😅 As if it wasn't 100% clear that people want the unambiguous decimal integer representation 🙄
Got #veilamp running inside a Debian #incus container. And a #nix flake sort of working (though the window chrome is off). Learned a bit about alsa and pipewire. Why do I have to make everything difficult? 😅
I need to build up a library again! I've gotten complacent stream-ripping most of my music with #NewPipe. Which works (but for how long) and quality is garbage.
Projects like this make you want to become the net we should have had. It makes me want to do better. The world needs #veilid now more than ever. 
For the 2nd year in Toulouse (France), we are organizing:
• Nix & Guix dev room at Capitole du Libre, November 14, 2026!
We're looking for various proposals for that track: lightning talks, longer presentations and discussions, sharing how you use Nix & Guix in real life, and demos of your latest side projects, either in French or English :)
* Submit a proposal: https://cdl.stoemp.club/guix-nix-au-capitole-du-libre-2026/cfp
* Deadline: October 21, 2026
We're also planning a meetup at LAAS (a research lab in Toulouse) on Friday afternoon and an informal dinner on Saturday evening.
See you in Toulouse!
Capitalism is already grinding us down every single day... it’s wild that DHH is out here acting like a class traitor, getting way too comfortable in the #NiX #community while completely disrespecting the NiX Code of Conduct. People like this need to be completely iced out.
My guy, if you don't want to respect minorities, trans men and women? if you don't want to respect people? build it from scratch on your own. get fucked.
@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.
Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!
#nix on
#SailfishOS on the new #JollaPhone 😎
I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.
How it started: Hey there is a wiki page https://nixos.wiki/wiki/Printing for how to add my printers into my #Nix configuration. It looks straight forward. I should do that.
How it's going:
(2nd screenshot is the configuration that when enabled throws this error)
After the usual grind re-setting everything up again, restoring backups, etc. I have everything I need set up now (except
#nix 🤓)
I am *very* happy with this phone. It's such a massive upgrade to the broken (or non-broken) Xperia 10iii phones I have been daily-driving with #SailfishOS for far too long now. 😅
- 🤩 double-tap to wake like in good old times
- 🤩 fingerprint unlock
- 🤩 dang it's fast and smooth!
- 🤩 configurable (privacy) switch on the side
A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
#NixOS #Nix #HomeManager
Yes. Like countries and democracies, every organisation has to make the decisions it believes are necessary. I respect that. My point is simply that #Codeberg has become system-critical to my work, including infrastructure built with #LLM assistance for #Nix. I now have to fear that a key part of that infrastructure could be removed without warning. 1/2
Yay, I added my #yannix flake to search.nixos.org. You can now find my #nix /
#NixOS stuff on the official search page:
📦 my packages: https://search.nixos.org/flakes?query=yannix
🔧 my NixOS options: https://search.nixos.org/flakes?query=yannix&type=options
#pipelight website is down!
I switched my servers config to dendritic #nix
Sorry for this collateral!
I am still bringing the pieces together 😫
A new module is available: 'programs.herdr'. Herdr is a terminal workspace and agent manager. The new module lets you install it and declaratively configure its TOML config file.
#NixOS #Nix #HomeManager
boostedGuixPkgs: every Guix package, as a Nix flake via @pbsds https://lobste.rs/s/rm7qnt #nix
https://fzakaria.com/2026/06/25/guixpkgs-every-guix-package-as-a-nix-flake
Oh great, nixos-rebuild tried to be smart again. You apparently need to keep a dirty worktree of the root git project or it'll clone all of the submodules from github (once you found the changelog where it tells you how to enable submodule support).
Why can't you just be normal?
I used relative paths for a reason. I didn't want you to download it from github each time. The local repo is the authoritative one...
Edit: or deleting the remote from the git repo, that also worked
A new module is available: `programs.hyprland-qt-support`. This module enables Hyprland Qt support — a Qt6 QML style provider for hypr* apps. It can be configured through the `settings` attribute.
#NixOS #Nix #HomeManager
The `programs.firefox.globalExtensions`, `programs.floorp.globalExtensions`, and `programs.librewolf.globalExtensions` options now assert that the browser package is managed by Home Manager. On Darwin, setting `programs.<browser>.darwinDefaultsId` also satisfies this requirement. If you used `globalExtensions` with `package = null`, set `package` to a non-null browser package or switch back to `profiles.<name>.extensions.packages`.
#NixOS #Nix #HomeManager
The 'programs.uv' module can now manage uv-installed Python versions and tools declaratively. Use {option}`programs.uv.python.versions` to install Python versions (with {option}`programs.uv.python.default` selecting the default interpreter per implementation) and {option}`programs.uv.tool.packages` to install tools. Unpinned entries track the latest release on each activation, while pinned ones (e.g. `"3.12.4"` or `"black==24.1.0"`) stay put. Set {option}`programs.uv.python.prune` or {option}`programs.uv.tool.prune` to make the managed set fully declarative, removing versions and tools that are no longer listed.
#NixOS #Nix #HomeManager
The `programs.codex.plugins` and `programs.codex.marketplaces` options were added to configure Codex plugins and local plugin marketplaces declaratively.
#NixOS #Nix #HomeManager
Nix Tip:
registry.unstable.to = {
type = "github";
owner = "NixOS";
repo = "nixpkgs";
ref = "nixos-unstable";
};
registry.master.to = {
type = "github";
owner = "NixOS";
repo = "nixpkgs";
ref = "master";
};
Works, but if you already have them pulled into your flake
registry = {
unstable.flake = inputs.nixpkgs-unstable;
master.flake = inputs.nixpkgs-master;
};
Is both faster for you, and nicer for github.
@xcabal05 I'm in the first batch and haven't gotten mine yet. I'm a fulltime #SailfishOS user since its beginnings though and I am happy thus far. It's a real Linux in the pocket, terminal, ssh, #nix, etc. which is what matters to me. The Android apps I need work fine. But expect annoyances here and there. I really hope the new phone fixes annoyances I have with my Sony Xperia 10iii now. Most notably the camera sometimes not saving photos or videos and network switching wrecking connectivity.
So, I gave #devenv a try.
I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.
But, while #devenv configs are composable locally, they can't import a remote config as #flake does.
Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.
CC @Ilygad
NixOS - Das Multi-Host-Setup individualisieren
In meinem letzten Beitrag der NixOS-Reihe zeige ich, wie man einen einzelnen Rechner aus dem gemeinsamen Setup herauslöst und individuell konfiguriert – ohne die anderen Rechner auch nur zu berühren.
#NixOS #Nix #Flakes #Nix_Store #Linux
https://gnulinux.ch/nixos-das-multi-host-setup-individualisieren