u/AshR75

GitHub: https://github.com/rccyx/osyx

All open source --> https://github.com/rccyx/osyx

All open source on GitHub: https://github.com/rccyx/osyx

This is a highly configurable SDDM login system.

Free and open source software of course, MIT licensed.

It ships with 5 complete visual setups right out of the box (4 static images, like the one you saw, and 1 looping video), and you can tweak literally everything through a single theme.conf file.

You can swap the background image or video, adjust blur intensity, change fonts and sizing, shift the form layout (center/left & right), change animation easing curves, and customize every single color hex across the text fields, buttons, and hover states.

So, I've been running Linux exclusively for many, many years at this point.

Over time, my setup has evolved into a highly tuned terminal centric & keyboard driven machine, and I've decided to start open sourcing parts of it to give back to the community.

There are many tools I've built for my personal workstation, and this specific tool happens to be a core login system.

Even though a login screen may look trivial, if you daily drive Linux, you have probably run into the common dilemma:

On one hand, you have the stock distribution defaults. They're incredibly stable and reliable, but they look very stock and out of place on a custom machine, and it's very hard to customize them.

And on the other hand, you have highly stylized options built by community hobbyists. They look beautiful and creative, but they are often structurally brittle. They can leave untracked files across your directory tree, break unexpectedly, etc.

When that happens, you have to deal with what I call the Monday morning problem.

You're all of a sudden locked out at a TTY prompt, having to handle it yourself, and wasting time Googling at 8:00 AM when you should be doing anything BUT that!

So I made this to have something that still looks premium and pristine on a login, but also brings enterprise like reliability to it. It gives you a super flexible QML design system without risking your system stability.

The installation is just a one command safe run. It builds out a local staging area first, validates the files and dependencies, and only activates the login system once everything passes. If you happen to run it 55 times or so, it won't brick/duplicate anything. It simply checks the file state and moves on.

It's tested across a massive matrix of distros, covering almost everyone at this point like Arch, Fedora, Debian, and Ubuntu (along with all the flavor bundles like Pop!_OS, Mint etc.). It works on openSUSE, Gentoo, even Alpine, and I just added NixOS support today.

If a failure happens mid-installation, it rolls back automatically to your previous working configuration so your session is never compromised.

The uninstaller is also first class.

It pulls out all fonts, configurations, and the repository source, returning the system exactly to its pre-cloned baseline. The only thing it leaves behind is the base Qt dependencies since there is no way to know what was on your system beforehand.

I also included a safe runtime preview command so you can test your visual changes on the fly without having to log out or reboot to verify the configuration.

Now, this is technically an SDDM theme but it works across the distro matrix here. I broke down everything you need to know, how the stack sits, how to configure & switch back, and also how to escape the TTY limbo just in case in the docs section .

Source: https://github.com/rccyx/thyx

GitHub: https://github.com/rccyx/osyx

I just open sourced the login screen from my personal Linux setup.

It’s a QML based SDDM theme system with 5 complete presets (4 static images and one dynamic video).

Everything is configured through theme.conf: background image or video, blur, font, form position, animation timing, easing, date and time format, field colors, placeholder colors, button colors, and the power/restart/sleep icons.

The installer is one command, sets up everything atomically. It detects the distro (Debian based, Arch, Fedora, and more), installs the needed runtime packages, stages the theme first, validates the tree, then moves it into place.

