sloppy_diffuser

@RareBird15 @programming @linux @selfhosted

Ones I haven't seen mentioned (unless it came in while I was typing this).

https://github.com/kainctl/isd - Interactive systemd.

https://github.com/zellij-org/zellij - tmux alternative. Built in which-key functionality. I initially switched to it because I like large scrollback buffers and tmux was super slow at resizing window panes. Can open buffers in nvim for better search. Nicer TUI if you don't mind a little bloat / bling.

https://github.com/arxanas/git-branchless - Work on stacked commits. Instead of opening PRs linerally you work on several commits at once with the expectation each commit will be a PR. Promotes smaller PRs that are easier to review to complete a feature. Often when doing that linerally you may discover a bad choice made earlier and have to reverse course and refactor. With a branchless workflow you go back and forth on commits so the final stack of PRs doesn't include those reverse course refactors. git sl has some nice TUI graphs of your stack.

https://github.com/mystor/git-revise - Split, rearrange commits. Works nicely with git-branchless.

https://github.com/tummychow/git-absorb - Reflect changes from a commit backwards. Also works well with a branchless workflow.

If I'm honest I just develop linerally and use an AI agent/skill to restack using the 3 programs above to erase pivot / refactor points and to group logical blocks into an easy to review PR.

https://github.com/ymtdzzz/otel-tui - Open Telemetry viewer.

https://github.com/brocode/fblog - JSON Lines viewer.

https://github.com/aristocratos/btop - Better top.

https://github.com/jandedobbeleer/oh-my-posh - Terminal prompt. My daily driver.

https://starship.rs/ - Another terminal prompt. Played with a little but never got around to giving it my full attention to match my oh-my-posh setup.

https://rclone.org/ - Remote backups using my own encryption key. Supports many cloud providers.

https://github.com/Mic92/nix-fast-build - Not sure its really faster but has a nicer TUI.

https://dircolors.com/ - Directory listing colors in terminal output to better distinguish file types. At a glance I can distinguish read-only, executables, symlinks, directories, etc.

https://github.com/jesseduffield/lazygit - Git TUI. I only use in neovim though, don't think I've ever run it directly.

https://github.com/sindrets/diffview.nvim - Better merge conflict handling in neovim.

https://www.lazyvim.org/ - Base neovim config with lots of TUI sugar.

https://github.com/stevearc/oil.nvim - File tree explorer in neovim with editing capabilities. Hands down the most efficient way I've found to normallize torrent file names. Fixing 5+ seasons of a show takes a few minutes if you know the right vim keybinds.

https://github.com/getsops/sops / https://github.com/mic92/sops-nix - Encrypt secrets in git repos.

https://github.com/zdharma-continuum/fast-syntax-highlighting - Syntax highlighting as you type shell commands.

https://github.com/luccahuguet/yazelix - Opinionated Yazi, Helix, Zellij setup with custom patches to integrate. Looks interesting but could never get to work with nix as it keeps trying to write to store paths. They even have a flake.nix in the repo...

less - Less shitty more (terminal pager) with the options below.

export LESS="-aRix2 --use-color --mouse --wheel-lines=3"
export SYSTEMD_LESS="$LESS"

# a = search from current position
# i = case insensitive
# x2 = tabstop
# R = color control chars show color 

https://pnpm.io/ - Better monorepo support than npm. Faster too. Easy to patch dependencies.

https://bun.sh/ / https://deno.com/ - Alternate node runtimes. Only have used bun, but its a faster cold start and uses less memory.

https://oxc.rs/docs/guide/usage/linter.html - eslint clone in rust. Seconds versus minutes. Uses the golang TypeScript 7 preview version of typescript-eslint for type checking.

https://rolldown.rs/ - Rust clone of the rollup JS/TS bundler.

https://ast-grep.github.io/ - Grep AST patterns. Written in rust.

https://dprint.dev/ - Formatter that unifies other formatters. Lots of fast rust plugins.

https://biomejs.dev/ - Rust based node formatter. dprint support.

https://github.com/astral-sh/ruff - Rust based python linter and formatter. dprint support.

