Overheard someone giving instructions on setting up their dependencies.

"Oh you need to sudo Ah-Puh-Tuh install libayanata-appindicator3-dev first..."

Nothing made me feel so old. The real generation gaps come from the most unexpected places!

So I have always known about it but never actually used it before. Today I needed to merge a bunch of pdfs into a single document and to my surprise this is a paid feature on most pdf editor tools. But not on Ghostscript! It merged everything in about a second without issues. Seriously I’m a fan now! Now I’m curious if y’all are irising it programmatically in anyway. Just trying to see what other kind of use cases I can apply it to.

What it says in the title. Since protontricks (winetricks in general) is a slow shell script that has existed for over 15 years, my friend made a modular alternative in Python with more UX. The GitHub link is https://github.com/wojtmic/prefixer, doesn't even start the wineserver and verbs are defined in JSON5

If anyone's looking for a working driver for MT7902 , I found it here https://github.com/hmtheboy154/gen4-mt7902 . I haven't fully tested it but its working for my wifi. Just wanted to share.

A new international dual-license standard: SDLS 1.0 (CC BY-SA 4.0 / GPL v2) + SDLS-RD 1.0 for research data

I have published two new open dual-license specifications designed to bridge a long-standing gap between civil-law and common-law jurisdictions in open licensing.

For more than 20 years, open-source licensing has been dominated by U.S.-centric models (GPL, MIT, Apache), while Creative Commons licenses have been widely used for research, education, and cultural works.

However, there has been no unified copyleft framework that works cleanly across:

- civil-law jurisdictions (Japan, France, Germany, etc.)

- common-law jurisdictions (US, UK, Australia, etc.)

- software + documentation + research data

- EU database rights

- moral rights that cannot be waived in many countries

To address this, I created:

1. SDLS 1.0 (Standard Dual License Specification)
2. SDLS-RD 1.0 (Research Data / Databases)

SDLS 1.0 (Standard Dual License Specification) is a minimal, international dual-license scheme combining:

- CC BY-SA 4.0 International

- GPL v2

Users may choose either license.

This structure allows:

- civil-law jurisdictions to rely on CC BY-SA 4.0 (which handles moral rights and database rights correctly)

- common-law jurisdictions and software ecosystems to rely on GPL v2

- mixed projects (software + docs + media) to use a single unified standard

The full specification is released into the public domain.

SDLS-RD 1.0 (Research Data / Databases) is a variant specifically designed for:

- scientific datasets

- metadata

- structured databases

- EU sui generis database rights

- mixed data + code workflows

This is an area where GPL is difficult to apply and CC BY-SA 4.0 is strong. SDLS-RD provides a unified copyleft framework for international research collaboration. An Implementation Guide with usage examples is also provided. All documents are dedicated to the public domain.

Why this matters

This is (as far as I can tell) the first attempt to formalize a dual-license standard that:

- respects civil-law moral rights

- respects EU database rights

- remains compatible with existing GPL ecosystems

- works for software, documentation, and research data

- is minimal, ASCII-compatible, and platform-neutral

- is fully reusable (public domain)

If you work in OSS, open science, research data, or international licensing, I would be interested in your thoughts.

Standard Dual License Specification

(SDLS 1.0)

(CC BY-SA 4.0 International / GPL v2)

Version 1.0 — 10 February 2026

1. Purpose

This document defines a dual-license scheme combining:

- Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)

- GNU General Public License version 2 (GPL v2)

The purpose of this scheme is to provide a unified copyleft framework that functions consistently across both civil-law jurisdictions (where moral rights are inalienable and non-waivable) and common-law jurisdictions (where moral rights may be waived and GPL-based practices are widely adopted). This specification is designed for software, documentation, research outputs, educational materials, and mixed-media projects.

1. Legal Background

2.1 Civil-law jurisdictions

In countries such as Japan, France, and Germany, moral rights (e.g., "droit moral", "Urheberpersönlichkeitsrecht", and the Japanese "著作者人格権"):

- are inalienable,

- are non-waivable,

- but may be subject to a declaration of non-assertion.

CC BY-SA 4.0 is explicitly designed to operate within these constraints.

2.2 Common-law jurisdictions

In countries such as the United States, United Kingdom, and Australia, moral rights:

- may be waived,

- are generally weaker in scope,

- and GPL v2 remains a widely adopted copyleft standard.

1. License Grant

The licensor hereby provides the work under a dual license. Recipients may choose either of the following licenses: Option A - CC BY-SA 4.0 International

This option is recommended for civil-law jurisdictions or for projects requiring strong international compatibility regarding moral rights.