There’s also a matching uninstall script that removes the theme, fonts, and installed files cleanly, basically as if the theme has never been installed (except for the QT dependencies since there's no way to know).

Preview works without restarting SDDM, so you can tweak the login screen without logging out every time.

Plus, I aded a comprehensive readme & guide even if you're not too familiar with SDDM, and all of this, it explains everything.

GitHub: https://github.com/rccyx/thyx

Made a super customizable login screen theme (actually 5 presets) for Linux, if this isn't your call to leave Microslop for good, I don't know what is 💔🥀

GitHub: https://github.com/rccyx/thyx

I made a an SDDM login theme(s), well it's 5 preset themes (4 static and one dynamic) but it's infinitely customizable though a `theme.conf` file, so you can make your own.

Has video background support, PAM fingerprint auth, composable QML design system, one-command installer/uninstaller. CI/CD tested on every push.

The installer is idempotent and atomic throughout. Tells you exactly what it will do before doing anything, handles edge cases defensively, backs everything up.

The uninstaller pulls out everything the theme installs, fonts, repo, the works, except the Qt dependencies, and falls back to whatever theme you had before.

Also added a simple doc covering the full mental model: how login works on Linux, what SDDM is, how the auth stack fits together, what the installer does line by line, and recovery steps for the unlikely case something goes sideways.

Auto installs automatically on Omarchy since it's Arch.

But it also covers fedora, Ubuntu (Jammy / Noble / Resolute), Debian (Bookworm / Trixie / Forky / Sid), Linux Mint, Pop!_OS, Zorin, openSUSE Tumbleweed, Gentoo, Alpine Edge.

Everything configured through theme.conf: wallpaper or video background, font family and size, form alignment, background blur, animation duration and easing, date/time format, field and placeholder colors, button colors, power/restart/sleep icon colors and hover states.

Safe to preview without restarting sddm or rebooting on every tweak.

Source (MIT): https://github.com/rccyx/thyx

It's the renaissance all over

source ---> https://github.com/rccyx/osyx

Been running tmux as the backbone of my workflow for years, but the default green status line is a visual relic at this point.

It probably makes a lot of people skip over tmux entirely for other options, mostly because they don't realize it can look beautiful.

Over time, I've engineered a highly optimized, distraction free keyboard, terminal centric environment & without tmux it wouldn't be possible.

Thought I'd open source my themes for the community:

GitHub ---> https://github.com/rccyx/osyx

TMUX config Docs ---> https://github.com/rccyx/osyx/blob/main/docs/ui/tmux.md

TMUX jinja template ---> https://github.com/rccyx/osyx/blob/main/packages/flavors/base/tmux.conf.j2

It's a toggle also so you can hook it to i3, Sway, GNOME, whatever. Tap once, speak as long as you want, tap again. Transcribed, copied to clipboard (optionally piped to stdin), runtime artifacts wiped & binary exits.

The install (and uninstall) is one command.

YOU compile it on YOUR own machine. No pip. No cargo. Nothing.

The only thing pulled during setup is the GGML Whisper source at a pinned git commit, which itself has no deps and compiles straight with a standard C++ toolchain. CPU only. No CUDA, no Vulkan. If the machine has a CPU it works.

If you have a C++ build environment on Linux you basically have everything you need already.

Handles audio directly via PipeWire or ALSA.

Runs local transcription against GGML Whisper models through their C-compatible API, linked in-process. No server. No queue. No resident process.

The idle footprint is exactly 0MB.

The CLI:

asryx                          # Toggle record/transcribe
asryx status                   # Check idle/recording/transcribing
asryx --pipe-to '<COMMAND>'    # Set post copy pipe command
asryx --no-pipe                # Clear post copy pipe command
asryx --language <auto|CODE>   # Set language
asryx --model list             # List supported models
asryx --model install <MODEL>  # Download model
asryx --model use <MODEL>      # Switch model
asryx --model uninstall <MODEL> # Remove model

Default model is base.en at 142MB. Works with all supported GGML languages (99 langs).

The README lists every file and directory the tool touches.

Doesn't stay in memory between uses.

Doesn't load the model unless invoked.

Plus, I hate blackbox tools, so I explained exactly how it works in the mechanism section in the README:

Source(Apache-2) --> https://github.com/rccyx/asryx

Microslop said you can only change the wallpaper, I'm like bet.

Switched to Linux three years ago, started with WSL (it sucks), now I run Debian full time. No need for any Microslop whatsoever.

(uploaded my confs on github: https://github.com/rccyx/osyx)

TL;DR:

I’m running Debian 13 with Hyprland here, but the switcher itself is portable.

It’s basically a fuzzy finder CLI shell layer. Alt+R rotates the whole desktop theme live: Starship, Tmux, Hyprland borders, Mako, Wofi, Neovim, Dircolors, Git colors, wallpaper & the login.

GitHub ----> https://github.com/rccyx/osyx

I’ve been trying to find a reliable voice-to-text tool for my daily workflow, but I've consistently run into issues with the current ecosystem.

Omarchy ships with VoxType, but it has major issues (discussed below).

I've checked almost everything out there too: Handy, hyprwhspr, hyprvoice, nerd-dictation, WhisperWriter...and the usual pile of Whisper wrappers, tray apps, GUI frontends, Python scripts, Bash scripts, Node apps, Tauri, etc.

They all suffer from the exact same failure modes: holding a persistent key (pessimal), opening an app (bloated), picking a provider or choosing from 965 models you'll never use (decision fatigue), sending audio to a server (privacy), waiting for a response (speed), and hoping the network holds (unreliable).

Plus, tech stack and setup hell. Always a never-ending checklist of configuring this, tweaking that. You're constantly forced to deal with GUIs, background daemons, systemd services, bloated Python environments, Docker containers, massive Node setups, glued bash scripts, etc.

I just want one atomic and simple operation: Tap a keybind, talk, and get a desktop notification that the text is in my clipboard. And never error out as long as my machine is charged.

I use Omarchy for one of my rigs, and since it ships with VoxType and one of it's features satisfies the model, I spent some time looking into into it.

It’s a popular tool, but looking at the codebase highlighted a growing trend in OSS that I think is worth discussing: AI driven feature creep.

When AI is heavily used to generate code without strict architectural oversight, codebases can grow by accretion.

I noticed a few specific architectural issues that make it difficult for me to rely on the tool for my daily work:

• File Size & Complexity: The main.rs and cli.rs files are well over 2,3k lines each, and config.rs is approaching 5,000. The main.rs file alone handles CLI dispatch, config loading with 200+ lines of manual flag overrides, daemon PID management, audio transcription with a DSP resampler written inline, meeting commands covering start/stop/pause/resume/export/show/delete/label/summarize, inotify file watching, JSON formatting for Waybar, even GitHub web scraper update checking, and a first launch macOS setup flow, and more**.**
• Lack of Abstraction & repetition: The config override block in main.rs alone repeats the same pattern about 60 times without extracting it into a reusable abstraction.
• State Conflicts: In the same file, there are instances where the conceptual operation is the same, but the implementation diverges. For example, one function checks if the daemon is running by reading runtime_dir/pid, while another function reads runtime_dir/voxtype.lock, causing meeting commands to falsely report the daemon as not running. This bug has been fixed, but the bug itself is telling: The divergence is only possible if the two functions were written in separate contexts with no shared state, either across time with no refactoring pass, or across prompts with no architectural consistency check.

By no means this is a knock on the maintainer. Open-source is hard, and the maintainer owes us nothing for course.

But as a user who dictates prompts, notes, and code all day, I can't afford to lose a 15-minute train of thought because a newly merged CLI flag introduced a state conflict.

And since I couldn't find a tool that fit my exact needs, I ended up building one, even though I don't particularly enjoy writing C++ these days.

I made a pure C++ binary that compiles natively. Zero dependencies beyond standard Linux and C++ build tools. It links against whisper.cpp as an embedded library through its public C API. It boots, runs inference in-process, copies to your clipboard, and cleans up after itself. No daemons, no background services.

If anyone else is suffering from configuration fatigue and just wants a dead-simple, local transcription toggle, you can check it out here:

Source: https://github.com/rccyx/asryx

So excited to share this project with everyone here, going beyond just dots

GitHub: https://github.com/rccyx/osyx

Last time I dropped the rose theme.

Well, this is the next one.

Since then I've added a whole bunch of docs, open sourced a new tool, and next up is the flavors engine where one keybind switches themes instantly.

TL;DR:

I'm building a long-term project though, not just a dots dump, combining peak ricing aesthetics with hardcore '90s hacker terminal workflows.

Hyprland is the only compositor that makes this possible. (Although I'm using a year old version)

GitHub: https://github.com/rccyx/osyx

Dots on GitHub in case you need to yank some confs: https://github.com/rccyx/osyx

Requirements: Electricity (maybe)
Cost: $0

lol, hope this convinces you to move off

windows could never 🥱

This is Debian btw on Hyprland, if you need to take some confs, here
https://github.com/rccyx/osyx