https://github.com/numtide/treefmt - Like dprint, forwards to other formatters, but intended for nix declarative setups (for use with devshell or devenv).

https://direnv.net/ / https://github.com/nix-community/nix-direnv - Activate a virtual environment when you enter a directory. Common with nix devshell/devenv but can run any command. Auto reload based on certain files via watch patterns.

https://github.com/mikesart/inotify-info - Debug why you've maxed out file watchers.

https://github.com/lyonel/lshw / https://github.com/pciutils/pciutils - Detailed hardware info.

https://github.com/wagoodman/dive - TUI to explore docker layers.

https://github.com/containers/skopeo - Bunch of utilities for working with docker images and registries.

cash cant be traced

I think this is a feature, not a bug. You assume the risk in exchange for some privacy assuming you don't deanonymize yourself on the return address.

You could print a random letter or graphic(s), preferably on heavier paper

I was expecting this at the first half of the sentence: https://27bslash6.com/overdue.html

I've been using etesync for contacts to fill the void when I first discovered it wasn't supported. I don't really use any of the other features outside of a e2ee cloud sync of contacts.

Don't know if they can. If I'm recalling correctly he holds enough Class B shares to retain supermajority voting power.

Anyone else using the same concept would have to write an increasingly convoluted while loop with extra steps.

Sounds like an origin story for recursion.

NixOS. Started with Yellow Dog Linux in 1998.

I don't do everything through nix's derivation system.

Many of my configs are just an outOfStoreSymlink to my configs in the same dotfiles repos. I don't need every change wrapped in a derivation. Neovim is probably the largest. A few node projects for automations I'm fine using pnpm to manage. Nix still places everything but I can tweek those configs and commit in the same repo without a full blown activation.

Items are in a hash table using color/material type/shape as the hashing method optimized for human pattern recognition providing O(1) access. The table is smaller than the number of items causing some collisions. Those items are in a randomly sorted vector. Average case is still around O(1) with an O(n) worst case.

Olauncher (free version) and Pro Launcher (paid version).

Used the free version for years and decided to shell out for the paid version about a year ago.

Primary access to apps is via the search outside of the limited slots for shortcuts (text). Paid version adds some additional slots (icons). Simple and reminds me of a terminal.

Something like https://graphite.com/ to create stacked PRs that are reviewable probably would have helped. Can be replicated with local LLMs or remote AI providers with locally configured agentic workflows. Never used graphite personally, but I've seen some open source maintainers use it to split up large PRs.

With these sorts of tasks models really seem to suffer from not knowing what packages or conventions have been deprecated. This is really obvious with an immature ecosystem like nix.

This is where custom setups will start to shine.

https://github.com/upstash/context7 - Pull version specific package documentation.

https://github.com/utensils/mcp-nixos - Similar to above but for nix (including version specific queries) with more sources.

https://github.com/modelcontextprotocol/servers/tree/main/src/sequentialthinking - Break down problems into multiple steps instead of trying to solve it all at once. Helps isolate important information per step so "the bigger picture" of the entire prompt doesn't pollute the results. Sort of simulates reasoning. Instead of finding the best match for all keywords, it breaks the queries down to find the best matches per step and then assembles the final response.

https://github.com/CaviraOSS/OpenMemory - Long conversations tend to suffer as the working memory (context) fills up so it compresses and details are lost. With this (and many other similar tools) you can have it remember and recall things with or without a human in the loop to validate what's stored. Great for complex planning or recalling of details. I essentially have a loop setup with global instructions to periodically emit reinforced codified instructions to a file (e.g., AGENTS.md) with human review. Combined with sequential thinking it will identify contradictions and prompt me to resolve any ambiguity.

The quality of the output is like going from 80% to damn near 100% as your knowledge base grows from external memory and codified instructions in files. I'm still lazy sometimes and will use something like Kagi assistant for a quick question or web search, but they have a pretty good baseline setup with sequential thinking in their online tooling.

Like, from Yellow Dog Linux? Was my first Linux distro as a kid (grew up with an Apple computer). Red Hat based so checks out. TIL.