• 0 posts
  • 15 comments
Joined 11 months ago
Cake day: September 22nd, 2025
  • Yes, just enabling a service or program is one line in nix but the module behind can do a lot of things (install the package, create and enable the systemd service file, install and setup any db if needed or other service dependencies, set some default settings…). For some service that would be quite the bash script.

    Also theming in nix is very easy for the apps supported by Stylix.

  • You don’t need to add mcfly bash integration to your .bashrc manually. Remove it from home.packages and instead enable the home-manager module with programs.mcfly.enable = true;. That’s all you need to do, it has a enableBashIntegration setting that’s true by default. Same for atuin, programs.atuin.enable = true; is enough.

    It’s an habit you have to learn when switching to nix, check first if there is a module for the program you want to install before resorting to home.packages or environment.systemPackages.

  • On the AT Proto there a different kinds of data, identified by what’s called a lexicon. Bluesky’s aggregates data with a lexicon matching app.bsky.* (like app.bsky.post, app.bsky.like…). If Bluesky goes down you can still interact with your data, not just through the main Bluesky AppView. There are other apps that have their own lexicon (Sifa ID, a LinkedIn like, Tangled, a code forge, Stream.place, a Twitch like, Leaflet for blogging…). And even for Bluesky lexicon, there are other AppViews that aggregates the Bluesky lexicon (I think for now only Blacksky have one, Northsky and Eurosky are planning one but that’s not done yet).