Terminal Root

Route application traffic via command line

Wed, 15 Apr 2026 22:03:23 +0000

toricli.sh is a tool written in Go, focused on making it easy to route application traffic via the command line. The goal is to simplify the use of anonymization on Linux without relying on complex configurations.

It falls into the same category as tools like torsocks, but with a more direct and automated approach.

Installation

For Windows, use WSL

# systemd
curl -fsSL https://raw.githubusercontent.com/thobiasn/tori-cli/main/deploy/install.sh | sudo sh

# Arch
yay -S tori-cli-bin

# macOS
curl -fsSL https://raw.githubusercontent.com/thobiasn/tori-cli/main/deploy/install.sh | sh -s -- --client

Docker:

docker run -d --name tori \
  --restart unless-stopped \
  --pid host \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  -v /proc:/host/proc:ro \
  -v /sys:/host/sys:ro \
  -v /run/tori:/run/tori \
  -v tori-data:/var/lib/tori \
  -v ./config.toml:/etc/tori/config.toml:ro \
  ghcr.io/thobiasn/tori-cli:latest

Usage example

toricli curl example.com

And the traffic is anonymized.

For more information, visit: https://toricli.sh/.

Pyrite64, a Modern Engine for Nintendo 64

Sun, 12 Apr 2026 22:11:56 +0000

Pyrite64 is an open-source engine + visual editor for creating native 3D Nintendo 64 games — not “N64-style”, but games that actually run on original hardware or accurate emulators. For development (scripting) with C++ or C

What’s the idea?

Replace the old workflow (confusing SDKs + broken toolchains)
Bring something closer to Unity/Godot, but focused on the N64
Generate real ROMs compatible with the console

Features:

Visual editor with scene management
Model import (GLTF / Blender + Fast64)
Node graph (basic visual scripting)
Runtime engine (rendering, collision, audio, etc.)
HDR + bloom adapted for N64
Asset manager with automatic cleanup ([AlternativeTo][2])

Installation

Windows

The project itself automates almost everything.

Download the release (or clone the repo)
Run the editor
It automatically installs everything:

GNU/Linux

Dependencies:

GCC/Clang
CMake
Basic build libs
libdragon toolchain

Then just clone, compile, and install

git clone https://github.com/HailToDodongo/pyrite64
cd pyrite64
mkdir build && cd build
cmake ..
make
sudo make install

Getting Started

Create a project

Inside the editor:

New Project
Set name + folder
It creates the structure with project.p64proj

Configure toolchain + emulator

File:

project.p64proj

Important fields:

"pathEmu": "ares",
"pathN64Inst": "/path/to/toolchain"

pathEmu → emulator command
pathN64Inst → toolchain root ([Instagit][3])

Import assets

Typical workflow:

Model in Blender
Export GLTF
Import into the editor

Build the scene

Add objects
Adjust transforms
Define materials

Game logic

Two options:

Node graph (visual)
C++ (more control)

Build and run

“Run” button
Generates ROM
Opens automatically in the emulator

For more information, visit the official website with FAQ.

Install This Modern Network Scanner with TUI Mode

Wed, 25 Mar 2026 10:43:42 +0000

If you’ve used tools like nmap and found them heavy, verbose, or too slow for simple tasks, Nibble solves exactly that problem.

Nibble is an open-source network scanner focused on simplicity, speed, and usability. It allows you to discover devices and services on your local network without needing to memorize complex commands or configure anything manually. It works on GNU/Linux, macOS, and Windows (x86 and ARM).

Installation

brew install backendsystems/tap/nibble
pipx install nibble-cli
npm install -g @backendsystems/nibble
go install github.com/backendsystems/nibble@latest

Or run it directly with:

npx @backendsystems/nibble

Nibble repository.

Manage APT packages with a modern terminal interface

Mon, 23 Mar 2026 11:13:08 +0000

APTUI is a TUI (Terminal User Interface) written in Go that acts as a frontend for APT.

The concept is simple: do everything you already do with APT, but without leaving the screen and without typing repetitive commands.

Main features

Real-time filtering as you type
Fuzzy search (no need for exact name)
Fallback to apt-cache search

Installation

Via Go

go install github.com/mexirica/aptui@latest

Or via APT (Debian/Ubuntu)

(custom repository available in the project)

Then just run:

aptui

For more information, visit the repository.