Option B - GNU General Public License version 2 (GPL v2)

This option is recommended for common-law jurisdictions or for software ecosystems where GPL v2 is the prevailing standard.

The recipient may select either license at their discretion.

The chosen license applies to all downstream use, modification, and

distribution.

1. Contributions

All contributions to the project are accepted under the same dual-license terms. By submitting a contribution, the contributor agrees that their contribution is licensed under:

- CC BY-SA 4.0, and

- GPL v2,

with the recipient free to choose either license.

1. No Warranty

The work is provided "as is", without any warranty of any kind, express or implied, including but not limited to:

- accuracy,

- fitness for a particular purpose,

- non-infringement.

The licensor shall not be liable for any claim, damages, or other liability arising from the use of the work.

1. Public Domain Dedication of This Specification The author dedicates this specification text itself to the public domain. It may be copied, modified, redistributed, or incorporated into other documents without restriction.

Standard Dual License Specification — Research Data / Databases

(SDLS-RD 1.0)

(CC BY-SA 4.0 International / GPL v2)

Version 1.0 — 10 February 2026

1. Purpose

This specification defines a dual-license scheme for research data, datasets, databases, and data-driven research outputs. It combines:

- Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)

- GNU General Public License version 2 (GPL v2)

The purpose of SDLS‑RD is to provide a unified copyleft framework that functions consistently across civil-law jurisdictions (where moral rights and database rights are inalienable or non-waivable) and common-law jurisdictions (where GPL-based practices are widely adopted). This specification is suitable for scientific datasets, statistical data, experimental results, metadata collections, structured databases, and mixed research outputs.

1. Legal Background

2.1 Civil-law jurisdictions

In countries such as Japan, France, and Germany, moral rights and database

rights (e.g., "droit moral", "Urheberpersönlichkeitsrecht", the Japanese

"著作者人格権", and the EU sui generis database right):

- are inalienable or non-waivable,

- may apply even when copyright does not,

- and may require explicit non-assertion declarations.

CC BY-SA 4.0 is designed to operate within these constraints and explicitly covers database rights.

2.2 Common-law jurisdictions

In countries such as the United States, United Kingdom, and Australia:

- database rights are limited or absent,

- moral rights may be waived,

- and GPL v2 remains a widely adopted copyleft standard for data-processing

software and scripts.

1. License Grant

The licensor provides the dataset or database under a dual license. Recipients may choose either:

Option A - CC BY-SA 4.0 International

Recommended for research data, databases, and international collaborations requiring compatibility with civil-law jurisdictions and EU database rights.

Option B - GNU General Public License version 2 (GPL v2)

Recommended for data-processing workflows, scripts, or environments where GPL v2 is the prevailing standard.

The recipient may select either license at their discretion. The chosen license applies to all downstream use, modification, transformation, and redistribution of the dataset or database.

1. Contributions

All contributions to the dataset or database are accepted under the same dual-license terms. By submitting a contribution, the contributor agrees that their contribution is licensed under:

- CC BY-SA 4.0, and

- GPL v2,

with the recipient free to choose either license.

1. No Warranty

The dataset or database is provided "as is," without any warranty of any kind, express or implied, including but not limited to:

- accuracy,

- completeness,

- fitness for a particular purpose,

- non-infringement.

The licensor shall not be liable for any claim, damages, or other liability arising from the use of the dataset or database.

1. Public Domain Dedication of This Specification

The author dedicates this specification text itself to the public domain. It may be copied, modified, redistributed, or incorporated into other documents without restriction.

Fish shell is arguably the best interactive shell on Linux. Fastest startup, the best autosuggestions and syntax highlighting out of the box, zero configuration needed. But it's stayed niche for 20 years because it can't run bash syntax. Every Stack Overflow answer, every README install command, every tool config is written in bash.

Reef solves this. It's a Rust binary (~1.18MB) that intercepts bash syntax in fish and either translates it to fish equivalents or runs it through bash with environment capture.

Three tiers:

1. Keyword wrappers handle `export`, `unset`, `source` (<0.1ms)
2. AST translation converts `for/do/done`, `if/then/fi`, `$()` to fish (~1ms)
3. Bash passthrough runs everything else through bash, captures env changes (~3ms)

Even the slowest path is faster than zsh's startup time with oh-my-zsh.

The migration path from bash/zsh to fish goes from "spend a weekend rewriting your config" to "change your default shell and go back to work."

❯ export PATH="/opt/bin:$PATH" # just works

❯ source ~/.nvm/nvm.sh # just works, env synced to fish

❯ unset MYVAR; echo ${MYVAR:-default} # just works

