Tech TALKK! - [^_^]

Okayyy, so I realized talking about tech is gonna eat up way too much space on my About Me page. So, I decided to give it its own page - a dedicated little playground for all the tech I use. That way, anyone curious can just jump straight in without digging through my personal blog. Anywayyy, I think you get the idea… so let’s talk tech

Hardware I use

Let's start with the one that I spend most of my time with.

Latitude E5470

Is my main device that I run Arch Linux on it as my main operating system, and I use this device for studying, coding, all my academic staff, and of course for my personal use.
You may ask why Arch specifically?. so when I choose operating system to use as my main one it was based on several points: Each point of them may take lots of pages to talk about so I mentioned the headlines only
I think now you just figured it out why I choosed Arch cuz it is satisfied all points, and also I did not have any problems with systemD (till now) so it is all fine for me to use it instead going to void.
I use dwl, foot, and wmenu, deliberately following in the footsteps of dwm, st, and dmenu. out of a deep appreciation for the suckless philosophy. I value software that stays small, predictable, and honest about what it does. Minimal storage, minimal CPU and memory usage, and minimal distractions. A workflow that does exactly what I tell it to, and nothing more.
RIP X11, you served your time.

Ideapad 3

This is my second device, which I use regularly. I have Windows installed on it for specific reasons, such as using tools and applications like Photoshop when needed for work or other purposes. Additionally, I use it occasionally to play League of Legends.

Galaxy Tab A 10.1

This is the third and last device I use consistently. It is my school device, which I use exclusively for educational purposes, such as reading documents, accessing textbooks while studying, and similar tasks.
I’m also considering switching its operating system from Android to GrapheneOS, both for the experience and to enhance its security.

Software I use

Wayland-based minimalist stack

In pursuit of a lightweight, efficient, and distraction-free environment, I deliberately avoided full desktop environments such as GNOME, KDE Plasma, or even lightweight stacks like Xfce. Instead, I built my system around the Wayland display protocol, which provides a modern, secure, and low-latency alternative to the traditional X server model.

At the core of this setup is dwl, a dynamic tiling Wayland compositor inspired by dwm. dwl preserves the minimal philosophy of suckless tools while leveraging Wayland’s cleaner architecture. My configuration focuses strictly on functionality, with only essential patches and modifications applied to support my daily workflow.

wmenu

For simple user interaction, I use wmenu, a minimal Wayland-native menu program inspired by dmenu. It integrates seamlessly with dwl and avoids any XWayland dependency, keeping the entire graphical stack purely Wayland-based.
I use wmenu primarily to trigger scripts, and present minimal selection menus. Its simplicity allows me to pipe shell output directly into it, making it an essential component in several automation workflows.

foot

The terminal I choose in my setup is foot. It is a fast, lightweight, and Wayland-native terminal that aligns well with the minimalist design goals of my system.
Given that most of my interaction with the system happens through the terminal, foot serves as a central interface for my usage.

vim

vim is the editor I spend the majority of my time in. I use it as a complete working environment for programming, note-taking, configuration, and documentation. The modal editing paradigm allows me to operate efficiently with minimal context switching.
You can find my vim configuration at .vim/vimrc in my dotfiles.

swhkd

For managing global key bindings under Wayland, I use swhkd. swhkd is a Wayland-compatible hotkey daemon inspired by sxhkd, designed to work cleanly with compositors like dwl.
My key binding definitions are stored in .config/swhkd/swhkdrc.

mako

System notifications are handled by mako, a lightweight notification daemon designed specifically for Wayland compositors. It provides unobtrusive, configurable notifications without pulling in large dependencies.

vim-LaTeX-zathura

By combining these three tools, I've created a powerful solution for summarizing my lectures and managing my academic work. In essence, I use these tools for studying and taking notes.
You can find the source code for my plugins in the .vim/ftplugin/tex.vim file within my dotfiles. I wrote all these plugins myself. While there are many better options available online, I created them specifically to meet my needs and to be as minimal as possible, aligning with my goal of using the OS as I mentioned earlier.

GnuPG (GNU Privacy Guard)

GnuPG is my go-to for locking down everything—emails, photos, backups—because privacy is just common sense. No shady middlemen, no bloated software, just pure control. I trust math over people, and encryption keeps my data mine.

LibreOffice (Docx, pptx, etc..)

I use LibreOffice for my documents, but I don't use it to write DOCX files or create PDFs. Instead, I rely on Vim, LaTeX, and Zathura, as I mentioned earlier.

software I was using

Kali Linux

For penetration testing, security research, and offensive security workflows, I use Kali Linux in its default configuration as provided by the official installer. I just used it for some educational purposes and returing back to arch.

Xfce DE

The default graphical environment in my Kali setup is Xfce. I use it as-is, as previously mentioned, since Kali was installed for a temporary period of time.

Xfce Terminal

The primary terminal emulator in this setup is Xfce Terminal.

Preinstalled Kali tools

One of the primary reasons for using Kali Linux is its extensive collection of preinstalled security tools. These tools are organized by category and tightly integrated into the system menus, allowing for quick discovery and execution.
The toolset includes, but is not limited to: This curated environment allows me to focus on methodology and analysis rather than installation and dependency management.

Suckless tools

In an effort to minimize the use of my laptop's CPU and memory, I opted against using desktop environments such as Gnome, KDE Plasma, or even Xfce. Instead, I chose to implement a tiling window manager, specifically utilizing the X server with dwm, st, and dmenu, along with other efficient suckless tools. This decision was primarily driven by their simplicity and effectiveness. My system configuration is intentionally minimalistic, as I prioritize functionality over aesthetic customization. I rely solely on the terminal and dwm as my window manager, with dmenu to streamline certain tasks. Consequently, I have only applied a few necessary patches tailored to my specific use cases, aligning with my primary objective for using this operating system.

sxhkd

For managing my system key bindings, I use SXHKD. If you don't know what SXHKD is, it's basically an X daemon that executes commands based on input events. This makes it pretty easy for me to do some things faster and execute scripts just by pressing a key. The integration between SXHKD and other tools in my system, like dmenu and xclip, provides me with a really powerful tool and improves my workflow.
If you want to have a look to my key bindings you can reach it here .config/sxhkd/sxhkdrc in my dotfiles.

xclip

As anticipated, I utilize xclip as the clipboard manager for my system. For those unfamiliar, xclip is a command-line interface for X selections. I find it incredibly useful, especially when combined with dmenu, as it enables me to perform a variety of tasks efficiently.


This line means that the page is still under construction.