Manage Your SQL Databases via Terminal with This App

Wed, 04 Mar 2026 08:49:08 +0000

Pam is a minimalist command-line interface (CLI) tool written in Go, designed to simplify managing and executing SQL queries across multiple databases. Inspired by “The Office,” Pam pays homage to the character who organizes everything efficiently.

Key Features

Query Library: Save and organize your most-used SQL queries for easy access and reuse.
Multi-database Support: Compatible with PostgreSQL, MySQL, SQLite, Oracle, SQL Server, ClickHouse, and Firebird.
TUI (Terminal User Interface): Keyboard-focused navigation with Vim-inspired shortcuts for efficient manipulation of query results.
Direct Editing: Update cells, delete rows, and edit SQL directly in the results table.
Data Export: Export results in formats such as CSV, JSON, SQL, Markdown, or HTML.
Parameterized Queries: Support for parameterized queries, enabling dynamic searches without rewriting SQL.

Installation

You can install Pam via Go, by downloading the binary directly from the releases repository, or using Nix/NixOS.

go install github.com/eduardofuncao/pam/cmd/pam@latest

Basic Usage

After installation, initialize a connection to your desired database:

pam init mydb postgres "postgresql://user:pass@localhost:5432/mydb"

Add queries to your library:

pam add list_users "SELECT * FROM users"

And run them interactively:

pam run list_users

The TUI interface supports Vim-like shortcuts (j, k, h, l), copy cell (y), export data (x), edit cell (u), delete row (D), and more quick commands.

Pam stores its configuration in ~/.config/pam/config.yaml, allowing you to adjust row limits, column widths, and color schemes for the interface.

The app provides example commands for easily connecting to various database types, including PostgreSQL, MySQL, SQL Server, Oracle, SQLite, ClickHouse, and Firebird.

For more information, visit the repository

How to optimize the cd command to go back multiple folders at once

Fri, 20 Feb 2026 13:26:03 +0000

Everyone in the UNIX/GNU world constantly uses the cd command to navigate into folders through the terminal.

The cd command, also known as chdir, is a command implemented in command-line interfaces of various operating systems (Unix or any Unix-like system, DOS, Windows, OS/2 and AmigaOS).

On GNU systems (used by most Linux distros) it is a shell builtin, meaning it’s a bit more complicated to create a patch.

The cd command is very useful, however, one of the most annoying things is when you navigate into many folders and want to go back an exact number of steps, requiring commands like:

cd ../../../../../../
# Or
cd ..
cd ..
cd ..
cd ..
cd ..
cd ..

In both cases above, you need to go back 6 times.

But we can create a Bash function that reduces the amount of typing, making it faster and like a boss to go back to the 6th folder without much difficulty, like this: cd -6. Just add this function below to the end of your ~/.bashrc:

cd() {
    if [[ "$1" =~ ^-[0-9]+$ ]]; then
        local n=${1#-}
        local path=""
        for ((i=0; i<n; i++)); do
            path+="../"
        done
        builtin cd "$path"
    else
        builtin cd "$@"
    fi
}

Then reload your ~/.bashrc with the command: exec $SHELL or source ~/.bashrc and then just test it:

cd -6

In other words, use -(dash/minus) followed by the number of folders you want to go back, examples: cd -8, cd -7, cd -11,…

Remember that to go to your home folder, simply run: cd(without arguments) and to return to where you were, use: cd - without specifying any number!

Simple and practical, isn’t it?!

Vix: The 'Node.js' of C++, Without a Garbage Collector

Fri, 30 Jan 2026 12:52:19 +0000

vix is a modern runtime/framework in C++20 for building high-performance and distributed backend applications (offline-first, peer-to-peer, etc.) — a native alternative to Node/Deno, featuring async HTTP, routing, ORM, and modules.

It’s used to create web servers, APIs, and distributed applications in C++ with contemporary ergonomics (no garbage collector, no overhead from “old” frameworks). It features:

Async HTTP server (Asio)
Routing, middleware, native JSON
CLI for scaffold/build/run
Optional modules (ORM, WebSockets, utilities) Everything is designed for performance and offline/P2P applications.

Installation

Clone the repository and compile with CMake:

git clone https://github.com/vixcpp/vix.git
cd vix
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build -j

Optional: install headers/artifacts system-wide (according to the project docs).

To use it as a dependency in your project, include the compiled headers/libs and configure CMake to link with “vix”.

Basic Example (HTTP Hello world)

Create a main.cpp file:

#include <vix.hpp>
using namespace vix;

int main() {
    App app;

    app.get("/", [](Request&, Response& res) {
        res.send("Hello world from Vix!");
    });

    app.run(8080);
}

Compile with your CMakeLists that links the Vix runtime. When running, access localhost:8080.

For more information, visit: https://github.com/vixcpp/vix

Copy Files via Command Line with C++

Fri, 02 Jan 2026 23:05:48 +0000

How about the convenience of copying files via the command line? You can quickly create your own command with C++.

See the step-by-step guide below!

Dependencies

Example for distros that use APT as the package manager

Look for corresponding names for your distro.

sudo apt install build-essential libx11-dev libxcb1-dev libpng-dev

Also compile and install clip

git clone https://github.com/dacap/clip
cd clip
cmake . -B build
cmake --build build
sudo cmake --install build

Create the Code

Example: main.cpp

#include <clip.h>
#include <fstream>
#include <iostream>
#include <sstream>
#include <memory>

const auto use = [](){
  std::cerr << "Use: xclip++ <file> [file...]\n";
};

class Xclip {
  public:
    Xclip(int argc, char** argv){
      std::ostringstream buffer;

      for (int i = 1; i < argc; ++i) {
        std::ifstream file(argv[i], std::ios::binary);
        if (!file) {
          std::cerr << "Error opening: " << argv[i] << "\n";
          std::exit(1);
        }

        buffer << file.rdbuf();

        if(i + 1 < argc){
          buffer << '\n';
        }
      }

      clip::set_text(buffer.str());
    }
};

int main(int argc, char** argv){
  if(argc < 2){
    use();
    return 1;
  }

  auto xclip = std::make_unique<Xclip>(argc, argv);
}

Compile and Install

g++ main.cpp -o xclip++ -lclip -lxcb -lX11 -lpng -pthread
sudo install -v xclip++ /usr/local/bin/

Use Easily

xclip++ file.txt
# Or multiple files
xclip++ file1.txt file2.md file3.cpp # ...

Update and Fix

If you notice, when trying to use the pipe (|) it doesn’t work, for example:

cat file.txt | xclip++
echo 'Lorem Ipsum' | xclip++

To fix this, I added:

<unistd.h>
Overloaded the constructor: Xclip(const std::string& content) to clip::set_text(content);
And finally added setvbuf(stdout, NULL, _IONBF, 0);

Code ready to use with pipe:

#include <clip.h>
#include <fstream>
#include <iostream>
#include <sstream>
#include <memory>
#include <unistd.h>

const auto use = [](){
  std::cerr << "Use: xclip++ <file> [file...]\n";
};

class Xclip {
  public:
    Xclip(int argc, char** argv){
      std::ostringstream buffer;

      for(int i = 1; i < argc; ++i){
        std::ifstream file(argv[i], std::ios::binary);
        if(!file){
          std::cerr << "Error opening: " << argv[i] << "\n";
          std::exit(1);
        }

        buffer << file.rdbuf();

        if(i + 1 < argc){
          buffer << '\n';
        }
      }

      clip::set_text(buffer.str());
    }

    Xclip(const std::string& content){
      clip::set_text(content);
    }
};

int main(int argc, char** argv){
  setvbuf(stdout, NULL, _IONBF, 0);

  bool has_pipe = !isatty(STDIN_FILENO);

  if(has_pipe){
    std::ostringstream ss;
    ss << std::cin.rdbuf();
    std::string input = ss.str();

    Xclip xclip(input);
  }else if (argc > 1){
    Xclip xclip(argc, argv);
  }else{
    use();
    return 1;
  }

  return 0;
}

Compile and install:

g++ main.cpp -o xclip++ -lclip -lxcb -lX11 -lpng -pthread
sudo install -v xclip++ /usr/local/bin/

If you want a shorter command name, also run:

mv xclip++ xclip
sudo install -v xclip /usr/local/bin/

Now just use the xclip command, examples:

# Single file:
xclip++ file.txt

# Multiple files:
xclip++ file1.txt file2.md file3.cpp # ...

# Via pipe:
echo 'My test' | xclip
cat file.txt | xclip

Get to Know GNU Guix: A System for Programmers

Thu, 01 Jan 2026 18:54:50 +0000

GNU Guix is a distro, package manager, and operating system from the GNU project that proposes a radically different approach from most GNU/Linux distributions. It is based on functional management (Guix System), focusing on reproducibility, isolation, and total system control by the user.

Similar to NixOS, it uses the GNU Guile (Scheme) language to define packages, services, and the entire system configuration.

Features:

The output depends only on the inputs.
There are no side effects on the system.
Each package is installed in a unique directory in /gnu/store.
Nothing overwrites anything.
Different versions of the same software coexist without conflict.
Instant rollback.
Independent profiles.

GNU Guix is widely used for: Scientific Research, DevOps, and Security Auditing.

Guix strictly adheres to the Free Software Foundation guidelines, solidifying: Free Software Freedom.

GNU Guix is not for those who want to “just install and use”; it’s for those who want control, predictability, and truly declarative systems.

If you see the operating system as code, Guix makes more sense than any traditional distro.

Download and Installation

You can download the .iso from the GNU Guix Downloads page. Choose the alternative that suits your interest. If you are installing on your physical machine, choose the first option: GNU Guix System (version) 64-bit (x86_64) or 32-bit (i686).

After booting from the .iso file, just follow the steps to install, which, by the way, is quite intuitive. The first screen will be this one. If you want ease, just choose the option using graphical mode:

GNU Guix does not use the commercial Linux Kernel but offers you two types of Kernels:

GNU Hurd, a kernel that is not yet finished but functional, which separates tasks. Since Linux is considered a systemd (like a multifunction printer) of kernels—it performs many tasks, which is considered a bad idea by many (including Tanenbaum, the creator of Minix, which inspired Linux);
and also GNU Linux-libre, an operating system kernel cleaned of all binary blobs containing private firmware, some of them even created by the NSA.

The selection screen is this one:

Choosing the Graphical Environment

During installation, you can also define your Desktop Environment or Window Manager, or even install your own (e.g., KDE Plasma), which is not in the list later, but already on this screen there are options: GNOME, XFCE, MATE, Icewm, Openbox, AwesomeWM, i3, Ratpoison, and Emacs EXWM:

After these basic choices, just partition your disk as desired and start the installation process… and then, after the reboot, just choose the system automatically in GRUB:

Usage

To install anything, just use the guix command without sudo. Example, installing Vim:

guix install vim

Remember that GNU Guix offers independent profiles, so Vim will only be available for your user.

If you want to install globally, add the vim package to the packages section of operating-system in the path: /etc/config.scm, example of inclusion on the append line:

(use-modules (gnu))

(operating-system
  ;; ...
  (packages
   (append
    (list vim)
    %base-packages)))

If you need to reconfigure to see it: sudo guix system reconfigure /etc/config.scm

Then just install with sudo:

sudo guix install vim

The package list has everything: GNU GCC, GNU Make, Clang/LLVM, CMake, … For all packages, see:

https://packages.guix.gnu.org/

Or here: https://hpc.guix.info/browse.

For more information, visit: https://guix.gnu.org/

20 Alternatives for Sharing Code as Images

Sat, 29 Nov 2025 17:10:36 +0000

A few years ago, I published a list of good options for sharing code snippets.

Now, with new tools emerging and others evolving, I’ve prepared an updated version: 20 Alternatives for Sharing Code as Images. If you’ve seen the old list, this is a continuation, but with IMAGES. If you haven’t, this new selection already includes what’s worth using today.

01. Ray.so

Very clean and simple interface. Has light, dark, and gradient backgrounds. Allows adjusting padding, font size, and exporting as PNG.

02. CodeImage (app.codeimage.dev)

Highly configurable: themes, borders, windows, fonts. Great for those who want to “build” the image, not just copy and paste.

03. Snappify

Allows for more complex layouts: multiple code blocks, annotations, diagrams. Exports in PNG or SVG.

04. CodetoImg

Simple (“no-frills”) interface for quickly turning code into an image. Allows for different themes and languages.

05. Chalk.ist

Has interesting modes like “diff mode” (showing differences between code versions). Allows customization of background, line numbers, reflection, etc.

06. CodePNG

Minimalist tool for generating simple and elegant images. Support for different languages, customizable font, and simple settings.

07. Polacode (VS Code)

Extension for VS Code: generates a screenshot directly from the editor, preserving your theme. Very useful if you want to capture code snippets while you’re already programming.