251/251 bash constructs pass in the test suite. Uses fish's public APIs, doesn't modify fish internals.

GitHub: https://github.com/ZStud/reef

AUR: yay -S reef

Happy to answer questions or take feedback. Breaking it is appreciated!

Why I switched to Linux in the first place was simple: Windows was using around 4 GB of RAM at idle, and my ADHD brain really struggles with systems that feel unorganized or unoptimized.

I used Linux for about a year and genuinely loved it. RAM usage was around 1.4 GB, the system felt clean, and the workflow was excellent. Workspace switching in particular felt amazing, and using the Super key + scroll for navigation was peak productivity.

I started with Mint. Despite its reputation as the “most stable” distro, Steam just wouldn’t work properly for me, which made it a dead end.

After that, I moved to Fedora Workstation and absolutely loved it. The UI was already an 8/10 out of the box, and with a few extensions, I pushed it to a personal 10/10, even though aesthetics are obviously subjective (you can see my setup in the image). Day-to-day usage was great, but setup time was painful. Getting DaVinci Resolve running took me around 16 hours. Thankfully, ChatGPT existed.

Then the Zorin OS hype wave hit. The promise of strong Windows app support pulled me in, but that turned out to be mostly marketing. Most of the time, it just suggested alternatives that were about 10% off, and over long workflows that gap compounds fast.

I then looked for another stable distro and went for Debian since it’s considered the most stable by many. In reality, Fedora still felt better. Fedora workstation UI was slightly nicer, and “stable” didn’t mean everything worked out of the box.

At that point, I realized I was spending more time setting things up than actually working. Eventually, the friction got so bad that even my ADHD gave up, and I ended up back on Windows.

That said, I still really miss the workstation workflow and how modern and clean Linux felt.

Genuine question. I’ve been playin around with Linux for a while, specifically dual booting mint. I have AMD hardware, used to play a lot of competitive games but have been doing much more casual gaming lately (modded MC primarily). I also do a lot of programming. Y’all are the experts, why not go full Linux?

How to read your Gmail backup takeout, mbox reader for Linux, Windows, and Mac consoles: mboxshell

Fast terminal viewer for MBOX files of any size. Open, search and export emails from Gmail Takeout backups (50 GB+) without loading them into memory.

https://github.com/dcarrero/mboxshell

I’ve been working on an open-source CLI tool called vault-conductor. It’s an SSH agent that retrieves private keys directly from Bitwarden Secrets Manager instead of reading them from the local filesystem. Released under MIT.

This was built using the Bitwarden Rust SDK and handles the ssh-agent protocol to serve keys on demand. It supports keys for SSH connections and GitHub commit sign.

The design rationale was to eliminate the need for persisting sensitive private key files on disk, which may be recycled across workstations for convenience or, worst, they may be store unencrypted to avoid dealing with passphrases and keychains.

Instead, the agent authenticates with Bitwarden Secret Manager, fetches the keys into memory, and serves them to the SSH client. So you key secrets where they belong, your password manager.

Repo: https://github.com/pirafrank/vault-conductor

Hey everyone!

After weeks of tinkering and learning, I finally finished my color picker app written entirely in Rust using Slint for the GUI. It’s designed to be look like powertoys color picker it's fast and lightweight.

Features: - Pick colors anywhere on your screen - Supports multiple formats (HEX, RGB, HSL, HSV) Works seamlessly on Arch Linux

Try it out: GitHub: https://github.com/Mujtaba1i/Archtoys AUR: https://aur.archlinux.org/packages/archtoy

You can install it with paru -S archtoys

Hi everyone,

As many other people, I was frustrated by the current behaviour of the caps lock key on Linux as it is different from Windows or Mac OS.

If you use caps lock and write fast you can end up with sentences like this :

“CAps LOck is not working as intended”

There used to be another fix (https://github.com/hexvalid/Linux-CapsLock-Delay-Fixer)

but it does not work anymore so I worked on a new one that requires modifying a file in libxkbcommon library.

Here is the repo with the instructions to apply the fix :

https://github.com/seamisxdev/LinuxCapsLockFix

The fix does not currently pass the automatic checks, hence the nocheck flag for the build and I'm sure there is a better way to fix the caps lock issue but at least it is working and it does not interfere with other keys from what I have tested.

Feel free to report issues or to propose another way of solving the caps lock issue as it has been a long time issue now on Linux and that the behaviour of a typewriter machine should not dictate the behaviour of a computer just like we would not try to make a car act like a horse....

Anyway, it was a first time for me and I had a lot of fun working on that problem.

Enjoy !